You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.
- [X] I searched for similar issues and did not find one
- [ ] I'm using the latest version available in the [Windows Store](https://www.microsoft.com/store/apps/9NW16X9JB5WV)
I'm submitting a feature request:
I would like to suggest the following functions for the new (wonderfully implemented) registration page! But you can treat this with low prio of course.
Add users directly to the support MUC which has should be available in one the respective keys
This can make sense at several places, I leave that to your opinion: Guide the other to the providers webpage, or let the user directly open an email also based on the respective keys. When looking at their Account Profile or Help. Dunno.
I think is has high value as you as the client develop can barely help with all providers issues. Maybe you can also show this if there is e.g. a connection error. Then a redirection to the providers support can be shown (or an email, maybe even a propared one with further details).
Is way of guiding user to the support is also an idea of this project. Client developers can now put that off their support load.
Well, of course it should be differentiated between support for the server or support of UWPX.
Many many ideas :D
The text was updated successfully, but these errors were encountered:
And I agree with you that displaying a “Get support” link/MUC join button would go a long way towards better support for new users.
But joining them directly into those MUCs is in my eyes a bit too much. The reason for this is as follows:
If I think about it from my point of view, I would hate it if applications join me directly into MUCs without me approving this.
From the point of view of my parents, for example, they wouldn't even understand what happens there and just keep the MUC.
I think there should be a dedicated tab/button to get in contact with support for your server provider directly, instead always joining/showing the support MUC.
Before you create a new issue:
I'm submitting a feature request:
I would like to suggest the following functions for the new (wonderfully implemented) registration page! But you can treat this with low prio of course.
I think is has high value as you as the client develop can barely help with all providers issues. Maybe you can also show this if there is e.g. a connection error. Then a redirection to the providers support can be shown (or an email, maybe even a propared one with further details).
Is way of guiding user to the support is also an idea of this project. Client developers can now put that off their support load.
Well, of course it should be differentiated between support for the server or support of UWPX.
Many many ideas :D
The text was updated successfully, but these errors were encountered: