SERVICES — WEB APPS
Web app development in Turin, Italy
Portals, private areas, platforms, internal tools: applications that open in the browser and work on any device, with nothing to install.
Empatix builds custom web apps: applications used from the browser, on computers, tablets and phones. We are based in Turin, Italy; the projects come from companies that need a tool which does not exist ready-made.
When you need a web app
- You want to give customers a portal to check orders, documents and the status of their requests.
- You have a service that is booked or configured online, with your own rules.
- An internal process lives on shared spreadsheets and email, and you would like a real working tool.
- You have an idea for a digital product and need a first version to put in front of users.
- The company website must do more than present: an up-to-date catalogue, enquiries, private areas.
What we build
- Customer portals and private areas, with role-based access.
- Booking platforms: calendars, availability, reminders, payments.
- Internal tools and dashboards, connected to business software and company data.
- Websites with application features: dynamic catalogues, configurators, advanced search. That is the case of the Dionisi Group website, with an always up-to-date car catalogue and workshop booking.
- Product MVPs: the smallest version that lets you test an idea with real users.
What sets a well-made web app apart
Speed. Every second of waiting costs attention and customers. We measure loading times on real phones, not just on the developer's computer.
Accessibility. Keyboard navigation, screen readers, readable contrast: we follow the WCAG guidelines because an accessible application is simply a well-built one, and for many services it is also a legal requirement.
Security. Minimal permissions, data encrypted in transit, dependencies under control. For anyone building software in Europe the rules have become more precise: we write about it in our article on the Cyber Resilience Act.
Maintainability. Readable code, automated tests, documentation. A web app lives for years: it must be able to change without being rewritten.
Visibility. When pages need to be found, we design them for search engines and AI engines: content in the HTML, structured data, clean URLs.
Technologies
On the frontend we use React and Next.js or Vue and Nuxt, with TypeScript. On the backend Node.js or Python, with PostgreSQL for data. For deployment, Docker and automated pipelines: every change passes its checks before going live. The full stack is on the technologies page; the choice depends on the project and on the skills you already have in house.
Cost and timing
The cost of a web app depends on three factors: the number of features, the number of user roles and the systems to integrate. We always propose an estimate split into phases, starting from a first version that covers the main flow. It is the safest way to spend well: you invest in the features users really use, not the ones imagined around a table.
How we work
PHASE 01
Listen
We understand the problem before proposing a solution. Workshops, questions, zero pointless slides.
We clarify who the users are, what they must be able to do and which systems the app has to talk to.
PHASE 02
Design
Clickable prototypes in days, not months. You decide on something you can actually touch.
A navigable prototype of the main flow, on phone and desktop.
PHASE 03
Build
Short sprints, frequent releases. Watch the product grow week after week.
Sign-in, permissions and the main flow first; the rest grows through frequent releases.
PHASE 04
Evolve
We don't vanish after launch. We measure, improve and stay by your side.
We measure speed and real usage and act where users get stuck.
Frequently asked questions
What is the difference between a website and a web app?
A website presents content; a web app lets people do things: book, order, manage data, collaborate. The difference shows in the project: a web app has users with different permissions, data to protect, business rules and often connections to other systems.
Web app or mobile app?
A web app runs on every device from a single codebase, updates without going through the app stores and needs no installation. A native app is worth it when you need phone features the browser does not offer, or a presence in the stores. Often you start with the web app and add a mobile app when usage justifies it.
Can a web app work offline?
Yes, when it is needed. With a local-first architecture the data stays on the device and syncs as soon as the connection returns: useful in a warehouse, on a building site or on the move. We cover this in our article on local-first and CRDTs.
How do you handle data security?
Strong authentication, role-based permissions, encrypted connections, dependencies checked and kept up to date, verified backups. Personal data is handled under the GDPR, collecting only what is really needed.
How long does it take to build a web app?
It depends on the number of features and integrations. We work in short sprints with frequent releases: instead of waiting for the end of the project, you see a first working version early and set the next priorities based on it.
Last updated:
