Acrobat Mobile Toast Notification Decay Time

[ndudde67]

I use the Android version of Acrobat Mobile to markup/take notes on PDFs for school. I use the Comment>Pencil tool for this. Occasionally I make a mistake and have to use the undo/redo buttons. The issue is that when you have to undo several lines, the toast notifications (non-interactive pop-up notifications at the bottom of the screen) that say "Drawing was undone" stack and take FAR TOO LONG to disappear. I'm not an Android developer, but I know the decay time can be adjusted for a toast notification. Either that needs to change or the app shouldn't keep stacking the notifications on my screen. They obstruct content. The following link details the correct way to instantiate a toast and provides a parameter to control the duration of the toast via user-definable constants LENGTH_SHORT and LENGTH_LONG.

https://developer.android.com/guide/topics/ui/notifiers/toasts

This StackOverflow post might also be helpful (although I suspect some info might be deprecated):

https://stackoverflow.com/questions/12922516/how-to-prevent-multiple-toast-overlaps?answertab=trendi...

Here's a suggested change if you can't change the behavior of the toasts:

You could (instead of using notifications) have the UI perform a gentle glow/highlight around the undo/redo controls. This still provides the user with a visual cue that the action has occurred without getting in the way of getting work done.

Thanks for reading this feedback, devs.

[S. S · Accepted solution]

Hello,

I hope you are doing well. Per the description, I understand that you want to change the Decay Time for toast notifications.

However, this has to do with the accessibility settings of the device and not through the application. You may contact your manufacturer support to get a better idea if this can be done.

If you think there is an enhancement that can be done on our part, please feel free to fill in the feature request form so that it reaches our engineering team for them to look into it and try to implement it in the upcoming updates.

Link: Share your feedback on Acrobat DC (uservoice.com)

Thanks,

Souvik.

[ndudde67]

Thanks for your swift reply.

Actually, per my post, if the app cannot have its decay time altered or the toasts cannot be kept from stacking (I have checked, and I am sure there are methods for cancelling active toasts) then toasts should not be used for this functionality. It creates a poor user experience and surely violates Google's design intentions for Android. There is absolutely no reason that undoing 5 actions should require a notification to stay onscreen for 5 times the length of one notification. The device manufacturer's accessibility settings may control the length of time for one notification, but it is the developer's responsibility to ensure that they do not stack. My accessibility settings for toast timeout are set to the default (minimum) setting.

I don't wish to make a massive issue out of a minor problem, but I am sure that the fix is relatively easy.

Thank you

[ndudde67]

Also, I will follow your advice and give feedback through the method you have suggested.

[S. S]

@ndudde67 Hello,

Thank you for sharing the feedback with the engineering team. They will track the feedback and will try to get it fixed in the upcoming updates.