Frontend development
Frontend development and markup to order: we build an interface that holds up equally on a phone and on a wide monitor, opens fast and stays readable on real data. We take the project as a separate stage or place a developer inside your team.
The frontend is everything a person sees and touches, which is where a product earns its reputation. The difference between "it is built" and "it works" usually hides in the details: how a screen behaves on a slow connection, what happens with a very long product name, whether a filled-in form survives an accidental page refresh.
A screen is not one picture but a dozen states: loading, an empty list, a network error, insufficient permissions, very long text, a very old browser. We plan for them from the start, because adding states on top of finished markup costs more than allowing for them at the beginning.
Speed and accessibility are work of their own. Server-side rendering, sensible page weight and careful handling of images and fonts give both a fast first screen and good positions in search. Accessibility adds keyboard navigation and correct markup, and widens the audience of the product along the way.
There are two ways to take the frontend. As a separate stage, when the design and the server side already exist or are being built in parallel. Or as a developer inside your team under the outstaffing model, if your own people are short on time or capacity. If there is no design yet, you can start with prototyping on a ready set of components and add the full styling later.
The frontend runs alongside web development and mobile apps. Interfaces we have built can be seen in the cases from the Ubix.Network ecosystem: the wallet, the exchange, the staking platform, the network explorer and the ecosystem analytics, as well as in Silent Notary, SignItNow and Battle of the Bees.
What the service covers
Any combination of the items below can be taken on its own.
Screens for every size, from a phone to a wide monitor, checked in real browsers rather than only in the design file.
An SPA where the product is closer to an application, server-side rendering where the speed of the first screen and search matter. Often this is the same application in two modes.
Connecting to your server side or to external services, handling request states, caching, retries and clear messages when something fails.
Components, themes, states and documentation for them, so new screens are built quickly and look part of the product.
Page weight, loading in chunks, images and fonts, markup, keyboard navigation, contrast.
We step into an existing frontend, work out how it is built, put it in order and keep developing it.
How we work
We look at the layouts, the server side and how the product is going to grow. The output is the list of screens, their states, the risks and an estimate.
We build the base: project setup, routing, core components and themes. After that the screens go quickly and consistently.
Two-week iterations, each of which can be opened by a link and tried on your own phone.
We connect the data, go through the states and run it on a slow network and on realistic volumes.
We ship it, watch browser errors, measure speed and refine based on feedback.
Stack and tools
Cases for this service
Frequently asked questions
Yes, that is a common scenario. We work from your layouts and with your server side, and we flag the gaps in the specification before the build starts.
We can build it together with design, or start with prototyping on a ready set of components where the task allows. The second path is cheaper and suits internal systems, where convenience matters more than individuality.
Vue and Nuxt are our main tools, and we also work with React. If your stack is different, we will say plainly where we need time to get up to speed and account for it in the estimate.
We will. First we work out how it is built and assess its condition, then we say plainly what is cheaper to put in order and what to rewrite.
Everything is set by the contract, and we put it in writing at the specification stage, before the work starts. During the project the team works either on our infrastructure or on yours: the choice depends on the complexity of the project and on whether you already have infrastructure in place. Every approved stage is transferred to your servers and your repository, so the work accumulates on your side rather than ours. Once the project is closed, all code, materials and documentation are handed over to you together with the rights to them.
Yes, under a separate agreement: development, dependency updates and on-call duty.
Related services
Shall we discuss your task?
Tell us what needs to be done and we will come back with an estimate, the team composition and a plan for the first two weeks.