Application structure

[DuncanLithgow]

Do we have a diagram of the menu/organization structure?

It might be worth looking through it for possible optimization. ATimeTracker has virtually the same functions as TimeSheet (https://github.com/ambrice/timesheet) but in my opinion a somewhat trickier structure. (I've given up on TimeSheet as it's been abandoned)

Could we look at revising the structure generally? I'm happy to help developing a suggestion (I'm not a programmer)

[robinrosenstock]

@DuncanLithgow What exactly do you mean by "structure"? The general usage/usability of the app? Because You've said you are not a programmer, I guess, you don't mean the source code structure? When I hear something about a diagram of the menu/structure of an (android) app, I think about the different screens in the app and how to get there (for example from the tasks overview to the times screen). In Android these are called "Activity", which can be opened/switched to with "Intents".

Here is the form of an example diagram that comes to my mind:

Although this link is for android developer, it shows some guidelines and example in structuring the app: https://developer.android.com/design/patterns/app-structure.html

I also think there are better alternatives than to use the hamburger menu all the time...

[DuncanLithgow]

Hi @geniusupgrader yes, the visual organization of the app is what I'm talking about. I've had to reluctantly go back to TimeTracker for now - I don't remember the deal breaker. But it'd be happy to plan some time to give feedback on ATimeTracker and restart using it again for tests.