I currently have an Android Wear action that is very destructive. How could I add a confirmation dialog to that action before executing it.
For example, I have an action "Finish Workout" on the wear...once a user finishes their workout, they can't resume it. I want to ask them 'Are you sure you want to finish your workout?'
how could i do this?
You can use DelayedConfirmationView that is designed to address this, see this tutorial. It will give your users a chance to stop/cancel the operation if they decide to.
Related
So, I'm building a Ride Hailing app and I'm still not sure of what route should I go with for alerting a user for a New Ride Reuest.
Should I go with Draw Over Other Apps to open the activity when the notification is received.
Should I use fullScreenNotificationIntent with showOnLockScreen
And if I use fullScreenNotificationIntent, the Android system not always open the activity, it shows a headsupNotification, and I will have to add and handle accept reject actions.
Need a proper professional suggestion on this.
I'm trying to implement in-app updates in my application but I'm facing a doubt about how to work with flexible updates. I will show the flexible update to the user in the splash screen when the user open the application, what I need to do before this? Can the user navigate on the application or I need to force the user to keeps on the splash screen until the update are done?
My doubt about this it's because of the snackbar that I want to show to her when the update are done, notifying the user to restart the app, but if I initiate the in-app update listener in the splash and let the user continue the navigation, how can I show the snackbar?
I'm trying to implement in-app updates in my application but I'm facing a doubt about how to work with flexible updates. I will show the flexible update to the user in the splash screen when the user open the application, what I need to do before this?
Your question is unclear. Your user opens the app, you present the option to update in the background. OK. So ... what else needs to happen "before this"?
Can the user navigate on the application or I need to force the user to keeps on the splash screen until the update are done?
Allowing the user to navigate the application is exactly the purpose of doing a flexible update.
My doubt about this it's because of the snackbar that I want to show to her when the update are done, notifying the user to restart the app, but if I initiate the in-app update listener in the splash and let the user continue the navigation, how can I show the snackbar?
Have you read the documentation that explains exactly how to do this?
Are UI recommendations or guidelines somewhere. I am looking for the recommendation from Google but unfortunately I can't find it.
I want to see something like "...do not use exit button in your Applications until you really need it...".
I'm sure that the exit button in android app is not good idea, in general at least. But I want to prove this idea to customers and designers.
I need links with explanations.
This video will help your customers to understand: https://www.youtube.com/watch?v=631T7B8HOv4
Basically, the back button is an exit button. So, there is already an exit button!
Show it to your customer and ask him if he wants to look stupid with duplicate button that takes precious space on a small screen.
His app will never look professional.
General Design Guidelines:
http://developer.android.com/design/get-started/principles.html
Best Practices for User Experience & UI:
http://developer.android.com/training/best-ux.html
Providing Proper Back Navigation(Something you were looking for):
http://developer.android.com/training/implementing-navigation/temporal.html
we used back button as Exit button. Generally on Back button, as per clients req we used to show the default dialog to user, "Do you want to exit app ? ".
Generally clients needs this confirmation because if we press back the app is directly exit from app. so just for confirmation to user clients want this exit dialog be there.
No exit button is iOS philosophy, not android. I suggest you stick with device's back button rather than a UI button to exit your app while asking for confirmation via dialog box or a Toast.
I have the following flow in my application and dont know how to implement this in an android way.
The user can check in the app if there is a update available, if so he can choose if he wants to download it, and once it is downloaded an update of the database takes place.
In the android documentation I only find basic description of either a progress dialog, or alert dialog but not how to have something more complex. For the sake of the example what i would like is the following.
The user clicks the check for update button
A progress dialog with checking for update pops up (which can be canceled)
If there is no update available the user gets informed and can click ok.
If there is an update available the user can choose to download it or cancel.
If he chooses to download he sees a progress bar. (with a cancel button)
Once the download is finished he sees a database updating alert dialog.
Finally he gets an all is done info and can click ok
Just an example yet what is the android way of implementing a series of dialogs like this. Wizard, series of different dialogs, one always changing one ...
Suggestion how to implement this in a recommended way would be highly appreciated
thanks
martin
Each dialog can launch the next subsequent dialog and automatically dismiss itself. Look at the DialogListeners attached to each button in example code
i am trying to create a dialog box to appear in the middle of the screen when my main program is not in focus and running in background. The purpose of the dialog box is to force the user to take an immediate action. I am already using the notification manager to notify the user but i would still like a old school popup dialog box.
Thanks :D
Popping up a dialog from an application running in the background is thought of as bad practice because it may confuse the user, and may annoy the user because you are disrupting the current task s/he is engaged in.
It is advised by the Android developers to use the Android notification system for tasks like these. A guide to create notifications is here: http://developer.android.com/guide/topics/ui/notifiers/notifications.html
Dialogs are created with the Intent of the current activity. Since your app will not be in focus at the time, you cannot create a dialog.