Skip to content
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

Closed
1 task
Tracked by #5151 ...
daniellekirkwood opened this issue Nov 17, 2021 · 3 comments · Fixed by #6048
Closed
1 task
Tracked by #5151 ...

Mobile FTUE: Choose Server screen (iOS) #5161

daniellekirkwood opened this issue Nov 17, 2021 · 3 comments · Fixed by #6048
Assignees
Labels
A-Login T-Task Refactoring, enabling or disabling functionality, other engineering tasks Z-FTUE Issue is relevant to the first time use project or experience

Comments

@daniellekirkwood
Copy link
Contributor

daniellekirkwood commented Nov 17, 2021

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

  • Check with marketing the URL to show people (do not create as link)

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.

@daniellekirkwood daniellekirkwood added A-Login T-Task Refactoring, enabling or disabling functionality, other engineering tasks Z-FTUE Issue is relevant to the first time use project or experience labels Nov 17, 2021
@daniellekirkwood
Copy link
Contributor Author

Apple guidelines for sharing info on paid plans without an in-app purchase option

  • 3.1.1 In-App Purchase: If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, etc. Apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.
  • 3.1.3 Other Purchase Methods: The following apps may use purchase methods other than in-app purchase. Apps in this section cannot, within the app, encourage users to use a purchasing method other than in-app purchase. Developers can send communications outside of the app to their user base about purchasing methods other than in-app purchase.
  • 3.1.3(c) Enterprise Services: If your app is only sold directly by you to organizations or groups for their employees or students (for example professional databases and classroom management tools), you may allow enterprise users to access previously-purchased content or subscriptions. Consumer, single user, or family sales must use in-app purchase.
  • 3.1.3(f) Free Stand-alone Apps: Free apps acting as a stand-alone companion to a paid web based tool (eg. VOIP, Cloud Storage, Email Services, Web Hosting) do not need to use in-app purchase, provided there is no purchasing inside the app, or calls to action for purchase outside of the app.

@daniellekirkwood daniellekirkwood changed the title Build FTUE Choose Server screen iOS Nov 17, 2021
@daniellekirkwood daniellekirkwood changed the title iOS Build FTUE Choose Server screen Nov 17, 2021
@daniellekirkwood
Copy link
Contributor Author

@amshakal Do you still have the notes you took on researching the Play Store limitations for this screen? Could you add them here?

@amshakal
Copy link

amshakal commented Dec 9, 2021

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'
'Go to our website to upgrade your subscription to Premium'
'This movie isn’t available to rent in the app. However, any movie that you rent through ourwebsite.com will be immediately available to view in the app'
'Need extra lives? Head to our website to purchase more'

@daniellekirkwood daniellekirkwood added Z-FTUE Issue is relevant to the first time use project or experience and removed Z-FTUE Issue is relevant to the first time use project or experience labels Feb 7, 2022
@daniellekirkwood daniellekirkwood changed the title Build FTUE Choose Server screen Mobile FTUE: Choose Server screen (iOS) Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Login T-Task Refactoring, enabling or disabling functionality, other engineering tasks Z-FTUE Issue is relevant to the first time use project or experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants