Planned

Up Next

In Progress

Features

Roadmap

<ul><li>Generic authentication driver</li><li>Starts off with mock implementation<ul><li>Can also be hooked up to a custom implementation</li></ul></li><li>Merge a specific auth plugin to hook it up to an actual universal auth provider, e.g.<ul><li>with/auth-clerk → (✅ done)</li><li>with/auth-work-os → (📆 planned)</li><li>with/auth-supabase → (📆 planned)</li></ul></li><li>Follows the “workspace driver“ pattern:<ul><li>Import auth essentials from `@auth/driver` (workspace)<ul><li>useAuth(), useUser(), useOrg()</li><li>&lt;UserButton /&gt;, &lt;OrganisationSwitcher /&gt;</li><li>&lt;UserProfile /&gt;, &lt;OrganisationProfile /&gt;</li><li>…</li></ul></li><li>Can config / app / swap actual implementations without changing app code</li></ul></li></ul>

In Review

[Plugin] - More options for '@auth/driver' (1/3)

Thorr Stevens

<ul><li>Generic database driver</li><li>Starts with mock / memory implementation (will warn you)<ul><li>Can also be hooked up to a custom implementation (e.g. → REST API)</li></ul></li><li>Merge a specific DB plugin to hook it up to an actual Database Solution, e.g.<ul><li>with/db-mongoose → ‘@db/mongoose‘ → (✅ done, but to be published)</li><li>with/db-supabase → ‘@db/supabase‘ → (📆 planned)</li><li>with/db-drizzle → ‘@db/drizzle‘ → (📆 planned)</li><li>with/db-convex → ‘@db/convex‘ → (📆 planned)</li><li>…</li></ul></li><li>Follows the “workspace driver“ pattern:<ul><li>Import DB essentials from <code>@auth/driver</code> (workspace)<ul><li>Create / Import DB models with common interfaces from Zod schemas<ul><li>insert(), insertOne(), insertMany(), …</li><li>find(), findOne(), findMany(), …</li><li>update(), updateOne(), updateMany(), …</li><li>delete(), deleteOne(), deleteMany(), …</li><li>findOrCreate(), upsertOne(), …</li><li>…</li></ul></li></ul></li><li>Can config / add / swap actual implementations without changing app code</li></ul></li></ul>

[Plugin] - Add @db/driver options (1/4)

Plugin to use WorkOS as the auth provider

[Plugin] - @auth/work-os

Add a preview plugin to upgrade from Expo SDK 52 (default) → 53 After a few months of stable tests, we’ll merge this to make SDK 53 the default

[Plugin] - with/expo-sdk-53

<ul><li>Preview plugin branch for the upcoming Nativewind V5</li><li>More info &amp; migration guide: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.nativewind.dev/blog/v5-migration-guide">https://www.nativewind.dev/blog/v5-migration-guide</a></li></ul>

[Plugin] - with/nativewind-v5

Add a preview plugin to add Zod V4 support (next to the default of Zod V3) Introduce a similar pattern to zod itself, where you can still choose which version to use based on which folder segment you import from After a few months of stable tests, change the default to be Zod V4 instead of V3

[Plugin] - with/zod-v4

Add a preview plugin to upgrade from Next.js 15.0.4 (default) → 15.4 After a few months of stable tests, we’ll merge this to make Next.js 15.4 the default

[Plugin] - with/nextjs-15.4

Add Mongoose as a NoSQL Database driver and plugin option.@[Plugin] - Add @db/driver options (1/4)

[Plugin] - @db/mongoose

Plugin for using <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://datafa.st/">DataFast</a> as an analytics and tracking plugin

[Plugin] - @analytics/datafast

Plugin to use PostHog for analytics and tracking

[Plugin] - @analytics/posthog

Plugin to use Polar as the payments solution

[Plugin] - @payments/polar

