Make client apps with BDK

Put iOS and Android apps in every proposal you send. Each client's web app becomes their own app: their users sign in over the page they opened, add a photo to a request, share a booking or listing, and come back without signing in again when a notification says something changed. The client keeps the accounts and the code; the build and the retainer stay with you.

01 / 05

Native sheets and screens

Present each client's sign-in as a native sheet over the page their user is on.

  • Open sign-in as a sheet when a user starts a request or booking.
  • Show sign-in over a shared property listing without losing the listing.
  • Return the user to the booking they started once the sheet closes.
  • Reuse the same sign-in flow in every client app you deliver.
Try it in the demo app

02 / 05

Camera and photos

Add camera input wherever a client's workflow needs a picture from the user.

  • Photograph a damaged item for a client's returns flow.
  • Capture a site issue in a client's field-service app.
  • Take a profile photo in a client's membership app.
Try it in the demo app

03 / 05

Share sheet

Let each client's users pass content out of the app to whoever needs it.

  • Share a listing, booking or request link from the client's app.
  • Send an invoice PDF from a client's billing app to the accounts team.
  • Send an event page to a friend from a client's events app.
Try it in the demo app

04 / 05

Push notifications

Bring each client's users back when something changes for them.

  • Notify a customer when their order or request moves forward.
  • Send a booking reminder from a client's scheduling app.
  • Open the right screen in the client's app when the user taps.
  • Alert a client's staff when a new enquiry arrives from the app.
Try it in the demo app

05 / 05

Saved login

Sign each client's users back in without asking for their password again.

  • Offer to save credentials after a user signs in to a client's app.
  • Sign them back in when they return to check a request.
  • Skip the sign-in screen when a user opens a client's app from a notification.
Try it in the demo app

Five of 71 native capabilities

The five above are the ones this kind of app leans on most. Every build ships with the whole set. Scroll the strip for the rest.

  • In-app purchases
  • Modal sheetsNew
  • Face ID login
  • QR scannerNew
  • Sign in with AppleNew
  • Live locationNew
  • Deep linksNew
  • App badgeNew
  • Incoming sharesNew
  • ContactsNew
  • Health dataNew
  • Audio playerNew
  • Voice recorderNew
  • Date-time pickerNew
  • Rating promptNew
  • Tracking promptNew
  • NFC scanNew
  • Native transitions
  • Photo pickerNew
  • Share sheetNew
  • Push notificationsNew
  • Saved loginNew

All features are included when you request a build with BDK. See pricing

What you set up

  • For each client: their Apple Developer and Google Play accounts.
  • Their Firebase project's service-account key and their OneSignal app.
  • Their Branch key and link domain. Agree who tests and who submits.

Where your web app stays in charge

  • Your client owns the code, hosting, logins, data and business logic you deliver.
  • Physical goods and services keep web checkout where allowed; digital goods use store billing where required.
  • Web updates go live without a rebuild when they use capabilities already in the app.
Can I work across frameworks or AI-built apps?

Yes. Add the SDK to each web app where you control the code.

Can clients keep ownership after handover?

Yes. Their accounts, their projects, their code.

Can every client app use the same feature set?

Choose features per project and check the build's reported capabilities before exposing them.

Create your project, or open the demo app and run the features yourself.