The spreadsheet everyone knows
Almost every company has one: a shared spreadsheet that quietly became important. Who has which training, when it expires, who has which device. Everyone can see everything and overwrite anything. Nobody is quite sure which version counts.
A fictional example: at Hofmann Engineering, Stefan, head of workplace safety, keeps training records in a spreadsheet. Forklift licences, first aid, safety briefings. Managers add entries, employees look things up, and every year an expired certificate is noticed too late. Here's how the spreadsheet becomes an app.
Describe
Stefan describes in his own words what the list should do and who may see what:
"An overview of trainings per person. Everyone sees their own records, managers see their team's. Only workplace safety can make entries. Trainings that expire in the next 60 days should stand out."
A build agent builds the app from that. No code for Stefan, no IT ticket, no agency. It isn't a form builder or drag and drop: the result is real software with a data model, permissions and tests.
Answer the domain questions
Openbase.one only asks what Stefan has to decide as the expert, for example: "Does a training count from the day someone attended or from the date of the certificate?" or "Can a manager upload a certificate themselves?" Stefan answers, and the app is built accordingly.
Checked before it goes live
Before a version goes live, it is built and checked:
- The data model and access rules are checked.
- Records are classified, training records for example as personal.
- Every page is opened in a real browser as every test persona: "as an employee: only own records visible", "as a manager: only own team visible", "as workplace safety: all records editable".
A version goes live only when the check passes.
Live in the workspace
The app runs in the company workspace, and people sign in with their company accounts. It runs isolated without network access, and every data access is checked against workspace, app and permissions. The audit log shows who changed what. The app also runs natively in the app for iPhone and Android, from the same code. And each person's assistant can use it with that person's permissions, for example to look up which certificates in the team expire soon. Changes always come to the person for approval.
Change it later
A new mandatory training comes along? Stefan describes it, and the new version is checked again. Every version is kept, and the previous one is live again in one click. The code lives as a git repository in your workspace, and the data is exportable.
Whether the deadlines are right in substance is your call. If you want help with that, or want to bring the existing list over, there are support contracts and a migration package.
What it costs
One price per workspace, with unlimited users and apps on every plan. All plans, support contracts and packages are on the pricing page.
Describe your first app and watch it go live, checked.
Start for free