Chrysolites Tech Academy

Short-Video App with React Native and Supabase · Course book

Chapter 18: Shipping to the Stores

Pairs with Lesson 18: Submitting the App to the App Store

Finishing the code is not the same as shipping an app. Before an app reaches the App Store or Google Play, it must pass a review against each store's guidelines, and apps that host user-generated content, such as videos, comments and chat, face some of the strictest rules, because they can expose people to harmful material. Apps that look like copies of existing products are also rejected. This chapter explains what reviewers look for and how to prepare: making the app distinct, building the safety features that user content requires, writing terms and a privacy policy, managing users' data, building and submitting with Expo's EAS tools, and handling a rejection calmly, with version and build numbers worked through by hand.

Making the app your own

Stores reject apps that copy the look, name or branding of existing apps, and apps that offer little beyond what many others already do. A tutorial project that recreates a famous app's design is a fine way to learn, but submitting it as it is invites rejection. Making it distinct is partly about legal safety, avoiding others' trademarks and designs, and partly about giving users a reason to choose it.

Practical changes include an original name and app icon, its own colours and login screen, and above all a distinctive purpose. One effective idea is to make the app private: a friends-only space where short videos are shared only with mutual followers, rather than a public feed for strangers. That changes the product meaningfully, suits people who want to share with a close circle, and reduces moderation risk, because content is seen only by people who chose each other.

The App Store requires an icon of 1,024 × 1,024 pixels, from which the system produces smaller sizes. Icons should be simple, recognisable at small sizes and free of text that becomes unreadable when shrunk. Expo reads the icon and splash screen from app.json and generates the platform-specific versions at build time.

Safety features for user-generated content

Apple's guidelines for apps with user-generated content require specific protections, and Google Play has comparable policies. Reviewers test for them, often by looking for the controls on a video or profile.

RequirementWhat it means in this appHow it is built
A way to report contentA "Report" option on every video and commentInsert a row into a reports table with the item, the reason and the reporter
A way to block abusive usersA "Block" option on profilesA blocks table; blocked users' content is filtered from feeds, comments and chat
Filtering objectionable materialHolding back clearly unacceptable contentWord filters on text, and review of reported items
Timely action on reportsSomeone reviews reports and removes violating contentA simple moderation view and a commitment to respond promptly
Published contact detailsUsers can reach the developerA support email or page in the app and the store listing

Users must also agree to terms of use that forbid objectionable content and abusive behaviour, usually shown at sign-up with a checkbox or a clear statement that continuing means accepting them. Blocking should take effect immediately and be reflected in every query that shows other people's content, which is easiest when the database applies it, for example by excluding blocked users in the queries or policies that return videos, comments and messages.

Privacy, data and account deletion

Both stores require a privacy policy: a public web page explaining what data the app collects, why, how long it is kept and who it is shared with. A short-video app collects account details, uploaded videos and photos, messages and usage data, and it uses third-party services such as its back-end provider, all of which the policy should describe honestly. The store listings also ask developers to declare the data collected, presented to users as privacy labels or a data safety section, and these declarations must match what the app actually does.

Apps that let people create an account must also let them delete it from within the app, not only by emailing the developer. Deleting an account should remove the user's profile, videos, photos, comments, likes, follows and messages, or anonymise what must be kept, and sign them out. Because the account itself lives in the authentication service, deletion is usually done by a trusted server function, such as an edge function using the service key, which the app calls after the user confirms. Cascading foreign keys in the database make the clean-up reliable.

Permission descriptions, the sentences shown when the app asks for camera, microphone and photo library access, are checked too. They must explain clearly why each permission is needed. Vague text such as "This app needs your camera" is a frequent reason for rejection; "Record videos to share with your friends" is clear.

Building and submitting with EAS

Expo Application Services, EAS, builds and submits apps from the command line. eas build compiles the app in the cloud for iOS, Android or both, using build profiles defined in eas.json, such as development, preview and production. It manages signing credentials, the certificates and keys that prove a build comes from you, and can create them automatically. eas submit then uploads a finished build to App Store Connect or the Google Play Console, from which it is sent for review.

Prepareeas buildeas submitReviewRelease icon, policies,safety featuresproduction buildupload to storesguidelines checkto users rejected? fix, raise the build number, rebuild and resubmit
Figure 18.1 — The release pipeline. A rejection sends you back to fix the issue and build again with a higher build number.

Every upload needs a version that users see, such as 1.0.0, and a build number that must increase with every upload, even for the same version. EAS can increment build numbers automatically.

Worked example. The first submission is version 1.0.0, build 1. It is rejected because reporting is missing from comments. After adding it, the resubmission must be at least build 2; the version can stay 1.0.0 because users never saw build 1. After release, fixing a bug is version 1.0.1, build 3; adding the friends feed is a feature release, version 1.1.0, build 4; and a redesign that changes how the app works might justify 2.0.0. The version describes the change to users, while the build number only ever counts upwards, so the store can always tell which upload is newest.

The store listing needs a description, keywords, a category, screenshots of the main screens, an age rating questionnaire and contact details. For apps that require signing in, reviewers need a demo account with some content, provided in the review notes, so they can test everything, including reporting and blocking.

Before public release, both stores offer testing tracks. On iOS, TestFlight distributes builds to invited testers, first to your own team and then, after a lighter review, to external testers by email or a public link. On Google Play, internal, closed and open testing tracks do the same, and new developer accounts may be required to run a closed test with a minimum number of testers for a period before they can publish to everyone, so check the current rules early. A week of real people using the app on their own phones finds problems that no amount of solo testing will, from confusing screens to crashes on particular devices.

Android has a few differences worth knowing. Google Play uses an app bundle format, which EAS produces for production builds; the listing needs a feature graphic as well as screenshots; and the data safety form plays the role of Apple's privacy labels. The same safety features for user content apply, and Google Play also expects a clear way to report content and users. Preparing both stores' requirements together, from one checklist, avoids discovering a missing item at the last minute.

Handling rejections

Rejections are common, especially for a first app, and they are a normal part of the process rather than a failure. The rejection message cites the guideline that was not met and often describes what the reviewer saw. Read it carefully, fix exactly that issue, and reply in the review system explaining what changed and where to find it; if you believe the reviewer misunderstood something, a polite explanation with steps to see the feature often resolves it. Keeping a checklist of the requirements in this chapter, and testing each one before submitting, avoids most rejections in the first place. Once approved, keep the safety tools working and the policies current, because later updates are reviewed too.

Practice tasks

  1. Version 1.2.0 build 9 is released. Give the version and build numbers for a bug fix, then for a new feature, then for a resubmission after that feature is rejected.
  2. List the five safety features this chapter describes for user-generated content and where each appears in the app.
  3. Explain why account deletion is usually performed by a server function rather than directly by the app.
  4. Rewrite this permission description to be acceptable: "We need access to your photos."
  5. What should the review notes include for an app that requires signing in?
  6. Describe two ways to make a tutorial clone distinct enough to submit as your own app.

Install Chrysolites Tech Academy

Android / Chrome / Edge: open the browser menu and choose Install app or Add to Home screen.

iPhone / iPad (Safari): tap the Share button, then Add to Home Screen.