Front-End services
The half of your product people actually see.
Interfaces built against measured page-speed numbers, to the accessibility standard, and correct in Arabic as well as English from the first screen. What you keep is a documented component library, not a set of pages that has to be rewritten to add a feature.
SEECO and Athena SMP are both front ends we built and still run.
Overview
Front-End, the way we do it
The front end is where good systems are most often let down. A page that takes six seconds on a phone, a form that cannot be completed with a keyboard, an Arabic layout that was clearly added at the end. None of it shows up in a demo on a fast laptop in an office, and all of it shows up for the person trying to place an order.
We build interfaces against numbers rather than opinions: load time on a mid-range phone over a normal connection, measured before launch and after. You get a component library your own team can keep building on, in both languages, instead of a set of pages that has to be rewritten to add a feature.
What's included
What you actually get
- Quick on a mid-range phone, not only on a new one
- Usable with a keyboard and a screen reader, to the accessibility standard
- Arabic and English laid out the way each reads, from the first screen
- A component library, documented, that your developers can build on
- Page-speed numbers you are shown, before launch and after
How we work
Five steps, no surprises
- 01
We talk
A call or a WhatsApp thread. You tell us what is not working; we tell you honestly whether we are the right people.
- 02
We scope it
A written plan with what you get, what it costs and how long it takes. Fixed, so there are no surprises later.
- 03
We build it
You see it as it goes, not at the end. Changes are cheap while it is still being built.
- 04
We put it live
On infrastructure we set up and secure, tested before the launch date.
- 05
We keep it running
Updates, monitoring and someone who answers. Most clients stay on a monthly agreement.
Questions
About front-end
Can you work with a design we already have?
Yes. Send the Figma file, or just the current site, and we build to it. If there is no design, that is a separate piece of work we can do first so nothing gets invented during the build.
Do you rebuild, or improve what exists?
Whichever is cheaper for you. We look at what is there and say honestly which it is. Plenty of slow sites are a handful of fixable problems rather than a rewrite.
What does accessible actually mean here?
Keyboard navigation that works, contrast that passes, labels a screen reader can announce, and focus you can see. It is checked, not assumed.
Also
Related work
- Quality AssuranceFind it before your customers do.
- UX DesignWork out what it should do before anyone builds it.
- UI DesignScreens people can use without being trained.
- Design SystemsOne set of rules, so the tenth screen looks like the first.
- Mobile ApplicationsApps people keep on the first screen.
- iOSiPhone apps built the way Apple expects.
- AndroidAndroid apps that work on the phones people actually own.
- FlutterFlutter, when one team has to cover both stores.
- AIAI that does one job, properly.
- Machine LearningModels that earn their place in the business.
- Data ScienceAnswers from the data you already have.
- LLMsLanguage models, kept on a short leash.
- Generative AIGeneration with a human still holding the pen.
- PythonPython, for the work that has to be read as well as run.
- Back-EndWhere an order becomes an order.
- DatabaseThe part of your system that is hardest to fix later.
- Node.jsNode.js, for the systems that have to answer quickly.
- GoGo, where it has to be fast and stay simple.
- .NET.NET, for the systems a business runs on.
- JavaJava, for systems measured in decades.
- Web DevelopmentCompany sites, customer portals, and web systems that hold up.
- ReactReact, built so the next team can still work on it.
- AngularAngular, for systems that have to last.
Tell us what you have in mind.
An engineer reads your message and replies to you directly.
Talk to us