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.
AI-assisted development talks a lot about prompts. I care about what we're building, by which rules, and how we'll know it's right. Brief, architecture, acceptance criteria, tests and production checks.
I'm more interested in AI that helps me think better. The difference between delegating thinking and strengthening my own, with examples from research, planning, critique, writing and decisions.
What a Slovenian travel order must contain, why the tax rules require it, the seven most common mistakes and how I handle it myself. Without the amounts that change.
A half-hour checklist: AI crawler access, answers in the text, structured data, content worth citing, speed and indexing. No promises about getting you into ChatGPT.
The price of a website isn't a single number. What it's made of, what has to be included, which costs come after launch, and the seven points I'd check in any quote.
Since I build websites, the easiest thing would be to always propose a new one. But age isn't the problem. When I suggest a fix, a gradual improvement, a partial redesign, and when a new site really is needed.
I get the e-mails promising Google's first page too. Why that sentence says almost nothing on its own, what I'd ask the sender, and how a review differs from a sales pitch.
AI answers change the path to information, but they don't remove the need for a good website. How I look at visibility, sources and the promises of GEO tricks.