Adds an ‘npm collect:drivers‘ script<ul><li>Scans for `{driverName}.{driverType}.ts` files</li><li>Searches within ‘/drivers/‘ directories</li></ul>Supported {driverType} values:<ul><li>db - Data persistence (e.g. → ‘@db/mongoose‘)</li><li>auth - Authentication (e.g. → ‘@auth/clerk‘)</li><li>files - File Storage (e.g. → ‘@files/uploadthing‘)</li><li>email - Sending emails (e.g. → ‘@email/resend‘)</li></ul>Provider selection is configured in ‘@app/config’<pre><code>{
 db: 'mongoose', // from options 'mongoose' | 'supabase' | ...
 auth: 'clerk', // options 'clerk' | 'supabase' | 'workos' | ...
}</code></pre>Driver packages ‘@{driverType}/driver’ re-export the selected provider’s core modules:<ul><li>‘@db/driver‘ → insert / update / delete methods from ‘@db/mongoose‘</li><li>‘@auth/driver‘ → SignIn / SignUp / useUser() / … from ‘@auth/clerk‘</li><li>All driver options must conform to a common driverType structure, enforced with Zod</li></ul>Key Benefits<ul><li>❇️ Uses Zod to ensure a common interface for driver options<ul><li>Alternative to just Typescript for enforcing the driver “contract”</li></ul></li><li>❇️ Swapping providers becomes a config change, not a rewrite<ul><li>Business logic stays mostly untouched</li></ul></li><li>❇️ You can still use the drivers separately by importing from them directly<ul><li>e.g. ‘@db/mongoose‘ instead of ‘@db/driver‘ in some places</li><li>Enables you to use different provider if required<ul><li>e.g. during a migration to a new provider</li></ul></li></ul></li></ul>🚧 Caveats <ul><li>The architecture and script supporting this workspace driver architecture are finished,</li><li>BUT, most of the actual drivers are still in progress:<ul><li>@[Plugin] - @db/driver </li><li>@[Plugin] - @auth/driver </li></ul></li><li>You can already add your own custom drivers if you think this is an interesting approach<ul><li>Have a look at ‘mock.db.ts‘ as an example</li></ul></li></ul>

Completed

[Portability] - Workspace Drivers Architecture

<ul><li>Setup and Automations to ensure features are super portable between projects</li><li>Using monorepo workspace folders as the ideal unit of “copy-pasteable“ work</li><li>Saves you a lot more time in the long run:<ul><li>❇️ Stop reinventing the wheel, just drag and drop between projects</li><li>❇️ No more annoying patchwork to be done after copy-pasting</li><li>❇️ Forces you to think about features in a reusable way (optional)</li></ul></li><li>More info: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://fullproduct.dev/docs/project-structure">https://fullproduct.dev/docs/project-structure</a></li></ul>

[Portability] - Reusable Features Architecture

<ul><li>Expand the list of Turborepo Generators:<ul><li>❇️ npm run add:route → New universal route &amp; screen + link to data-fetcher?</li><li>❇️ npm run add:resolver → Add new API route &amp; GraphQL resolver</li><li>❇️ npm run add:form → Add new Form State Hook</li></ul></li><li>All linked / linkable to the same resolver (DataBridge or input / output schemas)<ul><li>Interactive terminal UI to pick the destination / schema / resolver / …</li></ul></li><li>Single Source of Truth = Nothing gets out of sync, e.g.<ul><li>Recommended Workflow 💡<ol><li>❇️ Gen new schema → e.g. ‘/schemas/Post’</li><li>⚙️ Turn schema into DB model → e.g. ‘/models/Posts’<ul><li>Reuse ‘Post’ schema to create typed DB model</li></ul></li><li>❇️ Gen new resolver → e.g. ‘getPost.resolver.ts‘<ol><li>Reuse ‘Post’ schema as (DataBridge) output</li><li>Reuse ‘Posts‘ model in actual business logic</li><li>Choose option to also generate fetcher fn</li></ol></li><li>❇️ Gen new route → e.g. ‘/posts/[id]‘ → &lt;PostDetailScreen /&gt;<ul><li>Choose option to pick `getPost()` as initial data provider</li></ul></li><li>❇️ Gen new form → e.g. `useUpdatePost()`<ul><li>Pick `Post` schema option to create form state hook for</li></ul></li></ol></li><li>Updating the ‘Post‘ schema will now automatically update all the rest</li></ul></li></ul>

[Plugin] - Route, Form & API Generators

<ul><li>An official CLI to help you:<ul><li>Create new universal apps from your starters<ul><li>Because who starts new projects from the GitHub UI?</li></ul></li><li>Easily install git-based plugin branches and PRs<ul><li>Enables a pick-and-choose stack</li></ul></li><li>Sync your repo post-creation to attach the starter’s git history<ul><li>Enables easier updates from the starter through git pull</li></ul></li></ul></li></ul>

[CLI] - npx @fullproduct/universal-app

