Access
Website
Public, open pages
Web application
Login, sessions, permissions
Web applications
Web applications built around the daily work.
A marketing website informs. A web application is where people sign in and do the work.
browser · roles · dashboards
Workspace
Quote #1042 · Open
Filter or select a row — status stays in charge.
Overview
Portals, dashboards, planning, bookings and customer environments. Tinsights builds web applications with accounts, permissions and data. It is not an extra page on the business website.
If visitors mainly need to read and get in touch, a website is enough. If they need to sign in, see status or keep data, it belongs here.
Website or web application
Select a category — see the difference immediately.
Website
Public, open pages
Web application
Login, sessions, permissions
Login
Website
Rarely needed
Web application
Core of the product
Data
Website
Content you publish
Web application
Live records users change
Roles
Website
Everyone sees the same
Web application
Client ≠ admin ≠ partner
Workflows
Website
Read → contact
Web application
Tasks → status → done
Updates
Website
New pages/content
Web application
Rules, fields, processes
Interaction
Website
Navigation and forms
Web application
Dashboards, filters, actions
Environments that hold the process
Pick a type — a realistic UI preview appears on the right.
- My jobs
- Documents
- Status: in progress
Portals
Clients or partners see their own work, files or status.
- My jobs
- Documents
- Status: in progress
Dashboards
Numbers and queues people actually use.
- Open: 14
- Today: 6
- Priority queue
SaaS
Product with accounts, billing logic and room to grow.
- Plan: Pro
- Seats: 12/20
- Billing
Scheduling
Who books what, with your rules.
- Mon 09:00
- Tue 14:30
- Slot taken
Internal systems
Team work without another disconnected tool.
- Intake
- Assign
- Complete
Rights & data
Role-based access and stewardship of what matters.
- Admin
- Editor
- Viewer
Workflow in screens
From intake to live status — one product path, multiple UI states.
Use cases
Where a web app makes the difference
Track jobs, fetch documents — no mailbox archive.
Process, assign and close requests.
One source for everyone instead of five spreadsheets.
Process
Screens follow the work
- 01
Tasks
What someone must do in the system on a normal weekday.
- 02
Data model
Entities, relationships, and what a mistake costs.
- 03
Roles
Who can see and change what — in the app, not in agreements.
- 04
Screens
Interfaces that follow the flow, not loose pages.
- 05
Integrations
CRM, mail, payments or scheduling where needed.
- 06
Launch
Deploy, monitoring and room to keep building.
Architecture
What sits under the screens
Tap a layer — a short explanation appears.
UI
Screens, filters, status — what users see daily.
From task to live environment.
Roles, data and screens stay connected as the product grows.
- 01Tasks & status
- 02Roles & permissions
- 03Live with monitoring
Related work
Web applications usually sit behind sign-in. Public cases on this site are mostly websites.
Facturatie / administratie
Facturatie & administratie app
Mobiele applicatie voor facturen, klanten, betalingen, omzetinzichten en financiële administratie in één duidelijke workflow.
Field service
Field service & routebeheer app
Applicatie voor planning, routebeheer, klantlocaties, werkorders, jobdetails en statusupdates voor buitendienst- en serviceteams.
Wellness
Relax & wellbeing app
Flutter-appconcept gericht op onboarding, rustige interactie en eenvoudige dagelijkse gebruiksflows.
Travel / booking
Travel & booking app
Flutter-bookinginterface voor zoeken, datumselectie en accommodatiekeuze.
Questions
No. A website is mostly public and informative. A web application has accounts, data and repeated use. Sometimes a business needs both.
Web applications
Tell us who must sign in and what they need to do.
Then it is quickly clear whether a web application is the right route — or a website is enough.