For this use case, phones are kinda powerful enough. Not quite though : applying photo filters (even just HDR+ in order to improve the picture) can take a l

For this use case, phones are kinda powerful enough. Not quite though : applying photo filters (even just HDR+ in order to improve the picture) can take a lot of time. I am not sure whether Prisma slowest is due to mobile SOCs or would be helped if they switched to a better implementation though (Google Photos & Snapseed rely heavily on Renderscript and have been able to deliver very fast filters that way) HDR+ is still slow though .. and I don't think it is unrealistic to ask to see the resulting picture in less than one second. So better SOCs would help there Also, for motion design, fluidity is very important : if you miss frames, the illusion is shattered. And that's also important for a lambda user, having things move into place helps in understanding what is going on. When you delete a mail (or have a new one), having the list of emails move into place instead of blinking from one state to the other helps the user understand the event. Same thing for screen transitions. Android is not quite there yet (and to be fair neither is iOS, it is even surprisingly worse in many regards). Again, it is not entirely clear how much of this is due to software (not java, but the OS debuts as a camera OS, then a blackberry competitor and only after that as a modern mobile OS) but surely better single core performances would help accomplish this and Apple wrecks Android in that specific area.