Toast notification on windows #1178
Replies: 4 comments 4 replies
-
@VladislavAntonyuk Would the upcoming Popup PR also address this 👆? |
Beta Was this translation helpful? Give feedback.
-
It is closer to "native" implementation and more familiar for users to see something in Windows notifications. Also toast should be automatically dismissed (at least we set an expiration time for it). I saw a sample in Windows community Toolkit that looks like on Android and iOS. You can try reuse it in your app with custom IToast implementation. |
Beta Was this translation helpful? Give feedback.
-
@VladislavAntonyuk Good thought about using the IToast interface for a custom approach. I appreciate the "closer to native" implementation approach, but in this case it seems like it's not exactly the same kind of native "thing" despite being called a ToastNotification in WinUI. It really behaves like something different. Some similarities sure, but different enough that if you are thinking about cross-platform user experience it stands out as "not the same kind of thing" on windows. That's my 2 cents anyway. I'll check out the IToast approach or just do something custom altogether. I understand how the root grid approach you mentioned can impact other content, but maybe using a standard page ControlTemplate to provide a layout that hosts a toast message consistently across pages would suffice. |
Beta Was this translation helpful? Give feedback.
-
Closed as per the Community Stand-up discussion here: https://youtu.be/N9wMcBP4jtg?t=2889 |
Beta Was this translation helpful? Give feedback.
-
I just evaluated the Toast feature in the toolkit. Kudos to the contributing developers. But I am curious about the decision to use a windows toast notification on the Windows platform. 1) The rendering "toast" on Windows is notably different / more formal, 2) it's outside of the application visual container, and 3) it registers something in the system (toast remains in the notification list for Windows until dismissed). Toast for Android and iOS feel considerably more lightweight from a user perspective, being internal to the app only, temporary in the app container, then gone. The use case scenarios you would consider for the Toast UI become limited if you wish to include Windows support.
Is there any consideration for changing this behavior on Windows to use something more similar to the iOS/Android experience?
Beta Was this translation helpful? Give feedback.
All reactions