Native mobile and desktop apps from one description

From a description of what you need, Builder Apps generates native apps for iOS, Android, macOS, Windows, and Linux that install on a device and keep working offline.

Get early accessView all products

Native apps from a description

Builder Apps produces software that installs on a device, has its own icon, and can work offline. From one description, Beryl Agents generate versions of the app for iOS, Android, macOS, Windows, or Linux. You can test the app in a device preview and adjust it before you submit it to the app stores or distribute it inside your organization. Your team can produce the iOS and Android versions from one description, while Beryl Agents take care of the details that differ between the platforms.

Get native apps for iOS, Android, and desktop from one description

Builder Apps generates a native version of your app for each platform that you pick, all from one description. The steps below follow an app from that description to its release through the app stores or inside your organization.

What your app can do on each device

One description, every platform

A native app built by hand usually takes an iOS specialist, an Android specialist, two codebases, and a release that each app store reviews separately. For an internal tool, an organization may decide that the cost is too high and keep the tool web-only.

When you describe your app once, Builder generates a native version for each platform that you target, so your iOS app, your Android app, and your desktop app all come from the same description. Beryl Agents follow the conventions of each platform, such as its navigation patterns and gestures, and meet the requirements of each app store.

Offline-capable by default

Your field workers, traveling sales staff, or rural clinic staff can lose their connection partway through a job. A web app can stop working at that point, because it needs a browser and a steady network.

A Builder app can store data on the device and sync it when the device reconnects. For example, a field inspector can fill in a report with no signal, after which the app uploads the report as soon as the phone is back online. The native runtime includes this offline storage.

Camera, GPS, biometrics, and push notifications

A web app can use the camera, push notifications, biometric sign-in, GPS, and the local file system only through the browser. As a result, the companies that build each browser set which of those features a web app can use on each phone.

Builder Apps generates native code that uses the device camera, sends push notifications, signs users in with biometrics, gets GPS coordinates, and works with the local file system. Your app asks for each of these features through the operating system's own permissions, as any native app does.

Data connections to Tables, People, and OneCloud

A mobile app usually needs a database, file storage, and a way to sign users in. If each of those is a separate service, your team will have to integrate it and manage another account for it.

Builder Apps can read and write data in Tables, use contact details from People, and store files in OneCloud. Builder connects your app to these products inside your Delalify workspace, so your app has a database, a contact directory, and file storage from the start if it needs them.

App store submission guidance illustration

App store submission guidance

Before Apple or Google will list an app, each company reviews the app's screenshots, its description, its privacy policy, and its compliance with the store's rules. If any of these misses a requirement, the store can reject the app, which means that you will have to submit it again.

Builder guides each submission to the Apple App Store and Google Play. Every generated app includes the metadata, privacy declarations, and screenshot templates that those stores require. You can distribute an internal app to your staff through enterprise distribution or a direct download link, with no app store involved.

What your team gains from native apps on Builder

Go native without platform specialists

Your team describes the app, while Builder generates the iOS, Android, and desktop versions with the differences between those platforms built in. Your team works in plain language, so it needs no Swift, Kotlin, or Electron skills.

Works without a connection

Field teams, traveling staff, and users in areas with weak coverage can keep using the app offline. The app syncs their data when the device reconnects, with no manual export or reimport.

Full device access

Your app can use the camera, push notifications, biometric sign-in, GPS, and the file system in the same way as any other native app.

Backend included when you need it

Your app can store data in Tables, look up contacts in People, keep files in OneCloud, and control access through Teams, with no outside service to configure. You connect only the products that the app uses.

How organizations use Builder Apps

Field inspectors who lose signal halfway through a site visit

A facilities management company sends inspectors to 50 sites per week. Each inspector needs a mobile app for photo documentation, checklists, GPS-tagged reports, and offline work at sites with poor signal. The operations manager describes the app to Builder, which generates an app that saves inspection reports to Tables and uploads photos to OneCloud when the phone reconnects.

Result

Inspectors complete each checklist on their phones, after which the app syncs the report, with its photos and GPS coordinates, once the phone reconnects. The operations manager reviews all 50 sites each week from a dashboard, so they no longer keep paper reports in a filing cabinet.

Field inspectors who lose signal halfway through a site visit

Dental front desk swaps clipboards for a lobby check-in tablet

A dental practice wants patients to check in on a lobby tablet, where they confirm their appointment, update their insurance details, and sign consent forms. The office manager asks Builder for an app with biometric confirmation, a photo capture for insurance cards, and a workflow that notifies the dental assistant through Channels when the patient is ready.

Result

Patients enter their own details on the tablet, so the front desk staff no longer type them in from a paper form. The app saves each insurance card photo to the patient's file in OneCloud, which spares the staff from scanning each card.

Dental front desk swaps clipboards for a lobby check-in tablet

Sales reps update deals from their phones between appointments

A sales team needs client profiles, meeting notes, and deal stages on their phones between appointments. The sales director describes to Builder a mobile CRM app that shows contacts from People and the conversation timeline from Channels, and that lets reps update deal stages from the parking lot. The app saves each change on the phone until the rep reconnects to a network.

Result

Reps update deal stages and log meeting notes between appointments, so they no longer save every update for the end of the day. The sales director builds each forecast from those updates, which the app syncs as soon as each rep's phone reconnects.

Sales reps update deals from their phones between appointments

Courier fleet with no proof of delivery for disputed stops

A delivery company needs each driver to see their route, mark each delivery complete, take proof-of-delivery photos, and record customer signatures. The fleet manager describes the app to Builder, which generates an app that stores delivery records in Tables, loads route assignments from the dispatch database, and uploads each proof-of-delivery photo to OneCloud with its GPS coordinates and timestamp.

Result

Drivers mark each delivery complete on their phones with a photo and a signature, while the dispatch team follows every delivery from a dashboard. When a customer disputes a delivery, the dispatch team can show the GPS-tagged photo and signature for that stop.

Courier fleet with no proof of delivery for disputed stops

Explore more of Builder

Sites

Builder generates marketing sites, dashboards, client portals, and SaaS interfaces from your description.

Learn more

Workflows

Drag triggers, branches, and approval steps onto a canvas to set what your Builder app does after each event.

Learn more

Components

Start each Builder project from ready-made blocks, a full template, or components from the gallery.

Learn more
View all Builder features

Put your app on your users' phones and computers

With early access, your team can generate its first iOS, Android, or desktop app from a description.

Get early accessView all products