Discuss a project

Devnora Insights19 articles6 topicsIn Lithuanian and English

Insights

We write about the choices that decide the outcome: where automation ends and AI begins, when a custom system beats an off-the-shelf one, why integrations break and how to keep your visibility.

Latest

Also new

Systems & integrations

Who owns an integration once it works?

Integrations rarely break on day one. They break six months later, when the other system changes something and nobody had ever answered the question of who would notice. What to settle before the work rather than after.

4 min read

Topics

Six topics, each of which also leads to the services it relates to.

  1. 3 articles

    Websites & e-commerce

    What a website costs, how to choose an e-commerce platform, how to redesign without losing URLs, and what to take over at handover.

    Latest: Redesigning a website without losing your URLs

  2. 4 articles

    Apps & products

    Whether you need an app or a mobile site, one codebase or two, what the first version should contain, and what happens after launch.

    Latest: iOS and Android: one codebase or two?

  3. 5 articles

    Systems & integrations

    A custom system or a CRM, why quotes differ so much, who owns an integration, and what to do when two systems disagree about the data.

    Latest: Do you actually need a dashboard, a report, or neither?

  4. 3 articles

    Automation & AI

    When automation is enough and when AI is needed, whether output is accurate enough, and how to prepare a team to work with AI.

    Latest: Preparing a team to work with AI: from scattered tools to an agreed way of working

  5. 2 articles

    Maintenance & technical quality

    What to take over at handover, how much maintenance a launch really needs, and when rewriting beats patching.

    Latest: Handing a website over to another development team

  6. 2 articles

    SEO & AI search

    Why a site cannot be found, how to keep visibility when URLs change, and what visibility in AI answers actually means.

    Latest: GEO and AI search: what Google actually says about optimising for it

All articles

Page 1 of 2

  1. Redesigning a website without losing your URLs

    The most common redesign mistake is not the design — it is losing addresses. This guide covers building an inventory of your existing URLs, assigning each one a decision, redirecting without intermediate hops, and verifying afterwards that nothing quietly fell into an error page.

    Websites & e-commerce

  2. Handing a website over to another development team

    A handover is not a file archive. It is an access inventory, a working environment, and proof that the new team can ship a change on its own. This guide gives the checklist and the one acceptance criterion that "everything has been handed over" does not cover.

    Maintenance & technical quality

  3. Rebuild or improve: deciding about an old system

    The decision to rebuild is made more often than it is justified. Four checks you can run yourself, and the question that separates a technical problem from an organisational one.

    Maintenance & technical quality

  4. Preparing a team to work with AI: from scattered tools to an agreed way of working

    In most companies somebody already uses AI — each in their own way, with nothing agreed. What a team genuinely needs to learn, what is worth standardising, what must be checked, and when training is the wrong answer.

    Automation & AI

  5. iOS and Android: one codebase or two?

    The decision is not driven by price or fashion but by how much the app has to talk to the phone itself. Where the line falls, what "almost identical" means, and when double the cost is justified.

    Apps & products

  6. MVP scope: what to build first and what to postpone

    A first version is not a small version of everything — it is one workflow, end to end. This guide gives a concrete postponement list, separates the work that cannot be postponed, and suggests agreeing in advance what observation would count as evidence.

    Apps & products

  7. How to tell whether an AI solution is accurate enough

    A demonstration always looks good, because the examples were chosen. Accuracy is your number, measured on your own cases — and you can measure it before you buy. How to do that without technical knowledge.

    Automation & AI

  8. GEO and AI search: what Google actually says about optimising for it

    GEO and AEO are sold as a new discipline with their own tools and their own fee. Google's own documentation says something different: optimising for generative AI search is optimising for search, and therefore still SEO. Here is what that means in practice, and what you can skip.

    SEO & AI search

  9. Do you actually need a dashboard, a report, or neither?

    Dashboards get commissioned more often than they get used. Usually the request does not mean "we want charts" but "we do not trust the numbers" or "preparing them takes too long". Those are three different problems with three different answers.

    Systems & integrations