Unless the hardware can and will be upped from a $20 to a $200 SoC because it’s required to keep response times low, then someone isn’t doing their job. There has obviously been mountains of specs during these projects, but the most important one - the response time - was obviously overlooked.
I’m not saying like the GP that this indicates inexperienced developers, but it does indicate poor technical leadership and priorities. Further, good/senior developers would have been more likely to call this out.
A higher powered SoC might help make it lag-free... But the real solution is simply to put in the requirements that 90% of taps must be fully responded to within 100ms. Animations must complete within 350ms and be 60 fps. Dragging must have a glass to glass latency of under 50 ms. Booting from door open to usable must be done in 5000 ms.
While we're there, lets put in the requirement that a random joe from the street, with no training, when given the UI and asked to complete a task (eg. Play me some coldplay, turn on the window defroster, pair a bluetooth phone, get directions to the nearest gas station), must be able to figure it out within 20 seconds and 6 taps on average.
I’m not saying like the GP that this indicates inexperienced developers, but it does indicate poor technical leadership and priorities. Further, good/senior developers would have been more likely to call this out.