[Feature] Mobile application about stamhoofd

[SimonBackx]

Well, the plan was is to use Capacitor. The code is already optimized to run in an app like way and the usage of HTML and JS shouldn't be too noticeble in this type of application. Native apps or Flutter (although not such a fan of Flutter) is for the long term when we do have more developer capacity / bigger community (because everything needs to be rebuild since most logic runs in the frontend due to the end-to-end encyption).

The nice thing is that we can keep shipping new features at the same speed and that we can integrate the current registration process also in the app without duplicating any code.

Of cource, a native app will always feel better and be more responsive, but this is just a tradeoff we have to make to push the project further. If executing is good and we do optimize for performance, we can really hide the fact that is not an native app for most users.

But the app is very high on the todo list, I want to ship a basic version at least before July.

[WardToulet]

I thought the plan was to provided a service worker and manifest to the application to turn it into a progressive web app this would allow the web app to function as a mobile app (on android at least, IOS does not support PWA's all that well) without splitting the effort between a flutter and a web frontend, thus slowing down development.

[maltsavkiryl]

When focussing on business value, starting with a PWA or something like capacitor would definitely would be a better approach. Stamhoofd isn't an application that would benefit much from being native (at the moment).

[SimonBackx]

We'll probably release open test versions of the app next week 🤞

[SimonBackx]

Apps will launch this week normally