The field catalogue
Design the form. Keep the record.
Recordry is two things at once: a builder for the form you wish existed, and the logbook of everything you have filled in from it. Draw up a template, publish it, and every record made from it is validated against that exact version and stored in an encrypted database on your own device. No account, no server, nothing to sign up for.
How It Works
A template, a version, and everything you log from it.
Most form apps give you a form. Recordry separates the form from the records made from it, because the form changes and the records must not change under you when it does.
Build the template
A template is the reusable form your records are made from. Add fields, group them into sections that can collapse, and drag them into the order you want. Each field carries its help text, whether it is required, optional, or required only when something else is true, and a machine key that becomes its column name in exports.
Publish a version
Nothing can be filled in from a draft. Publishing freezes the schema into a version that never changes again, and shows you exactly what is different from the last one before you commit to it. Try it first in the preview, which runs the real form and its real rules and saves nothing.
Keep the records
Records validate as you fill them in. Rules reveal and hide fields as the answers arrive, and a record finalizes only when what is required is genuinely there. If you finalize with problems outstanding, it is marked as needing attention and the reason is kept with it rather than discarded.
Rules & validation
The form should ask what follows from the last answer.
A long form that asks everyone everything is how a form gets abandoned. Rules let a template ask the next question only when it applies, and let a field be required only when it genuinely is.
- 1Show and hide A field, or an entire section, can stay out of the way until an answer makes it relevant. The rule is written in the builder as a sentence — when this, show that — not as a formula you have to debug.
- 2Required only when it matters A field can sit as optional until a condition makes it required. That is a third state alongside required and optional, so a form can insist on a reason for an exception without insisting on it from everyone.
- 3Validation with an honest failure A record cannot be finalized while a required answer is missing. If you finalize anyway, it is filed as needing attention with the outstanding count kept on it, rather than pretending to be complete.
- 4Preview before publishing Fill in the form exactly as it will be, with the rules live, before you publish it to anyone. The preview saves nothing — it is there to find the rule you got backwards while it is still free to fix.
The field catalogue
Sixty-six kinds of question.
A form is only as good as the answers it can actually hold. Rather than a text box for everything, each type knows what a valid answer looks like, which operators a rule may use against it, and how it should be stored — which is what makes searching, sorting and validating possible later.
Text
- Short text
- Long text
- Markdown
Numbers
- Whole number
- Decimal
- Currency
- Percentage
Choices
- Checkbox
- Yes / no
- Yes / no / unknown
- Radio
Date & time
- Date
- Time
- Date & time
- Duration
Layout
- Section
- Collapsible section
- Heading
- Paragraph
Structured
- Person name
- Address
- Checklist
- Table
Photos & media
- Photo
- Gallery
- File
- Audio
Location
- Coordinates
- Postal address
- Current location
Automatic
- Formula
- Sequence number
- Created at
- Modified at
Finding things again
A logbook is only useful if you can find the entry.
Records go into folders you arrange yourself, and a folder can decide what belongs in it — which is how a shared folder stays consistent without anyone policing it.
Folders that know what they hold
New records in a folder start from the folder's template. Set it to inherit from the parent, allow anything, or mark the folder strict, which blocks records made from any other template outright.
Search and sort
Search across your records, and sort by when they were last updated, when they were created, or by name — ascending or descending. Fields marked as searchable are what search looks at; masked fields are deliberately excluded.
History you can read back
Every record keeps its own history: created, edited, finalized, reopened, restored, or switched to another template. A finalized record is locked — duplicate it to make changes, so the original stays exactly as it was filed.
Finalized records lock
Once a record is finalized it is locked, and the app tells you to duplicate it rather than quietly letting you rewrite what was filed. Its history keeps every edit, finalize and reopen along the way.
Finding things again
A logbook is only useful if you can find the entry.
A form is only as good as the answers it can actually hold. Rather than a text box for everything, each type knows what a valid answer looks like, which operators a rule may use against it, and how it should be stored — which is what makes searching, sorting and validating possible later.
- Great 50%
- Good 38%
- Hard 12%
Get the App
Still being built
Recordry is under active development and says so inside the app as well as here. Templates, responsive form design, rules, custom validation, records, search, statistics, scheduling, reminders, photos and files, encrypted backup, CSV export, and template sharing work today. Audio, video, signature, sketch, sensor location, repeating-group entry, JSON/PDF export, and the app lock are not presented as finished features.
Get the App
Where you can run it today.
Recordry is built in the open and released from source. Below is honestly where each platform stands — not where it is heading.
Browser demo
The same app, compiled for the browser, against an in-memory database. Nothing is written to disk, nothing is sent anywhere, and everything is gone when you reload. It is for trying the builder, not for keeping records.
Open the demoAndroid
In closed testing on Google Play. Join the tester list and it installs like any other app.
iOS
On iOS it is the full app: an encrypted database on disk, with its key in the system keychain. The App Store build is not published yet.
Still being built
Recordry is under active development and says so inside the app as well as here. Templates, responsive form design, rules, custom validation, records, search, statistics, scheduling, reminders, photos and files, encrypted backup, CSV export, and template sharing work today. Audio, video, signature, sketch, sensor location, repeating-group entry, JSON/PDF export, and the app lock are not presented as finished features.
Privacy
There is nowhere for your records to go.
Recordry has no backend, no account system, and no analytics. The records you keep in it are frequently the kind you would not put in a cloud spreadsheet, so the app is built to make that impossible rather than merely unlikely.
No account, no sign-in, no email address
Templates, records and their values live in a SQLCipher database encrypted with AES-256
No analytics, no trackers, no advertising SDKs
The database key is generated by the operating system's secure random source and held in the Keychain or Keystore
The Android release does not request the INTERNET permission at all
Fields marked sensitive are masked while typing and kept out of titles, search and exports
Try Recordry in your browser
Browser demo
The same app, compiled for the browser, against an in-memory database. Nothing is written to disk, nothing is sent anywhere, and everything is gone when you reload. It is for trying the builder, not for keeping records.