3 ms·
I implemented an app that uses Web App Manifest and Service Workers and uses material design lite. It's almost indistinguishable from a native Android app. If I
by MatthewPhillips 11y ago
I implemented an app that uses Web App Manifest and Service Workers and uses material design lite. It's almost indistinguishable from a native Android app. If I put a little more effort into the animations it would be even closer.
The biggest gap I find is sounds. There's no way to say "do the native click sound here". Now I could find the sound and play it in an <audio> element but I'm sure that these sounds differ depending on manufacturer and surely differ on iOS and WinPhone.
- TeMPOraL 11y ago> It's almost indistinguishable from a native Android app. If I put a little more effort into the animations it would be even closer. The key phrases here are "almost" and "If I put a little more effort". The almost-but-not-quite-native webapps are the mobile ecosystem's equivalent of the uncanny valley. It sort of looks like an app, but then it suddenly 404s a button, or starts lagging, or doesn't do the default for native controls, but rarely used function. It's enough to break user's trust in what the app is and what it's doing. It feels like Java's Swing all over again.
- hackcoughgasp 11y agoThe standards are still young and implementation is spotty. Several years from now the things that you can't do in a web app will be few.