Fast on real phones
We budget performance the way we budget cost — measured on mid-range hardware and throttled networks, not on our own machines.
01 Web applications
Websites are easy. Products are not.
- SvelteKit
- Next.js
- TypeScript
- Tailwind
- Cloudflare
Anyone can deliver a page that looks right on a designer's laptop. We build interfaces that stay fast on a mid-range phone, on a bad connection, on the busiest day of your year.
Start a projectWhy the app you paid for feels slow
- 01 Beautiful in the demo, unusable on a three-year-old Android phone
- 02 Every new screen makes the whole thing heavier and slower
- 03 Works in Chrome on the developer's machine, breaks elsewhere
- 04 Nobody can add a feature without breaking two others
↓
You do not need another redesign. You need an interface built so that adding to it is safe and speed is not something that degrades over time.
What you get
Accessible by construction
Keyboard navigation, contrast, and screen-reader semantics built into the components, so accessibility is not a report you get at the end.
Works in every language you sell in
French, Arabic, and English including right-to-left layout, handled at the framework level rather than bolted on later.
Safe to change
Typed end to end and covered by tests, so the sixth feature is as safe to ship as the first.
How we build it
- How we deliver it
- SvelteKit / Next.js
- Server-rendered by default: the page is useful before the JavaScript arrives, which is what makes it fast on weak devices and good for search engines.
- TypeScript strict
- The compiler rejects whole classes of mistake — missing values, wrong shapes, unhandled cases — before anything reaches your users.
- Cloudflare, in front of the app
- Your interface and assets are served from a global network, so a visitor in Casablanca and one in Dubai get the same response time. This sits in front of your backend — it does not replace it.
- Design system, not pages
- One set of components used everywhere. A change to a button is a change everywhere it appears, not a hunt through forty files.
When to bring us in
Every project starts with a scoping call- ↳ Your app is slow and nobody can tell you why
- ↳ You are launching a product, not a brochure site
- ↳ Your users are on mobile data and mid-range phones
- ↳ You sell in more than one language and need Arabic done properly
- ↳ Every release breaks something that used to work
- ↳ You inherited a codebase and need someone to take it seriously
What we build
Services- 02 Backend systems You need failure contained instead of total, your business rules written down once, and a backend chosen for the load you actually expect — not for whatever the last team happened to know. ElixirPhoenixNode
- 03 Mobile applications You need one codebase that treats both platforms as first class, works offline, and is still buildable in two years. React NativeExpoTypeScript
- 04 Custom software The work already has a process. Software should encode that process, remove the retyping, and let you see what is happening without asking someone. ElixirAshTypeScript
- 05 Cloud & delivery Infrastructure should be written down as code, reproducible from scratch, and monitored — so recovery is a procedure rather than a rescue. CloudflareTerraformRailway
Let's make it fast.
Send us the URL or the idea. We will tell you what is actually wrong and what it takes to fix it.
Start a project hello@elixiria.ma