Field service app
Build a field service or inspection app your crews will use
Field apps have a short list of hard requirements: addresses that become directions, forms that take photos and signatures, scans, and a phone that keeps working in a basement. Emberblocks has each of those built in as a field type or a block.
The field service template has jobs, technicians, customers, a dispatch board and a map, ready to open in the editor without an account.
Builders are always free. Facts about other products on this page were last checked on . Tell us if something is out of date: hello@emberblocks.com.
The field toolkit
Addresses and maps
The address field type autocompletes from Google, stores coordinates, and gives you distance and travel time in formulas. Jobs show on a map block; a button opens directions.
Signatures
A signature field captures a finger or stylus signature on the phone and stores it with the record.
Photos and scans
Image fields take photos from the camera; any text field can scan barcodes and QR codes.
Checklists
Boolean and select fields in a form, grouped into sections, with required fields the technician cannot skip.
Dispatch
A kanban by status or a calendar by scheduled date for the office; a 'My jobs today' view for each technician.
Offline
Published apps are responsive, install on a phone's home screen, and queue edits made offline until the connection is back.
Reports
Generate a PDF job report from a template and email it to the customer from a workflow.
Time
Time and duration fields for arrival, departure and hours on site, with sums in formulas.
How it works
- 1
Connect or import the data
Start on a built-in database, your own Postgres (Supabase, Neon, RDS, anything that speaks Postgres) or an Airtable base, or upload a CSV. Tables and columns are detected.
- 2
Describe the app, or start from a template
Ember drafts tables, views and workflows from a sentence or two. Or open one of ten working templates in the editor without an account.
- 3
Arrange the blocks
Drag tables, cards, record pages, kanban boards, calendars, maps, timelines, charts, stats, forms, buttons, comments, activity feeds, file viewers, signatures, barcodes and embeds onto a grid. Each block reads a table; filters, sorts, groups and formulas are configured in the inspector.
- 4
Set roles and publish
Roles decide which views a user sees and which fields they can read or edit; app users can be loaded from a table in your own data. Every publish is a versioned snapshot you can inspect and roll back, with a stable and a latest channel.
What you get in Emberblocks
Your data, live
Start on a built-in database, your own Postgres (Supabase, Neon, RDS, anything that speaks Postgres) or an Airtable base. Apps read and write live rows, so there are no exports to keep in sync.
Blocks on a grid
Drag tables, cards, record pages, kanban boards, calendars, maps, timelines, charts, stats, forms, buttons, comments, activity feeds, file viewers, signatures, barcodes and embeds onto a grid and wire them to tables. What you arrange is exactly what your team gets.
Real field types
Fields include text, email, phone, URL, number, boolean, date, date-time, time, duration, select, multi-select, reference, multi-reference, image, file, signature, address and JSON. Barcode scanning and signatures work in the browser without a native app.
Workflows
Workflows run when a row is created, updated or deleted, on a schedule, or from a button; steps update records, send email, call webhooks, branch on conditions and run code.
Roles and permissions
Roles decide which views a user sees and which fields they can read or edit; app users can be loaded from a table in your own data.
Publishing like software
Every publish is a versioned snapshot you can inspect and roll back, with a stable and a latest channel.
Phones and offline
Published apps are responsive, install on a phone's home screen, and queue edits made offline until the connection is back.
AI where it helps
Ember drafts a first version of an app from a plain-language description, and end users can ask questions of the data in plain language when you turn it on.
Questions
- How does offline work?
- The app shell is cached on the phone. Edits made without a connection are queued and replayed in order when the connection returns. It is not a full offline database: viewing data that was never loaded needs a connection.
- Can customers sign on the technician's phone?
- Yes. The signature field opens a drawing pad on any touch screen.
- Can I share a job with the customer?
- A public link can show a view without an account, and a role can give customers logins that show only their own jobs.
- Where does my data live?
- Wherever you want it. Use the built-in database, connect your own Postgres so rows never leave your server, or point an app at an Airtable base. Airtable bases are mirrored into Postgres and kept in sync both ways.
- How is Emberblocks priced?
- Builders are always free. Paid plans are priced by the number of people who sign in to your published apps: Starter $29, Pro $79 and Business $199 a month billed yearly. Every new workspace starts with a 14-day Pro trial, no card needed, and there is a free plan after that. Full details on the pricing page.
- What does Emberblocks not do yet?
- Custom domains, SSO and an Enterprise plan are not available yet. There is no live Google Sheets connector (import the sheet as CSV instead). Apps run in the browser and install to the home screen; there are no App Store or Play Store builds.
Try it on your own data.
Every workspace starts with a 14-day Pro trial without a card. You can also open a template in the editor first and sign up only when you want to keep it.