New answers tagged

1

I like Google Material Icons' Add Location icon:


0

The Floppy disk icon is a common icon that's been engraved into the minds as the Save icon. Apart from that, you could also use the Tick to signify Done and Save Ideally you should follow the guidelines specified for the Smartphone's OS.


0

Save and return to address book but need to acknowledge the user with successfull message We need to keep the Address book as landing page for all the actions like edit, delete and share functionalities. So that's the reason to return Address book page after saving data. This process is standard on around 90% of the application. When user return to ...


0

I think you should only touch the database when the user is finished editing their document. So, when the user hits the Save button, whatever data is entered at that point should be saved. In your example, if the user creates a new document, fills out a title and some content, renames the title, and then hits the Save button, the modified title and the new ...


2

Killing default behaviour is never a good idea. We humans are creatures of habit, and changing our personal workflows will most likely result in more questions than answers (and the frustration that comes with that). Adding to default behaviour might work, like adding a custom item in the context menu that is specifically for your own custom functions. But ...


0

Does the landscape mode offer a significant better user experience? If not, is it worth the effort and compromises? It's acceptable to restrict the app to portrait mode only.


0

I only fancy having the back button on the toolbar. As a user, it's hard to reach for the confirm/save button if it's in the toolbar. Isn't the whole of this screen to confirm/save? It should be placed in the area where it is easier to reach. A floating action bar perhaps? On the landscape view, the toolbar should still be placed on the top area. The ...


-1

According to me, The toolbar should only contain the back button. Devices are getting taller and taller, so the save button on the top would be a bad User Experience for the user when he uses your App one handed. So I would go for a FloatingActionButton in Bottom|Right of the Screen I would also suggest a FloatingActionButton which would be hidden till all ...



Top 50 recent answers are included