01
Role design
Who sees what, who can change what. If the permission structure isn't set up at the start, adding it later is one of the most painful jobs there is.
Mobile + Web App
Your customer on one side, using their phone; you or your team on the other, using a computer — both on the same system, working from the same data.
Who it's for
This structure fits any business that brings two different groups of users together: client and specialist, customer and dealer, patient and clinic, student and teacher, driver and operations.
The question that decides it: are both sides doing the same thing or different things? If your customer does something quickly on their phone while your team manages it all day at a desk, the two need separate interfaces. Giving both sides the same app wears both of them out.
What's included
02
Mobile app
For the end user, on iOS and Android.
03
Web panel
For the professional user; built to stay open all day and handle a lot of data.
04
Shared server and data layer
One source of truth; both sides see the same reality.
05
Messaging, notifications, file sharing
Almost every platform of this kind needs them, so they are in scope.
What came out of this: dyety®
dyety — digital nutrition platform
dyety is exactly this structure: clients follow their nutrition plan, recipes and meal, water, activity and measurement records from a mobile app; dietitians manage their clients, build plans, message and assign tasks from a web panel. Clinics sit on a third layer, running their teams and operations from the same system.
Explore dyetyFrequently asked
I have three different user types — is that possible?
Yes. dyety has three roles: client, dietitian and clinic. The more roles there are, the more permission design matters, but there is no structural obstacle.
Couldn't the web side be a mobile app as well?
It could, but we don't recommend it. For someone managing data all day, a phone screen is too narrow; it slows the work down.
Let's hear about your business first.
The first conversation is free. By the end of it we can usually talk about feasibility and a rough cost.