In the latest mobile version for Android (3.6.18), notes open in the last mode they were in: If I was editing a note when I closed it, it reopens in the editor; if I was viewing, it reopens in view mode.
I want notes on Android to default to opening in view mode every time. Is that available? I can’t seem to find an option for it in the Configuration settings.
Hmm, yes I can see how it could be annoyance. But it does remember so if you mostly use the viewer, you can always switch to this, and it will still be the viewer on the next note you open? I get that's a change from the previous version but I guess not too much of an issue? (unless I'm missing the use case)
Most of the time, I use the mobile version of Joplin as a reference database to look up information. I edit that data maybe 25% of the time. If I’m going to edit, the new feature requires me to remember to switch back to view mode before I close a note. Not a huge deal, but it would be nice if there were an option in settings to choose between
Recently, probably with an Android app update, I can't seem to figure out how to switch to the viewer mode at all. How do I do this? I've checked the three dot menu and icons at the top and I see nothing that seems related to switching views.
Thank you. I actually figured that out today but it took me a long time, partly because that book icon and the drop-down next to it look a lot like they are part of the same graphic. In other words, I interpreted that drop down symbol as applying to the book, and when I tapped in that general area I of course got a list of notebooks, which matched my expectations for tapping on a book icon! So for that reason I did not realize that there are two separate places to tap there. For better UI design, those two graphics should be separated further, and it might make sense to do something other than using a book icon right next to a notebook selection.
I just switched to the new version, so I don't want to comment on the "default to view mode VS default to last mode" yet. I'm not sure yet which one I prefer.
But I used it a bit on a phone (Android). One thing I noticed is that previously it was easier to exit the edit mode - I could press "back" button which is at the bottom, near the keyboard. So I was able to quickly protect my note from accidental changes and see the note rendering (I usually edit in Markdown mode). Now I have to move my fingers to the top of the screen - inconvenient.
And does finishing the edit trigger sync? If yes, then additionally I was able to start syncing faster.
I agree with this. I about had a heart attack after the change when I first opened the Android version and everything was in edit mode. Took me a little while to figure out how to change back to view. I am managing a shared instance of Joplin with less experienced users. I sent them an alert to be careful to turn on the view mode, but it would be better if the app defaulted to that between sessions. It's bad enough that they could accidentally delete everything. Now they can more easily accidentally change things that don't belong to them. I hope something can be done.
Frankly, I think the current iconography may be contributing to the confusion.
The book icon does not immediately communicate “View mode” or “Reading mode” to me. It reads more like a label than an action button.
Similarly, the edit icon feels inconsistent in scale and visual weight. In editing mode, the user sees a large book icon; in view mode, a large slanted pen. The relationship between the two states does not feel clear. A toggled state would be much clearer IMHO.
This is not meant as flames — just direct design feedback. I’d be happy to help from a UX/UI perspective.
@meny FYI I picked out the icons for this. It's very much replicating how it is done on the Obsidian Android app. Is there any ways you think the way it is done in Obsidian is better, or would you say it has the same shortfalls?
In editing mode, the user sees a large book icon; in view mode, a large slanted pen. The relationship between the two states does not feel clear. A toggled state would be much clearer IMHO.
Are you saying if the icons are reversed, then it would be ok? i.e. it shows a book when in view mode, and shows a slanted pen when in edit mode?
I did debate this myself, which way around the icons should be.
In your example, the non silohette icons don't really go with the theme and look kind of cheesy
In the case of the existing markdown / rich text editor toggle on desktop, I think it's not really clear whether the lightened / darkened button means enabled or disabled. Having a tick like in your first example makes it clear, but that takes up a load more space
that's just a mockup to check if it fits - agree I don't want toon eyes in there either
Yes whatever we do we should implement it in such a way that the button state is clear. On the desktop app, it's done by making the non-active option half-transparent, and the active one with a bg that standup against the toolbar bg:
I think those are strong enough visual cues and keeps things more compact. I agree that a tick would not be an ok here.