I didn't read any of this until today. The issue of eMMC size somewhat depends on how you end up using the Pyra. I see the most new-user friendly way to use the Pyra as being similar to the Pandora, and not requiring a large eMMC drive. That is, you get the basic operating system install, and you add applications and storage with the SD cards. If you have to re-install the operating system, your applications and data are back when you insert your SD card (of course, back ups are always a good thing, and lack of them is the most likely thing to bite a new user no matter which configuration you go with). This is not intended to be an argument against a bigger eMMC drive. A bigger drive only makes the system more flexible, and is only good, other than price concerns. The real sweet spot is the place where the added expense is worth the added flexibility. At some point it won't be; it can just be hard to determine when that becomes the case. It seems likely to me that either 16GB or 32GB would be the sweet spot as far as I am concerned. The ten Euros more for the 64GB might be worth it for me on a personal basis, but is unlikely to be worth extra cash outlay for the project, since most users would probably use the Pyra in a way that never makes use of the extra space. The technically savvy users who might want to do something that required more storage can always go to a good uSD card. Yes, it's slower, but it will all seem fast compared to the Pandora. Edit: The biggest single reason I can think of for arguing for more storage, or at least the 32GB, is the possibility of an internally installed Android build.