Uber clone (JavaScript Mastery)

javascript-mastery‘s build-along project: “Build a full-stack Uber Clone Application with Expo’s latest features and lightning-fast edge-ready Postgres database in React Native.” 1.9k stars, 692 forks as of 2026-08-09; no license stated in the repository. The teaching is a free step-by-step YouTube tutorial, and this repository is its companion code. Parked in the hub _inbox on 2026-06-28 under app-build-tutorials, five weeks before this spoke existed; routed here 2026-08-09.

What it teaches

A ride-hailing app, feature by feature: registration and onboarding, email/password auth with verification, Google OAuth, live location with map markers, Google Places autocomplete, ride discovery by origin and destination, vehicle selection on the map, ride confirmation, Stripe payment, booking after payment, profile management and ride history — “15+ features,” built for iOS and Android.

The stack is React Native and Expo, PostgreSQL (Neon), Clerk, Stripe, Google Maps, zustand and Tailwind. Stated prerequisites are Git, Node.js and npm, a basic understanding of React Native, and API keys from five services — Clerk, Stripe, NeonDB, Google Maps and Geoapify. The README’s own word for the approach is “beginner-friendly.”

The fourth form: the clone

Not a meta-curriculum — nothing here points at other people’s material. Not an executable-curriculum in the nirdiamant-prompt-engineering sense either, where each lesson is a notebook demonstrating one idea. It is a single application, reproduced end to end, with the teaching in a video and the repository standing as the answer key (clone-project).

The interesting part is what the reproduction consists of. ai-engineering-from-scratch is this spoke’s other build-it curriculum, and its rule is implement the thing by hand before you use the library. This one is the exact inverse: nothing is implemented by hand. Authentication is Clerk, payments are Stripe, the database is Neon, the map is Google, geocoding is Geoapify. What the learner actually practises is wiring five vendor SDKs together and shipping the result — the skill is integration, and the app is the artifact.

Both are honestly described as building something. They teach opposite things, and the spoke’s existing vocabulary — curation versus construction — does not separate them. From scratch and from services are both construction.

What stands in for the exam

There is no ride-hailing interview. What this curriculum points at is not an assessment but a demonstrable artifact: at the end you have an app that looks like a product, which is a portfolio object. That is the third shaping force developer-roadmap introduced — the labour market acting through what it names and rewards rather than through what it tests — showing up in a different form. A roadmap is organized by job title; a clone is organized by the product a job title is expected to be able to build.

Filed as consistent with the narrowed claim in synthesis rather than as a test of it. There is no exam, so it says nothing about scope; it is evidence about what fills the gap when no exam exists.

Weaknesses worth recording

• Five API keys is five external dependencies. A meta-curriculum decays by link rot and an executable one by dependency drift. A vendor-integration tutorial decays faster than either, because free tiers, SDK majors and console UIs all move independently of the author. Nothing here is pinned or dated.
• The stars measure the wrong artifact. 1.9k stars is the smallest number in this corpus by two orders of magnitude, and it counts the answer key rather than the teaching, which lives on YouTube and has no figure recorded here. Treat it as a floor, not a size.
• No license. The repository states none, which formally leaves the code unlicensed and makes the “reuse this in your portfolio” premise legally unsettled — a detail this spoke should watch for in build-along material generally.
• No outcome data, as everywhere else here. The claim that beginners finish this and can build an app is untested.

T3 — a self-published teaching artifact whose claims about its own effectiveness are the author’s, from a channel whose business is teaching.