Websites people can find and use
Service websites, product pages and content-led sites need a clear structure as well as a visual identity. Navigation, mobile layouts, accessible text and crawlable content all belong in the brief.
Spacewalk services · Available worldwide
Web application development
A website explains what you do. A web application helps someone get something done: find a vehicle, manage a booking or use a service. The starting point is the task your users need to complete.
Spacewalk builds websites and web applications with React, Next.js and Node.js. We combine interface design with the application logic and data behind it, for projects in Sri Lanka and worldwide.
What the work can include
Applications built around a workflow
For a portal, marketplace or internal tool, start with the actions people take and the information they need. User roles, validation, search and error recovery often matter as much as the first screen.
Data and integrations
A web application may need to connect to an existing database or external service. Identify the system that owns each record, the permissions required and what should happen when a connection is unavailable.
What to bring to a web project
A short description of the users and their main task is more useful than a long feature list. Include examples of the current workflow, any existing website and the systems the new application needs to connect to.
Separate the first release from later ideas. The project brief should also settle content ownership, hosting, access to source code and support after launch. If those decisions are still open, include them in your enquiry so they can be discussed before the scope is set.
Explore related projects
Questions before you start
Do I need a website or a web application?
If visitors mainly read about your services and contact you, a website may be enough. If they sign in, change records or complete a multi-step task, application development is likely part of the work.
Can an existing site be part of the project?
Include its URL, the parts you want to keep and the problems you want to address. Existing content, integrations and search traffic should inform whether to improve the current site or plan a replacement.
What affects the cost and schedule?
The number of workflows, integrations, user roles and content requirements all affect scope. Send the main requirements and any target date to discuss an estimate; a fixed price or delivery date needs a defined brief.