Does an app have to go in the App Store?
Not always. A Progressive Web App or web application is often enough. We only add a store release when the use needs it.
Apps
Apps for customers, staff and business processes.
An app is useful when people do the work on the move or repeatedly. Otherwise a web application in the browser is often stronger.
Tinsights builds business apps, customer apps and web-based applications, including Progressive Web Apps. We do not claim a fixed native framework. The choice follows use: phone, desktop, or both.
Behind the app there is almost always a backend: accounts, data, permissions and connections. Those belong to the job, not to a separate shell project.
App or web application
App
Fits when people use the product often on a phone, or when notifications and a fixed starting point matter.
Web application
Fits when the work happens mainly on desktop, or when you do not need an app-store process. Often live sooner.
What we deliver
A working part of the operation.
Not a loose gadget. The app hangs off the same systems as the rest of the business.
Mobile and business apps
For customers or staff, with the screens the work needs.
Progressive Web Apps
Installable from the browser, without a required app-store process.
Accounts
Sign-in, profiles and what someone may or may not do.
API connection
The app talks to your backend or existing software.
Payments
When something has to be sold or settled in the flow.
Notifications
Prepared where the process benefits. No claim for every channel.
Use cases
When an app makes the work lighter.
Customer environment
Track status, orders or appointments without calling.
Field work
Staff who record data or finish tasks on the move.
Internal tools
A fixed starting point for a process now split across too many apps.
How we work
Use first, then the channel.
Use
Who opens it, how often, on which device, and what must work now.
Choose the channel
PWA, web app or a native direction, only if that serves the use.
Build
Screens, authentication and the APIs behind them.
Launch
Handover, management and room to add functions.
Engineering
Where we keep the scope.
- Web-based appsTypeScript and a modern web stack, including as a PWA.
- APIsOur own backend or a connection to what already exists.
- AuthenticationSign-in that matches the risk of the data.
- No framework claimWe do not name a native stack we do not actually use.
Related work
We rarely show apps and signed-in environments as a public demo. Recent public cases are mostly websites.
Facturatie / administratie
Facturatie & administratie app
Mobiele applicatie voor facturen, klanten, betalingen, omzetinzichten en financiële administratie in één duidelijke workflow.
Horeca
Restaurant reserverings- en management app
Applicatie voor reserveringen, menubeheer, bestellingen, bezetting en dagelijkse horecawerkzaamheden.
Field service
Field service & routebeheer app
Applicatie voor planning, routebeheer, klantlocaties, werkorders, jobdetails en statusupdates voor buitendienst- en serviceteams.
Also relevant
Questions
Can you take over an existing app?
It depends on the codebase. We first look at whether continuing is wise, or whether a cleaner web app reaches the same goal.
Do you also build the backend?
Yes. Accounts, data, permissions and connections belong to the job. We do not deliver a shell without a system.
Unsure between app and web app?
Describe who will use it. We will say which channel carries the work best.