Skillnaija Start free

Build Your Own App for a Real Person, and Put It in Their Hands

The capstone project for Build Your Own Mobile App: React Native and Expo, from Your Phone to Google Play — a free Data & Tech course. Pass it and you earn a certificate anyone can verify.

Start the course free Download the project workbook

The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.

What you will submit

One Google Doc link (anyone with the link can view) containing: the public GitHub repository URL; the Play closed-test opt-in link or EAS APK link (route C needs no extra link; a saved Expo Snack link is optional); the demo video link (YouTube unlisted or Google Drive); the privacy policy and account-deletion page URLs (required for A and B); the real-user test notes; and the AI log or a pointer to it in the README. Plus four to eight phone screenshots uploaded as evidence. The examiner opens the repository, the video and the links.

What to do, step by step

  1. Your app, your idea. Build the records app you planned on your Record Card in Lesson 1, for a real person or group you can name (a trader, a thrift group, a tailor, a school, a church). It must not be SabiSell renamed: a different record, your own fields, your own labels and your own user. Projects that are the course example with the names changed fail.
  2. Part 1. The eight parts. Your app must have: (1) a list of records, each with at least four fields from your Record Card; (2) a form to add and edit a record, with validation and the right keyboard for numbers; (3) a details screen with delete-with-confirmation; (4) search or a filter, plus one total or count that answers your user's real question; (5) a photo on a record, or, if your Record Card has no photo field, a second share format and one sentence saying why; (6) share a record as text to WhatsApp; (7) records that survive closing the app and work with the network off; (8) sign-in and cloud sync to your own Supabase project, with row-level security so one account cannot see the records of another, and an in-app Delete my account.
  3. Part 2. One feature you built with AI (Lesson 11), and your AI log: at least five entries saying what you asked, what the AI got wrong or invented, and how you checked it. Using AI is expected; hiding it, or submitting code you cannot explain, is not.
  4. Part 3. Real-user test (Lesson 12): test on a real Android phone (the cheapest you can borrow) with at least 200 records, and note the model, Android version, RAM if known, how long the app takes to open, and whether the list scrolls smoothly. Show the app to at least three real people from your user group; write down their top feedback and the two changes you made because of it.
  5. Part 4. Your code: put the code in a public GitHub repository (uploading the files from your phone's browser is fine). Include a README.md with your Record Card, what the app does, how to run it, your SQL table and security policy, and the AI log. No secret keys: the Supabase publishable key is allowed because your security policy protects the data; a secret or service-role key in the code fails the security criterion. If you built it in My app (the in-lesson preview), use Copy this file or Download my app (.zip) to put every file in the repository.
  6. Part 5. Distribution, choose ONE and say which: (A) Google Play closed test: your app in a closed-testing track, with the opt-in link and a screenshot of the testers page; or (B) an APK built with EAS Build: the install link and a photo or screenshot of it installed on a tester's phone, plus your written store-readiness checklist (privacy policy URL, account-deletion page URL, Data Safety answers); or (C) phone-only: your public GitHub repository holding your app's files from My app (the Skillnaija in-lesson preview), your demo video, and the store-readiness checklist (a saved Expo Snack link is optional). A, B and C can all pass; A and B earn more of the distribution marks.
  7. Part 6. Demo video: a screen recording of two to three minutes on a real phone showing every one of the eight parts, including turning on airplane mode, adding a record, and syncing when back online. Upload it to YouTube (unlisted) or Google Drive (anyone with the link can view).
  8. Submit one link: a Google Doc (anyone with the link can view) listing the GitHub repository, your distribution link (A, B or C), the video link, the privacy policy and deletion page links if you made them, and your real-user test notes. Upload four to eight screenshots of your app on your phone in the evidence boxes.

Files to work with

Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 8 KB

How it is graded

CriterionWeight
The app works on a real phone: list, add and edit form with validation, details with confirmed delete, search or filter and a correct total, with no crash in the demo25%
It is the learner's own app for a named real user: the record, fields, labels and total follow their Record Card and are clearly not the SabiSell example renamed15%
Offline-first and sync: records survive restart with the network off, sync to the learner's own Supabase project when back online, and row-level security keeps accounts apart; in-app account deletion works15%
Photo and WhatsApp share work, with permissions asked at the moment of use and a sensible message when refused10%
Real users and cheap phones: specific low-end test notes and three real users' feedback with two changes made because of it10%
Honest AI use: one AI-built feature the learner can explain, and an AI log that names at least one AI mistake and how it was checked10%
Code and README: public repository, Record Card, run instructions, SQL and security policy, readable code, no secret or service-role keys7%
Distribution: route A (Play closed test) full marks, route B (EAS APK installed on a tester's phone plus store-readiness checklist) most marks, route C (phone-only: the app from My app in the repository, plus checklist) some marks8%

You need 65% overall to pass. A human examiner also reviews this safety-critical project before any certificate is issued. A failed submission comes back with feedback and can be revised and resubmitted once free; further attempts come with the All-Access Pass or as a paid retake.

Before you submit: make your link public

If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.

Frequently asked questions

Do I have to finish Build Your Own Mobile App: React Native and Expo, from Your Phone to Google Play before submitting the project?

Yes. The submission screen opens once every lesson in Build Your Own Mobile App: React Native and Expo, from Your Phone to Google Play is marked complete. The lessons are where the methods, the local context and the worked examples the project depends on are taught.

How is the project graded?

An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Because this is a safety-critical trade, a human examiner also reviews every submission before a certificate is issued.

Can I resubmit if I fail?

Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.

What do I actually submit?

A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 8 steps.

Is the certificate real?

Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.

More Data & Tech projects

Ready to earn this certificate?

Build Your Own Mobile App: React Native and Expo, from Your Phone to Google Play is self-paced. Finish the lessons, complete this project, and the certificate is yours to share.

Start learning free