The definitive guide for App developers and Project Managers

by ?? Edgar Andres Bonilla Grajales and Rodrigo Cibils

Patagonian Mobile DEC outlined the most relevant guidelines for Developers, Technical Leaders, Architects, and Project Managers involved in mobile app development. This blogpost provides valuable information for estimating, executing and delivering mobile solutions.?

Cracking the code: strategic steps for hybrid app success!?

Embarking on the development journey for a hybrid app (e.g. React Native, Flutter) destined for both Android and iOS platforms?

Even if the launch dates are different or far from each other, it is recommended to address the development for both platforms at the same time. Here's the blueprint for a seamless process:

• Simultaneous development: Break away from the old norm of prioritizing one platform over the other. Simultaneous development for both Android and iOS is the secret sauce to ensure your app features shine across the board. Don't risk the "lost in translation" scenario – embrace the power of hybrid technology.

• Revamping existing Apps: if you're dealing with an existing app, check its submission date. If it's been more than a year, it's time for a tech makeover. Update libraries and features to comply with the latest store requirements, ensuring your app stays at the top of its game.

Developer account Prep: before setting sail, ensure the app owner (your client) secures Apple and Google developer accounts. Be prepared for a process that might demand some paperwork, especially for organizational accounts.

You could read more in these guidelines?

1. Google requirements: required information to create a Play Console developer account?
2. Apple requirements: enrolling, verifying, and renewing with the Apple Developer app

• Global App strategy: define the app's global reach by considering not only software architecture and features but also business goals and user data processing. Navigate legal landscapes including, for example, GDPR for user data privacy in Europe and USA Medical Regulations. European GDPR for user data privacyUSA Medical Regulations

• Android SDK Policies Mastery: make sure to check the Android's target SDK policies. Updated every August 31st, the current requirements demand new apps target Android 13 (API level 33) or higher. Existing apps need to target API level 31 or above for continued availability on newer Android OS versions.?

How to submit your App to stores?

Ready to unveil your masterpiece to the world? Here's your backstage pass to a seamless submission process:

• Time to setup: either for Google or Apple, once the Developer Account is created, the following step is to create the app’s profile page and complete required forms (e.g. Government app declarations, Financial Features declaration, Privacy declaration, etc.)

• Internal testing kickoff! Don't keep your audience waiting! Try to submit your app for Internal Testing on Google Play and Test Flight on App Store Connect as soon as the first feature is usable. This sneak peek ensures a smoother final release, eases testing, and unveils potential store restrictions early on.

• Do periodic submissions: make your moves count with periodic submissions during the project's development. Catch issues early, courtesy of the Store's automated review. It's like having a rehearsal before the big show, ensuring your app steals the spotlight.

• Project estimation: when estimating, leave 1 or 2 sprints after the final store submission for fixing bugs and/or issues that the store could potentially report.

• The Grand Premiere: set a date, plan the development, and consider a minimum of 2 weeks or more for your app to dazzle the audience in the stores. This is your red carpet moment – make it count!

Pro Tip: Google hints at a new requirement – Individual Developers with newly created personal Play Console accounts will soon be required to test their apps with at least 20 people for a minimum of two weeks before applying for access to production.?

Meet Apple and Google's requirements for a show-stopping performance!

Before the curtain rises, ensure your app's attire is on point – work with a designer to craft the perfect logo, icons, and app-preview designs. This could take some time and working together with a designer is advised. Also, make sure that those assets meet the specified dimensions, formats, and other requirements from Apple and Google.

You can find lots of resources in these guidelines?

1. Apple Icons: Apple Human Interface Guidelines
2. Apple App Previews
3. Android Icons: Android Icon Design Specifications
4. Android Design Guidelines for Icons, App Previews, Screenshots, among others.?

Legal requirements for mobile apps

When your App includes user info (the likes of email or name) stores will ask for a Privacy policy.?

• Pro tip for privacy policies: Start early because drafting these policies take time and it would be advisable to count with an attorney in your team to deal with this step.??

• Ideally the Privacy Policy text should list which app permissions you are going to request,? why they are needed and how the information will be used.
• It should also include which user information is being gathered and how it is stored and used.

• Terms of use: The App Code of Conduct! It's not just a set of rules; it's the law of your app kingdom. Make sure your users know the deal – what's allowed, what's not, and the consequences of crossing the line.

• Accessibility is Key! Privacy Policy and Terms of Use should be accessible through your mobile app. It could be a screen dedicated to it or it can be just a link that redirects to the documents on the web. The important thing is that it must be accessible through the mobile app. The links must also indeed contain the Privacy Policy and they must be the same links that are registered on the Stores app submission forms.

• Cybersecurity tip: don′t submit analytics with unnecessary data! you should not send sensitive and/or unnecessary data with analytics. For example: email, name, and/or other sensitive information.

How do you deal with App Permissions?

When a permission is requested on the app, there should be an explicit text/modal/dialog that tells the users that a permission request will appear on their phones and they will be prompted to accept or deny those permissions. Examples of permissions are: Location, Notifications, Camera. This text/dialog/modal that shows up before the permission request should specify why that specific permission is requested and how that data will be used.

Note for iOS: on the native permission modal, the purpose of the permission should be specified too. This is made on the Info.plist file. See more about native permission modal.?

Apple Sign In for social logins

IOS has special requirements for Apps that use a third-party or social login service, if your app uses a third-party or social login service to authenticate or set up the user's primary account with those social logins you must also offer Sign in with Apple as an equivalent option.?

This will happen when using social logins such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login. For more information you could check the app-store guidelines for developers.?

Bear in mind that you must include this information in your Privacy Policy.

Create and Delete an Account in-app

If the App offers the possibility to Log In, then it must also offer the possibility to cancel/close/delete within the app. For this case, it doesn’t necessarily need the whole process to be in-app, for example, it could be just a button or link that will trigger an email to the user and the user clicks to confirm they want to cancel their account.

Authenticated flows in the App

Sometimes, Apple raises concerns when the entire functionality of the app relies solely on authentication, particularly when users are unable to access a feature unless they create an account and log in. If all the features of the app are usable only with an account, Apple may ask you to justify this choice. If they disagree, they will reject your app.

For example: If you submit an eCommerce app that requires people to create an account to use it, Apple will reject your app saying that people should be able to see and search for products without creating an account or logging in, and you as the creator of the app shouldn’t need to have people’s data to allow them to see products. It’s understandable for example, that for writing a review for a product or purchasing it, the user should create an account.

When submitting the App to the Stores, you must provide user credentials (email and password) that they can use to log in to the app to access and test authenticated flows.?

In-App Purchases & Payments

If an app includes In-App purchases, sometimes Apple will force you to use their payment platform in your App.

Don't redirect users to external payment systems - it's a violation of App Store policies.

This includes subscriptions, game currency, and access to premium features. The use of third-party payment platforms in iOS apps (like PayPal) is prohibited.

Apple will have a cut of 30% of your earnings through the app too, so take that into account when calculating your prices to the public. There are a lot of apps that have their own payment system and they are not required to do this. Take into account that those apps are often ecommerce platforms or other types of platforms in which you are not paying for the app itself or advanced features of the app, as they refer when saying “subscriptions, game currency, and access to premium features.” You are most probably paying for products or services which are offered through the app.

• In general terms, everything related to payments should be analyzed deeply before making any decision or planning any development.

Ready to develop your app? Our team at Patagonian is here to choreograph the perfect routine to ensure the best flow. Contact us for further details.