-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile FTUE: Choose Server screen (iOS) #5161
Comments
Apple guidelines for sharing info on paid plans without an in-app purchase option
|
@amshakal Do you still have the notes you took on researching the Play Store limitations for this screen? Could you add them here? |
Sorry, here are my notes: Developers can refer users to administrative information – like an account management page, privacy policy or to a help centre – as long as the webpage does not eventually lead to an alternative payment method. For services and products that are consumption only (apps that do not enable users to purchase access to digital goods or services from within the app), developers may choose to provide additional information about purchasing options without direct links, including using language like: 'You can purchase this book directly on our website' |
Parent Issue
element-hq/element-meta#126
Original Issue
Users creating an account need to select the server they would like to keep their account on.
We should provide them with a screen that offers them Matrix.org + an option to enter their own URL. On this screen we should also share info on EMS, but we need to be sure not to violate the App store guidelines (as we will not be offering an in app purchase)
insert link to design
This issue is considered complete when the tasks are complete, the screen matches the Figma design, it's been reviewed (by Product, Design & Engineering), and merged.
[Doug] Adding for my reference: we currently have a bug with wellknown lookup which should be avoided in the new implementation #5161. Probably more related to "Build FTUE Connect to Server screen" item in #5151.
The text was updated successfully, but these errors were encountered: