← nawal:~$ technologies

nawal:~$ technologies/typescript

TypeScript & React development services.

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.

  • ★ 5.0 on Clutch
  • US-timezone senior team
  • You own the code

What we build with TypeScript.

When a project needs a rich client app, this is our front-end stack.

01

Web apps & client portals

Customer-facing apps and self-service portals that feel fast and stay easy to change.

02

Admin dashboards & back offices

The screens your team lives in all day — tables, filters, workflows and reports that match how you operate.

03

Front ends for existing APIs

A modern interface on top of the backend you already run, without rebuilding everything behind it.

04

Design systems & components

A shared component library so every new screen looks consistent and ships faster.

05

JavaScript → TypeScript migrations

Add types to a growing JavaScript codebase incrementally — fewer runtime bugs, safer refactors, no big-bang rewrite.

06

Performance & accessibility

Faster loads, better Core Web Vitals and interfaces everyone can use — good for customers and for search.

nawal:~$ why-typescript

Why TypeScript — in business terms.

  1. 01

    Fewer bugs reach customers.

    Types catch whole classes of errors before code ships, instead of after a customer finds them.

  2. 02

    Easier to hand over.

    Typed code documents itself, so new engineers — yours or ours — get productive faster.

  3. 03

    One language for web and mobile.

    TypeScript runs in React and React Native, so business logic can be shared between your web app and your mobile apps.

nawal:~$ tools

The TypeScript & React toolbox.

Core
TypeScript · React
Frameworks
Next.js · Vite
Data
GraphQL · REST · TanStack Query
Styling
Tailwind CSS · design tokens
Quality
Vitest · Testing Library · Playwright

nawal:~$ engagement

Ways to work with us.

Need an engineering department, not just developers?

Fractional CTO + dedicated team

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?

Fixed-price project

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?

Ongoing support & evolution

Monthly support for what's in production — upgrades, monitoring, performance and the next features. Optional, never a condition.

nawal:~$ process

How we work.

Four phases. The first one is free — not as a discount, but because we won't quote a system we don't understand yet.

01

Discovery

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

02

Proposal

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

03

Build

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

04

Handover

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

TypeScript & React, answered.

Do you use TypeScript with Elixir?

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.

Can you work on our existing React app?

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.

Should we migrate our JavaScript to TypeScript?

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.

Who owns the code?

You do. Full repository, license 100% yours, at the close of each phase.

Got something that deserves to exist?

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.