Thoughts on app scope #149
Description
This might be related to #127, but from its contents this seemed a bit too much off-topic.
I've been using Vikunja for a couple of years already and just recently found out about the existence of the native Android app so I was happy to give it a try. The website (and thus webapp) serve me quite well for mobile, but the one thing I've been missing most that has so far kept me from migrating the last bits over from various other platforms to Vikunja is mobile notifications that remind me of deadlines and long term ToDo's so this would be the main thing I'm expecting from the native app.
I did not quite expect a complete re-implementation of the frontend, especially as the webapp already works quite well for smaller screens.
Because of the disconnected implementation there are features and customization options present in the webapp that are (currently) missing from this app.
Home Assistant also has both a regular website / webapp + Android companion app, but to avoid re-implementing everything frontend related twice (and to keep user customizations consistent between the App and Web) they provide a webview wrapper for the existing frontend and only add things to the companion app that cannot be implemented outside of it.
I.M.O. this could also be a well suited strategy for the Vikunja app. This would limit scope of the native app to features that cannot be offered by the webapp such as reminder notifications, easily creating new tasks through ShareTargets.
Depending on the goals of the native app this idea may be way out of line though. Just wondering if this kind of implementation had been considered.