I find it is best to include the UI back button by default (for the reasons listed by @Tin Man as well as parity and operational efficiency when designing an app for both iOS & Android). However, you should consider the implications of doing so on a screen-by-screen basis.
Additionally, you may want to specify different actions for the hardware back ...
I think it is based on the user expectations and as a user, I don't expect to see the "Home" button in the top-left of the screen in a mobile application
Expectations with the home button in an app
When I see just a Home icon, I would be hesitant to click it because I can't be sure of how to get back to the previous screen. Also, I might not be aware of ...
I am not sure about the rejection... But, you say that you go from an overview to a detail page and back. So the back button is certainly the right choice. It tells the user, that she can go back to the overview. The home button instead suggests that the user can go back to home, from wherever she might be. The way it looks one could mistake the home icon as ...
It is acceptable, and also, a lot of famous apps use the home icon, including Youtube, Netflix and Instagram. The home Icon is one of the few universally recognized by users.
If you want to know more, I recommend this article by Nick Babich:
Icons are, by definition, a visual representation of an object, action, or idea. There are a few icons that enjoy ...
Try testing the smallest effective difference with your users.
If some of the rows are offering details on touch, you can test with your users if a link color works. Since the whole row is tappable, You could try making each value per row as a link.
You could try a background color if need be as well. This might run the risk of being confused with a ...
While users are able to choose whether or not they want to receive notifications (and in some newer android versions, if they want it to display notifications bubbles on the icon) from your app, they cannot chose what kinds of notifications they want to get. That's a binary all or none decision.
If, for example, you have two kinds of notifications, one when ...
Unless the users are aware of this setting in your app, it will be difficult to get them to use it. Instead of putting it inside Preferences, if it is really important, it could be separated into its own option to stand out and be easily discoverable.
It is important to ask what advantages does it offer to the users in doing it this way. Does it offer them ...
It's my proposition:
Screen can be on the right.
Menu with elements(users, history, controls etc can be on left)
It is worth constructing a menu so that it is possible to make a categorization and divide into not correlated options if necessary
It all depends on the product strategy
if the target is to be an advanced graphic processing program
it's worth thinking about the menu comprehensively and holistic.
If it is however a one-time function in the application then - three buttons with active state of active tool should be good:
Or put the interface elements on the left side of the canvas ...
What you already have is good. Listing a few things that may help improve –
Align text to left, so that both text and buttons are aligned.
Increase whitespace around the content to make it look more centered.
Use text-link for the secondary CTA. This will improve focus on the primary and maintain content alignment.
Depending on the context like what devices and orientation this app is supposed to run on, I'd pick the safest option and have a known mobile pattern where all of your content is laid down from the top, starting with the image header.
What you have shown here is more like a website layout and that's not something people would expect when downloading & ...
At times a lot of these can be classified as anti-patterns since the guidelines for how Bottom Sheets should appear are very vague. The purpose of a bottom sheet is to appear to be easy to reach for the thumb or index finger while providing an alternative to a popup or similar content accessible for taller displays and one handed use.
Essentially I believe ...
According to Fitt's Law - The time to acquire a target is a function of the distance to and size of the target.
I agree that I think distance between the menu and the bottom sheet is substantial.
This solution allows placing a lot options in one place.
No you don't missing something - it's a good practise.
The other solution in this circumstances is ...