Coming from Device Magic
FreezeFrame Forms was built to be a straight swap for Device Magic’s core loop, so most of what you know carries over.
What works unchanged
Section titled “What works unchanged”Your Word templates. Placeholder syntax is deliberately identical:
{{fields.name}}, %for row in fields.LineItems% … %endfor%, and the familiar filters
(|currency, |date_time_format, image sizing, |list). Upload an existing DM template
and it fills. See Word templates.
The form model. Fields, groups, repeat groups, required, hidden, and calculated fields map across.
What is different
Section titled “What is different”| Device Magic | FreezeFrame Forms |
|---|---|
| Native mobile app, offline capture | Browser form at a public link, online |
| Dispatch to devices | Share the link (email, SMS, QR) |
| Organisations / device groups | Businesses, roles, and groups |
| Revert Version | Version history — same idea |
What is not here yet
Section titled “What is not here yet”- Offline capture / a native app
- Dispatch and assignment
- Live SQL-backed resources (static resources are supported)
Importing
Section titled “Importing”The importer accepts a Device Magic form export. Anything it cannot map is reported explicitly after import rather than dropped silently — read that summary, it tells you exactly which fields were skipped.