Tested, browsed to another tab, switched to another app, turned off screen. Are there any limitations compared to a native app?
It needs an example of nested loop and skipping last item, with comments.
It needs an example of nested loop and skipping last item, with comments.
Probably only minor ones; three come to mind:
- The web app has to be loaded every time (~700K total right now), whereas the native app works offline. This could be mitigated with a progressive web app, though.
- Fullscreen mode is usually blocked by mobile devices for websites, so you always see e.g. the address bar. That’s just a visual thing, though.
- I’d assume that native audio APIs would allow for more control (and are likely easier to work with too).
Not sure how that would work with the state being saved in the URL — you'd need to save each routine separately I think.
Keeping the state in the URL actually avoids this. There is no storage to be separated. The cost is what perilunar said, one shortcut per routine.