<ul><li>Adds automatic Nextra MDX docs generation from schemas</li></ul><pre><code>npm run regenerate:docs</code></pre><ul><li>Automatics MDX docs for<ul><li>Schemas (if put into a /schemas/ folder OR named .schema.ts)</li><li>Resolvers (using DataBridges → linking Input &amp; Output schemas to logic)</li><li>Components (using Prop schemas → getDocumentationProps)</li></ul></li><li>Picks up additional developer notes or custom docs<ul><li>Look for {subject}.docs.mdx files</li><li>If {subject} matches a schema / resolver / component with auto-docs<ul><li>Add the contents of .docs.mdx to the resulting Nextra MDX doc</li></ul></li><li>If {subject} is not one of the above, create its own Nextra MDX doc page</li></ul></li><li>Also sets the project up with `@app/docs` workspace<ul><li>Includes all the official docs from <a target="" rel="noopener noreferrer nofollow" class="link" href="https://fullproduct.dev/docs">fullproduct.dev/docs</a></li><li>/pages/ dir = Destination for all auto-generated docs</li></ul></li><li>✅ Easy onboardings and handovers </li><li>✅ Docs will automatically grow as you build new features</li></ul>

[Plugin] - with/automatic-docs

<ul><li>Adds the `with/nativewind` plugin branch to our universal base starter (mini)</li><li>Includes Nativewind as the default styling option for demo and premium starter</li></ul>

[Essentials] - with/nativewind

<ul><li>The minimal universal base starter, demo and premium starters share git history</li><li>Meaning you can upgrade and update from each by using git fetch and git pull</li><li>Will add @[CLI] - @fullproduct/universal-app to attach git history even to:<ul><li>Custom starters you add yourself (e.g. in-house solution)</li><li>Repos generated from the GitHub UI (e.g. template repo button)</li></ul></li></ul>

[Updates] - Maintain shared git history

<ul><li>Automatic GraphQL API → From linking Zod Input / Output schemas to resolver logic<ul><li>Creates ‘schema.graphql’ type &amp; input defs from linked resolver zod schemas</li><li>Automatically collects and links resolvers to their i/o schemas (👇)<ul><li>Builds an executable schema from them</li></ul></li><li>Sets up an `/api/graphql` endpoint using the Executable schema</li></ul></li><li>Fetchers automatically build their graphql query string from schemas as well<ul><li>Uses the Zod input &amp; output schemas (DataBridge) as Single Source of Truth</li><li>Automatically validates inputs → Executes the linkes resolver logic</li></ul></li><li>Basically, MOST of the GraphQL benefits without ANY of the hassle<ul><li>✅ Strictly typed API contract between front-end &amp; back-end</li><li>✅ Auto-documented API layer (using zod descriptions, etc.)</li><li>🙌 Never manually maintain graphql defs</li><li>🙌 Never manually write query definitions</li><li>🙌 Nothing can / will ever get out of sync this way</li></ul></li><li>More info: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://fullproduct.dev/docs/data-resolvers">https://fullproduct.dev/docs/data-resolvers</a></li></ul>

[Essentials] - Automated GraphQL API

<ul><li>Fetch data with ’@tanstack/react-query’ on server / browser / mobile</li><li>createQueryBridge()<ol><li>routeDataFetcher = Fetcher Function to use with react-query</li><li>routeParamsToQueryKey = Map route params to query key</li><li>routeParamsToQueryInput = Map route params to fetcher fn inputs</li><li>fetcherDataToProps = Map the resulting data to props</li></ol></li><li>&lt;UniversalRouteScreen/&gt;<ul><li>executes the queryBridge fetching steps automatically in each env</li></ul></li><li>More info: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://fullproduct.dev/docs/data-fetching">https://fullproduct.dev/docs/data-fetching</a></li></ul>

[Essentials] - Universal React-Query

<ul><li>Allow you to provide custom routers, link components, etc. through context</li><li>Ensures common reusable components are not tied to a specific framework</li><li>Meaning you can reuse your components outside of just Expo and Next.js<ul><li>Requires you to add a custom Link / useRouter / etc. in UniversalAppRouters</li></ul></li></ul>❇️ More info in this video by Jack Herrington:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.youtube.com/watch?v=yi8UCnXPu8U">https://www.youtube.com/watch?v=yi8UCnXPu8U</a>

FullProduct.dev ⚡️ Universal Starterkit

Roadmap