mForm

Open source · built by Dhwani RIS

An offline-first mobile framework for Frappe.

The building blocks for production-ready Flutter apps on Frappe — offline engine, sync, auth and metadata-driven forms.

Get started View on GitHub ↗

$ flutter pub add frappe_mobile_sdk

Built on Frappe Framework

9:41

◦ no signal

Visit Log

6 entries · 3 waiting to sync

Household #2291

✓ synced

Immunisation · 09:12

Household #2292

✓ synced

Nutrition · 09:48

Household #2293

◷ pending↻ syncing✓ synced

Immunisation · 10:24

Household #2294

◷ pending

Referral · 11:03

Household #2295

◷ pending

Nutrition · 11:31

The contract

SDKFlutter · MIT2.0 beta

ControlFrappe · AGPL-3.0

Frappev15+

Developers

Build it yourself

Add the SDK to a Flutter app, install Control on your Frappe server, and ship. Open source, MIT + AGPL-3.0.

Start building →Programme teams

Have us build and run it

Your staff collect data where there is no network. You see it on a dashboard the moment they reconnect. We build the app, train the team, and stay on call.

See how it works →

Where it runs

Built for programmes like these

Health & nutrition

Household visits, immunisation, screening and referrals — recorded at the doorstep, reviewed centrally.

Education

Attendance, assessment and student journeys tracked across schools and cohorts.

Agriculture & livelihoods

Plot-level surveys, seasonal cycles and enterprise data collected on the move.

Trusted by

People's Action for National Integration

How offline works

Offline is the normal operating state.

Staff record work with no network. The entry sits on the device until a connection returns, then reconciles with your Frappe server.

Read the offline model →

Synced

Confirmed by the server.

Pending

On the device, waiting for signal.

Syncing

Reconciling with the server now.

Failed

Retried automatically; the entry stays on the device.

Start with the quickstart.

Open source. Runs on the Frappe backend you already have.

Get started Star on GitHub ↗