Mobile app
Targets:
- Android
- iOS
- Windows phone?
The client-side of the app is designed for mobile compatible HTML5. In any case, the web app should work just fine when opening it in the browser of a mobile device.
Considerations:
- Local storage should work well, so that records can be stored potentially for days/weeks, and be synced as soon as an internet connection is available.
- Tighter layout; it only really is the
tracker
page.
Options:
- webtoapplication.com does everything for you for $119 - but: If the user is not connected to internet then the app will show an alert page that says no internet connection, please connect to a near network. Also, they are fishy, sending fake tweets and a competitor site is ... almost a copy, but with a slightly different theme.
- Anyway, PWA is the way to go!
Todo:
-
Only apply to /app
, right? So manifest only there too? the service global can be scoped, but our asset namespace is flat. We make the sw only cache/app
and supporting assets -
woops, the landing page looks different as expected on mobile devices now! fixed -
Do I want things different, e.g. different menu? no, fine for now -
Check with Chrome lighthouse plugin. done, and improvements made -
Fonts ... use google fonts or not? serving all fonts ourselves is actually easier -
Can actually detect online/offline status kinda, this seems to be the user turning offline mode on. We don't use this now -
Can detect if visible? does not seem like we can, other than JS api that we already use -
display standalone or fullscreen? fullscreen looks more native
Resources:
Edited by Almar Klein