Custom Apps, Built to Last

How Vidigraph turns a rough idea into a finished application — the discovery work, the build, the platforms it runs on, and what it takes to get it found once it is live.

Get a Quote
Abstract view of a Vidigraph application interface in a deep blue lit environment.

A custom application is not a template with your logo dropped in. It is software shaped around one organisation's actual problem, which is why two projects that look similar on paper can end up as very different builds. This page explains how Vidigraph works: what happens before a line of code exists, how the application is put together, which platforms it can run on, and what keeps it useful long after launch.

Every build starts with the problem, not the technology

The first job is deciding what the application is genuinely for. A shop that needs repeat customers, a tutor who needs lesson material in one place, and a designer who needs a spec calculator have almost nothing in common technically — but all three are often described as "an app". So the opening conversation is about the work being done today: the spreadsheets, the messages, the manual steps, the things that get forgotten. Only when that picture is clear do we choose the parts. That order matters, because picking a framework first tends to produce software that fits the framework better than it fits the business.

What the build actually involves

Most projects follow the same four movements, whether they take a fortnight or a quarter:

  1. 01Scope. The smallest version that solves the problem is written down, including what it deliberately does not do.
  2. 02Design. Screens are laid out around real content and real tasks, on a phone first, then expanded for tablet and desktop.
  3. 03Build. The application is developed against that scope, with working software to review at each stage rather than a single reveal at the end.
  4. 04Launch and support. It goes live on your own address, the data behind it is secured, and the parts likely to change are the parts kept easiest to change.

The full list of what we build sits on the services page, and live examples are in the app showcase.

One codebase, every screen size

Modern web applications are built once and rendered responsively, so the same product works on a phone, a tablet, a laptop and a large monitor without four separate builds. Where a native presence helps, the same code can be packaged for the App Store and Google Play, so a small team is not maintaining separate versions of the same feature. Layouts are designed at the smallest size first, because a screen that works on a phone will almost always work larger, while the reverse is rarely true.

AI where it earns its place

Artificial intelligence is useful in an application when it removes a task a person would otherwise do manually: reading a photograph and producing a design, drafting a caption, sorting a long list, answering a question from your own documents. It is much less useful bolted on as a chat box that has no access to anything real. Our approach is to put the model behind a specific job with defined inputs and outputs, keep the surrounding rules in ordinary code where they can be tested, and design the interface so a person can see what was generated and correct it. That keeps results predictable enough to rely on.

Timelines, cost and how a quote is put together

Cost follows scope, not ambition. A focused tool with a handful of screens is a far smaller piece of work than a marketplace with accounts, payments and moderation, and the difference is almost always in the number of states a user can be in rather than the number of pages. We quote against the written scope, so additions are visible as additions, and we would rather cut a first release down than stretch a budget over features nobody has asked for yet. The starting points for each service are on the pricing page.

Making sure people can actually find it

An application nobody can find is an expensive hobby. Every build ships with the unglamorous foundations done properly: one clear heading per page, page titles and descriptions that say what the page is for, readable body copy that answers the questions visitors arrive with, internal links between related pages, a sitemap, and fast loading on a mid-range phone over mobile data. Increasingly that also means writing for answer engines — assistants that summarise rather than link — which reward plain statements of fact and specific detail over slogans. Our website design service covers that groundwork in full.

Questions we are asked most

Do I need to know exactly what I want before getting in touch?
No. A described problem and a rough idea of who uses it is enough to start. The first conversation is there to turn that into a scope you can read in one sitting.
Can an existing spreadsheet or paper process be moved across?
Usually, yes. Most applications begin as a spreadsheets, a notebook or a set of messages. We map the current process first, then decide which parts are worth automating and which are better left alone.
Who owns the finished application?
You do. The application, its content and its data belong to the client, and it runs on infrastructure that can be handed over or moved.

Have a problem worth solving? Tell us what it is and we will tell you what it would take.

Start a project

We use cookies to improve your experience. By continuing, you agree to our Privacy Policy.