02 — Applications
Custom web applications
An application is no longer a site: there are accounts, data changing by the second, business rules and sometimes artificial intelligence. It is software that lives in a browser.
What I build
Accounts and sessions
Sign-up, sign-in, forgotten passwords, roles and permissions. Each person sees their own data and only theirs, with sessions secured on the server.
Real-time data
Information that updates without reloading: scores, order status, availability, messages. With the caching needed to take a rush of traffic without blowing up the API bill.
Artificial intelligence, built in
A language model wired to your own data, required to justify what it says. Analysis, summary, ranking, assisted writing — the AI serves the function, it is not there for decoration.
Payments and subscriptions
Taking payment online, subscriptions, invoices. Payment goes through an approved provider: your customers enter their card details there, never on a server of mine.
Business dashboards
Your figures, readable, in one place. Often the most profitable part of the project: what gets measured ends up improving.
How it works
-
01
Frame the real need
An application almost always fails for the same reason: what was asked for got built, not what was missing. We start by finding the repeated task that costs time.
-
02
Data model
Who owns what, who sees what, what must stay true in all circumstances. This dull step decides how solid everything else will be.
-
03
A first usable version
We aim first at the main path, end to end, for real. An incomplete application in use beats a complete one still being waited for.
-
04
Trials with real users
The first accounts reveal in three days what no specification had anticipated.
-
05
Going live, and watching it
Backups, error logs, rate limits on the APIs. We know when something breaks — before a user reports it.
One complete example
SportIQ brings together what its users previously did across four tabs: a scores app, a statistics site, a messaging group for friendly bets and a spreadsheet to keep the table.
So there are accounts, data changing by the minute during matches, a language model analysing each fixture, a moderated discussion thread and private leagues between friends. Each brick could have been bought separately; none of them would have talked to the others.
What costs money, and what costs nothing
What costs money in an application is almost never the screen you are picturing. It is what happens behind it: access rights, edge cases, what must happen when two people change the same thing at once, and what you do when an outside API stops answering.
What costs nothing, on the other hand, is asking those questions at the start. Revisiting them six months later, in production, with users inside, costs ten times more.
Need an internal tool rather than an online application? Look at business software.
This trade, online
Frequently asked questions
What is the difference between a site and an application?
A site presents information that rarely changes and is the same for everyone. An application has accounts: each signed-in person sees different content, acts on it, and their actions are kept. The second needs a server, a database and constant attention to security — so a budget of a different kind.
What does the artificial intelligence actually do?
It turns raw data into something readable. On SportIQ, the model receives a match's real statistics and both teams' history, then writes an analysis and a reasoned prediction. It does not guess: it starts from figures and has to justify its conclusions. Answers are cached, so two visitors to the same match do not trigger two bills.
What does an application cost once it is live?
There are recurring costs, unlike a showcase site: server hosting, database, and where relevant the calls to data or artificial-intelligence APIs. Those amounts depend on real traffic. I estimate them before starting and design the application to keep them down — caching is not a detail.
What about my users' personal data?
It is treated as such: hashed passwords, access limited by role, European hosting where possible, and only the data genuinely needed. Data protection is prepared during design, not after going live.
Will the application be able to grow afterwards?
That is planned from the start. The code is written so a new function can be added without reopening everything, and you own it. Changes are discussed as they come, in batches.
Do I also need a mobile app?
Rarely at first. A well-built web application installs onto a phone's home screen and works offline where needed. Going through the app stores adds review delays and commission: we do it when there is a real reason.
The other trades
Page updated on — written by Yvan Barbaggio.
A question that is not on the list? Ask it in two lines, I answer within 48 working hours.