3 ms·
You can't really win with web apps. A native app that painted either way would be called 'broken' and not pass QA. Yet we swallow things like this without blin
by JoeAltmaier 12y ago
You can't really win with web apps. A native app that painted either way would be called 'broken' and not pass QA. Yet we swallow things like this without blinking.
- nilliams 12y agoNot totally sure I get you, native apps tend to use a combination of placeholders and spinners too (when loading network content). Are you saying people are harsher in their judgement of web-apps, or more accepting?
- JoeAltmaier 12y agoVastly more accepting of web apps. Web apps stall, spin (or worse yet don't spin yet are unresponsive), paint in embarrassing frames and masks with old content showing through the holes, and on and on. A native app that did that would be criticized roundly; web apps get a pass for some reason.
- deleted 12y ago[deleted]
- solarexplorer 12y agoNot really. See Launch Images in iOS: https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/LaunchImages.html https://developer.apple.com/library/ios/documentation/UserEx...
- JoeAltmaier 12y agoThat's ok at launch (to cover up how awful web apps paint). But what then? Change forms or screens and it fails again. Or hit a button - no visual indication you hit it; app hangs; screen updates in spurts. Not all web apps, but certainly a large fraction.
- nilliams 12y agoBadly implemented apps are badly implemented, native apps aren't immune to this phenomenon.