We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
nawal:~$ technologies/typescript
Web apps, client portals and admin dashboards with typed, maintainable front ends — on top of an Elixir backend, or plugged into the API you already have.
When a project needs a rich client app, this is our front-end stack.
01
Customer-facing apps and self-service portals that feel fast and stay easy to change.
02
The screens your team lives in all day — tables, filters, workflows and reports that match how you operate.
03
A modern interface on top of the backend you already run, without rebuilding everything behind it.
04
A shared component library so every new screen looks consistent and ships faster.
05
Add types to a growing JavaScript codebase incrementally — fewer runtime bugs, safer refactors, no big-bang rewrite.
06
Faster loads, better Core Web Vitals and interfaces everyone can use — good for customers and for search.
nawal:~$ why-typescript
Types catch whole classes of errors before code ships, instead of after a customer finds them.
Typed code documents itself, so new engineers — yours or ours — get productive faster.
TypeScript runs in React and React Native, so business logic can be shared between your web app and your mobile apps.
nawal:~$ tools
nawal:~$ engagement
Need an engineering department, not just developers?
A CTO who joins your leadership conversations and a senior squad that builds. One point of accountability for architecture, timelines and delivery.
Have a defined system to build?
A free one-week discovery, then a proposal with scope, timeline and a closed price per phase. Demo every Friday; the code is yours.
Already live and need it kept healthy?
Monthly support for what's in production — upgrades, monitoring, performance and the next features. Optional, never a condition.
nawal:~$ process
Four phases. The first one is free — not as a discount, but because we won't quote a system we don't understand yet.
We sit with the people who do the work, not just the person who called us. We map how the operation actually runs — including the workarounds nobody documented. You keep the map either way.
1 week · free
Scope, sequence, timeline, closed price — written so you could hand it to someone else and they'd understand it. You sign it or you don't.
1 week · fixed
Two-week sprints. A working demo every Friday, run by the engineer who built it. Slack and repo access from day one — you can watch commits land.
8-24 weeks
We train your team on the system they now own. Monthly support if you want it, never as a condition. The code works without us.
ongoing · optional
nawal:~$ questions
Often Phoenix LiveView covers the interface without a separate front end. When a project needs a rich client app — complex editors, offline-heavy screens, or code shared with mobile — we use TypeScript and React on top of Phoenix APIs.
Yes — new features, performance, refactors, or stabilizing a codebase that's become hard to change. We start by reading what's there before proposing anything.
If the codebase is growing and bugs keep slipping through, usually yes — and it can be done file by file while you keep shipping. We'll tell you if it isn't worth it.
You do. Full repository, license 100% yours, at the close of each phase.
nawal:~$ related
Tell us what you're trying to solve. Within 24 hours you'll have a call booked and a first read on it — no cost, no commitment, no fine print.