Home / Development & Technology / Web applications

Development & Technology — Web applications

Web application development for the process behind the page

Portals, dashboards and workflow tools, built on WordPress, Magento or a standalone stack. One team in Nijmegen, scope agreed before anyone writes code.

Let's start building →
✓Fixed scope before we start ✓Code and repository stay yours
20Years in the market◆ 500+Satisfied clients◆ 98%Project delivery rate◆
In short

What is web application development?

Web application development builds software that runs in a browser and does work: people log in, enter or look up data, and something happens. A website explains; a web application carries out a process. The two are built differently from the first sketch onwards.

The starting point

Most web apps replace a spreadsheet

The request rarely starts as software. It starts as a shared file that four people edit, a mailbox used as a queue, or a process that only one colleague fully understands.

So the first question a web application development agency should ask is not which framework. It is which steps the process actually has, who owns each one, and where the data already lives.

Worth building against 200ms is the longest a screen may take to respond to a tap or click before Google counts the interaction as slow. Google's Core Web Vitals threshold for Interaction to Next Paint, at the 75th percentile. Source: web.dev.
What the work consists of

Two halves, in the order they happen

The build gets the application into use. The second half keeps it usable.

The build

Custom web application development, step by step

Web app development is a process problem before it is a code problem. We map the steps, the roles and the data, then build the version that is small enough to put in front of real users.

Process and role mappingEvery step, who performs it and what it needs to continue
Data model and integrationsWhere each field lives, and which system stays the source of truth
Interface built for repeat useScreens that someone works in all day, not visits once
After launch

What happens after the first version is live

A web application changes because the process does. What matters after launch is that it can be changed safely, by whoever maintains it next.

Monitoring and error reportingA failure lands in a log and an alert, not only in a support call
Updates and dependency maintenanceFramework and library updates applied on a schedule
Documented handoverRepository, environments and deployment written down, not remembered

A named developer stays with the project from scope through launch.

Choosing the route

Inside WordPress or Magento, or standalone?

Both routes are in our stack. Which one fits depends on where the users and the data already are.

Inside your CMS or shop WordPress or Magento

Suits an application whose users and content already live there: a client portal behind a WordPress login, a quote tool inside a Magento shop, a dashboard reading the same data as the site.

  • →Existing accounts and roles reused rather than rebuilt
  • →One place to host, update and back up
  • →Custom plugins or modules instead of stacking third-party ones
  • →Platform updates set the pace for yours

Standalone application Its own stack

Suits an application with its own users, its own permissions and real volume: an internal tool, a planning system, something a CMS would only get in the way of.

  • →Permissions and roles modelled on your process, not the platform's
  • →API-first, so another system can use it later
  • →Hosting sized for the load instead of for a website
  • →A longer first build than extending what you already run
Design

UI UX design for software people use every day

A tool used daily is judged on the twentieth visit, not the first. So we design the frequent path to be short, and the rare path to be findable.

Research with the people who do the workThe colleague in the process, not only the manager who signs off
The frequent task in the fewest stepsMeasured in clicks, not in opinions
Empty, slow and error states designedThose screens decide whether the tool gets used

More on our approach to UX for B2B tech →

How a build runs

Four phases, and the decision that is yours in each

No phase starts before the previous one is signed off, which is what keeps a build from drifting. Click through to see what happens and what we need from you.

Every phase ends with something you can look at

A scope document, a clickable prototype, a working version on a test environment and a handover in your own hosting. Each one is signed off before the next phase opens.

Phase 1

Scope

    What every build includes

    Agreed in the proposal, delivered in the project

    • ✓A scope document with the process and roles agreed
    • ✓Screen flows designed and approved before the build
    • ✓A working test environment you can log in to during the build
    • ✓Roles and permissions implemented and checked per role
    • ✓Integrations tested with real data, not sample data
    • ✓Monitoring and error reporting switched on before go-live
    • ✓Repository and environments handed over in your own accounts
    • ✓A documented handover to whoever maintains it next
    Next step

    Tell us the process, we'll scope the application

    One call about the steps, the roles and the systems involved is usually enough to say what version one should be.

    Before you ask

    The questions we actually get asked

    What is the difference between a website and a web application?

    A website presents information; a web application does work. Once people log in, enter data and expect something to happen, you are building software. That changes the testing, the hosting and the maintenance, which is why the two are quoted differently.

    What does web application development cost?

    Three things move what a web application development company can quote: how many roles log in, how many systems it talks to, and how much of the process is in version one. A single-role dashboard reading one database is a different project from a multi-role portal connected to an ERP. You get one fixed figure after scoping.

    Can you build it inside our existing WordPress or Magento?

    Often, and it is usually the cheaper route when the users and the data are already there. The limit is permissions and volume: when roles get complex or the load is heavy, a standalone application is less work than bending the platform. We say which during scoping.

    How long before we can use something?

    The point of scoping version one tightly is that it reaches real users early. A first usable version typically arrives well before the full scope is finished, because the frequent path is built first and the rare cases follow.

    Who owns the code and the repository?

    You do. The repository and the hosting accounts are in your name, and the code is handed over with documentation on how to run and deploy it. You can move the work to another party without asking us.

    Can another developer take over the application later?

    That is what the handover is for: a documented repository, named environments and a deployment process written down rather than remembered. We also hand over to your own developers if they are joining later.

    Still have a question?

    Talk to a specialist

    A short call usually answers more than a form does — about scope, platform, timing or anything else you want to know first.

    Ask a question →
    VisitNijmegen
    Start with the scopeFixed before we build
    Let's talk →
    Bumpp AI

    Ask about Bumpp’s digital marketing services.

    How can we help?

    Ask about SEO, websites or working with Bumpp.