Web apps
Apps/Web apps/Web apps

Web apps

A web app is a Next.js app served at its own address, with the platform's models, actions, environments and Logs behind it and no Shopify in front. It signs its own users in.

What a web app is

An app whose platform is web is a folder like any other app: models in api/models/, actions beside them, and pages in web/, a Next.js App Router app that Inference Bureau builds and serves at <app>.inferencebureau.app (development at <app>--development.inferencebureau.app), or on a domain of your own. Pages read and write records in server code with createClient(); the browser reaches records only through the app's own route, as whoever is signed in.

What a Shopify app gets from Shopify, a web app brings itself: who the user is, how they sign in, and which records they may see. The starter has those working on the first sync, and the pages in this section say how each part works so you can extend it.

The starter

Every web app made on New app or with ib-apps create begins as the same starter: an app people sign in to, such as a portal, a tool or a members' area. Remove what you don't need; a page that needs no sign-in simply doesn't call requireUser().

ib-apps create ib-portal                  # the starter: accounts and sign-in
ib-apps create ib-list --recipe waitlist  # a complete app from a recipe, here a site with no accounts
The starter
Sign-inEmail and password, an emailed link, and Google or GitHub once you connect them. See Sign-in.
Modelsuser and session, and account, member and invitation for teams
Rolesunauthenticated and signed-in, which reads the user's own record; the pages' records route runs as it
PagesHome, sign-in, sign-up, forgot and reset password, verify email, the sign-in link, and web/app/(signed-in)/account
EmailReact Email templates in web/emails/: confirmation, password reset, the sign-in link
Shared codeweb/lib/auth.ts, email.ts, oauth.ts
Agent skillweb-sign-in

It sets integrations: ["resend"] in settings.ib.ts, so Problems says when email isn't set up, and comes with a test of its actions in tests/. The starter files lists every file; the styleguide is its look. A recipe (a waitlist, a class booking, a Slack bot) is a complete web app to start from instead; a recipe keeps the sign-in it was written with, or has none.

Until November 15, 2026 a web app could also begin as a Site, with posts, a contact form and a newsletter and no sign-in. Sites made then keep their files, and a development environment added to one copies development's files.

Against a Shopify app

Models, actions, files, environments, deploys, Logs, jobs, the API and the MCP server work the same on both platforms. What differs is who the app is for and what sits in front of it:

WebShopify
Who uses itYour users, or anyoneMerchants in their Shopify admin, and shoppers on the storefront
Sign-inThe app's own: a __Host-session cookie and web/lib/auth.ts. Google and GitHub through your own OAuth clientsShopify's: session tokens in the admin, the app proxy on the storefront
RecordsOne set per environment, for the whole app. A model that belongs to a user carries a user field, and the signed-in role's grants filter by it (the starter grants the user's own record)Scoped to the store: every call carries a shop, and roles reach only that store's records
Rolesunauthenticated, signed-inshopify-app-users, storefront-shoppers, storefront-customers, unauthenticated
IntegrationsResend, Google, GitHub, Sentry, 1Password, Inference Bureau modelsResend, Sentry, 1Password, Inference Bureau models
Webhooks and schedulesSchedulesSchedules and Shopify webhooks
Outside Inference BureauNothing to createA Shopify app per environment in your Partner organization, made for you
AddressThe app's own, or a custom domainInside the Shopify admin; the storefront through the app proxy

A web app can still call Shopify's APIs with a token of its own in a variable, and a Shopify app can have public pages. The platform decides how people sign in and where the app appears, not what the code may do.

In this section

  • Sign-in: the methods, the user and session models, currentUser and requireUser, the signed-in role, the account page, sign-in limits, Google and GitHub, and previewing as a user.
  • Email: the templates in web/emails/, development's emails in Logs, Resend for production, and the preview in Files.
  • Next.js on the platform: what a build ships, server code and route handlers, force-dynamic, NEXT_PUBLIC_ variables, the records route, uploads, CORS, and what the router in front adds and strips.
  • Going to production: the checklist before the first deploy, and what to watch afterwards.