Users and permissions
Who sees which screen, who can change what.
Admin panels, portals and internal systems that run only in the browser — no installation, no store, no update headache.
Teams running the business on spreadsheets — once the files multiply and nobody is sure which one is current.
Firms that want a portal for dealers, suppliers or customers.
Businesses whose way of working doesn't fit an off-the-shelf program.
An app is not always the right answer. If the user works at a desk, in long sessions and with a lot of data, and there is no need for the phone's camera, location or notifications, then a web application ships faster, costs less and updates instantly. You don't wait for store approval.
Who sees which screen, who can change what.
Listing, search, filtering, bulk actions; making screens that are used all day feel fast is engineering work, not decoration.
Taking what's on screen out as Excel or PDF.
Accounting, stock, e-invoicing, payments.
Two-factor authentication, audit trails, backups.
Sign-in with two-factor authentication; the customer follows their own assistant's conversations, usage and cost from here. There is a platform admin panel beside it.
Explore DKC.aiThe web interface where dietitians manage clients and build nutrition plans.
Explore dyetyYes. We build the web application as though mobile is coming — because the data layer is shared, mobile gets added later rather than written from scratch.
It can. We run our own assistant platform on our own server, so we know how to set it up.
The first conversation is free. By the end of it we can usually talk about feasibility and a rough cost.
We would like to use Google Analytics to understand how the site is used; it places a cookie in your browser. If you decline, no cookie is written and the site works exactly the same. Cookie Policy