Some work outgrows a spreadsheet. A club tracks members, game logs and approvals in a shared sheet that three people edit at once. A store’s workers need to see orders and print packing slips but should not have the keys to the whole business account. An organization’s old wiki holds years of pages that nobody can search. These are small web apps, and they belong inside the website the business already has.
What we build
- Member databases with sign-up, login, profiles and roles such as member, editor, approver and admin.
- Approval queues: new or edited entries wait for someone with the right role to approve them before they go public.
- Staff screens: an orders list that fits a 1366 pixel laptop without sideways scrolling, order details, mark-as-shipped and packing slips, so workers never need the owner’s account.
- Searchable archives and logs, with filters, that replace folders of documents or an old wiki.
- Demo access codes for reviewers, one per person, which can be switched off at any time.
How it is built
The apps run inside your website on Wix’s business backend: Wix Members for accounts and logins, and Wix’s database collections or CMS for the records. The screens are custom code, built with the same design as the rest of the site and checked for accessibility at nine screen sizes.
Some rules we follow on every app:
- Roles are checked on the server for every request. Hiding a button is not security; the server refuses the action if the person’s role does not allow it.
- Staff are allowed by member ID, not by email, because anyone can register an email address nobody has claimed yet.
- Private details stay private. Members’ emails and phone numbers are not shown on public pages.
- Workflows match how the organization works. If an approved entry is edited, it goes back to the approval queue, so nothing slips through unreviewed.
- Writes only from your own site, in the format the app expects, so other sites cannot post into it.
How a project runs
- Inventory what exists. If there is an old system, we explore it read-only and list every page, feature and admin action. We never press “forgot password”, delete or settings buttons on a system we are only exploring.
- Agree the roles and the workflow in writing: who can see what, who approves what, and what happens on an edit.
- Build on a preview address with demo access for each role.
- Move the data and redirect the old addresses.
- Launch and support. Roles change and organizations grow, so most apps continue under managed hosting.
Who it is for
Clubs and organizations are the most common case; our page on member websites for clubs and organizations goes into detail, and our guide to member roles and approvals covers the decisions to make before a build. Stores add staff screens, and service businesses add things like job request queues. If people in your business copy data between tools by hand every day, there is probably an app worth building.
Pair it with automations and alerts when people need to hear about new entries the moment they arrive.
