31 ms·
Meh... I'd lean towards web app first, wrapping in cordova for ios/android and electron for desktop at first... adding in more native features as time moves for
by tracker1 8y ago
Meh... I'd lean towards web app first, wrapping in cordova for ios/android and electron for desktop at first... adding in more native features as time moves forward, probably react native for {platform} as a second stage.
- PaulHoule 8y agoWhat I am aiming for is an application that never locks up and never makes you wait without clear indication if it is making progress or not. I could care less about many "Native Features" but latency is king. I am sick and tired of looking at spinning beach balls and such.
- tracker1 8y agoIf your data backend is over the internet, it doesn't matter if it's a "native app" or "pwa". You can handle appropriate state in most cases. If you're good at it, you can do it at the most atomic level, and should be relatively quick. If you can shard your api/data systems by locality, even better.
- PaulHoule 8y agoIt's the 95% latency that kills you. I have seen so many people make an app that is blazing fast at the office (either on a LAN or w/ a fast connection to the cloud) that ends up horrible for many end users. Sometimes the people who made the app don't even know.