on iPad the UI is extremely unintuitive and/or broken
The benefit of the desktop is being able to hover over buttons, most have tooltips with descriptions. This is not an excuse necessarily but I would liken it to landing on github.dev or vscode.dev without having seen or used VS code before. I really hate walkthroughs with tooltips (both as a user and a developer) but maybe I'll have to do something like that. What I do like about the current UI is that, by keeping control elements on the side and tabs on the bottom, I can have a consistent experience across devices and screen sizes.
Drawing more attention to the fact that there is a tabbed interface might help, seems like that was an issue.
Re: markwhen's syntax - I'll tell you what I like about it first, and then get into some of your points. I like that it is quite progressive. You don't need a header to start, nor groups, nor ranges necessarily, and you shouldn't have to think much about date formatting.
```
1 Aug 2023: hi
```
is a valid markwhen document. If a list of dates like that is all you need, that's great. If you need ranges you can add ranges. Need groups, add groups. Need metadata, add a header. I like that it follows a new user's experience, you don't necessarily have to start with everything from the beginning.
On groups and sections, people wanted nesting, soooo the simple hashtag syntax wasn't going to work without an end hashtag or something. So it doesn't mean nothing, it means the end of the group or section. Idk, I'm open to suggestions about it. I personally don't use nested groups and sections that much but people wanted it. There has to be some endGroup or endSection syntax I think, even if it's not those specific words
Comments
Thank you for the candid feedback.
The benefit of the desktop is being able to hover over buttons, most have tooltips with descriptions. This is not an excuse necessarily but I would liken it to landing on github.dev or vscode.dev without having seen or used VS code before. I really hate walkthroughs with tooltips (both as a user and a developer) but maybe I'll have to do something like that. What I do like about the current UI is that, by keeping control elements on the side and tabs on the bottom, I can have a consistent experience across devices and screen sizes.
Drawing more attention to the fact that there is a tabbed interface might help, seems like that was an issue.
Re: markwhen's syntax - I'll tell you what I like about it first, and then get into some of your points. I like that it is quite progressive. You don't need a header to start, nor groups, nor ranges necessarily, and you shouldn't have to think much about date formatting.
``` 1 Aug 2023: hi ``` is a valid markwhen document. If a list of dates like that is all you need, that's great. If you need ranges you can add ranges. Need groups, add groups. Need metadata, add a header. I like that it follows a new user's experience, you don't necessarily have to start with everything from the beginning.
On groups and sections, people wanted nesting, soooo the simple hashtag syntax wasn't going to work without an end hashtag or something. So it doesn't mean nothing, it means the end of the group or section. Idk, I'm open to suggestions about it. I personally don't use nested groups and sections that much but people wanted it. There has to be some endGroup or endSection syntax I think, even if it's not those specific words