When does a new feature improve an application and when does it just complicate it? Drawing on my own products such as Bizko, I write about the path from an everyday problem, like entering the same data twice, to a tool people actually use.
Key questions
Does every business need its own app?
No. Every business needs a way for people to find it, understand it and use it. For most that is a good responsive website, for some a PWA, for a minority a native app. The starting point is what the user will do and how often, not what a competitor has. My thinking is in Does every business need an app today?
More than people usually think, but not everything. An example from my projects: FitBlizu, a map of gyms in Slovenia and Croatia, is a PWA; it has a manifest for installing and a service worker that caches only the basic app shell (checked on 4 October 2026). For push notifications on iPhone the state of the particular device matters: in February 2023 Apple announced Web Push support for web apps added to the Home Screen on iOS and iPadOS 16.4 (WebKit), so when I plan something I always check the current state on a real device.
Why do I like tools that do one thing?
Because I open them, do what I wanted and close them. A long feature list is often noise to the user; the measure is speed, reliability and clarity. I also like it when data stays on the device. SmallLynx is a brand for small Mac tools; the first one, SmallLynx Image, converts and optimises images locally, without uploading them to a server (according to the public site on 4 October 2026 it is in internal testing). More in I increasingly like apps that do one thing really well.
When does a new feature improve an app, and when does it only complicate it?
Every feature has a cost, even a free one: explaining it, maintaining it, testing it, space in the interface and the expectation that it stays forever. Before each one I ask whether it simplifies use or only lengthens the list. More in More features don't necessarily make a better product.
The first question isn't "website, PWA or native app" but "what will the user do and how often will they come back". Installing is a barrier for the user, not a milestone: if someone needs something once a year, they won't install an app.
The hidden cost isn't building but maintaining: store review, operating system updates and, for native solutions on several systems, several codebases. A native app makes sense when the user comes back often, when personal data is involved, push notifications are useful, work offline, a camera, location or sensors are needed, or deeper integration with the system. If none of these holds, I'd start with a website or a PWA.
In practice
Even among my own projects the paths differ. Bizko runs in the browser as a web application; FitBlizu is a PWA; SmallLynx is a brand of desktop tools for Mac. There is no single solution for all, and that is my criterion too: the starting point is the task the tool has to do, not the model. That is why in the articles on this topic I compare point by point, not by feel, and I check support for a feature on a device before I promise it.
Installation, updates, offline use, notifications, device access, maintenance cost: a comparison table and the cases where a PWA is enough and where it isn't.
A program doesn't need two hundred features to justify its existence. On focus, speed, privacy, local processing, ownership instead of subscription, and why a small scope is harder than it looks.
A native app isn't always the answer. Website, PWA and native app compared, and the criteria I decide by: frequency of use, notifications, offline work, camera and the cost of maintenance.
What a website has to tell someone who does not know the business yet, and why that is not mainly a question of design. I write about the decisions that come before the first line of code, about reviewing existing sites, and about when a redesign makes sense and when it does not.
Search is no longer just Google. I am interested in how people find information today, what of classic SEO still holds, and what AI answers change for a website. No ranking promises, verified sources.
I use AI every day and I do not trust it blindly. Here I note where it genuinely saves work, where the result has to be checked, and which promises do not survive the first enthusiasm. Experiments, not predictions.
How code comes about that can still be maintained a year later. I write about planning, testing, working with AI while developing, and the decisions we forget quickly once something simply works.
Technology is the beginning; business gives it meaning. I am interested in what a digital solution really brings a company, which processes are worth automating, and when a simple path beats a big system.