saecki
commented
3 years ago Regarding flutter I have to say it does look promising and definitely makes sense in this case as it allows targeting ios. But I'm a fan of native apps. While flutter does come close especially since the material components are pretty much identical, it doesn't feel as responsive and snappy as native apps. I haven't decided yet if I'll maintain a fork if the flutter app becomes stable or just go with flutter. Until then I will keep working on the android app.
While the material spec says that the backdrop-menu should relate to the front layer and provide contextual options, it is a beta spec and may change in the future. Additionally I have seen other apps place a drawer like navigation-menu in it with less than 5 entries since it doesn't look that empty. In my test application I played around a bit and had it implemented like this:
 |
 |
|---|---|
 |
 |
I am a bit split myself if this is ok or not and if you'd like to follow the spec I'd totally understand and go with a drawer menu. Either way it can wait for a new pull request.
agersant
This implements jetpack navigation using fragments instead of the old activity navigation.
MainActivityis written in Kotlin (if that is an issue I can convert it to Java) and I used the type safeView bindingfeature in some cases to make finding views declared in xml much nicer.Currently the settings are accessed through a toolbar menu, I could imagine moving them into a drawer layout or backdrop (design spec - implementation). That would make the navigation icon in the top left permanent and prevent shifting the title when navigating to a non top-level destination. In there a quick switch page for managing multiple servers and an about page could be added as well.