Service — React & Next.js Development
React & Next.js Development
I build web applications with React and Next.js in TypeScript — interfaces made of clean, reusable components, connected to real data and comfortable on every screen.
React and Next.js are my core tools. React keeps an interface organised as it grows; Next.js adds what a real product needs next — routing, server rendering for speed and search engines, and secure authentication.
My largest build, FreshCart, is a complete Next.js store with accounts, a synced cart and checkout. If you need something interactive — a platform, a dashboard, a tool — this is where to start.
01 / React & Next.js Development
What a React / Next.js build includes
Every project is built so it can keep growing after launch, without the code turning into a tangle.
- Component architecture — every repeated piece built once and reused everywhere.
- TypeScript for safer code and fewer surprises when features are added.
- Data from your API with loading, empty and error states handled.
- Authentication and protected pages where the product needs accounts.
- Forms validated in the browser with clear, friendly messages.
- Responsive layouts from small phones to wide screens.
02 / React & Next.js Development
How we work together
It starts with a short message about what you need. I reply with questions, a clear plan and a realistic timeline. While I build, you follow progress on a live preview link you can open on any device — and at the end you get the code, the live site and a walkthrough.
What you get
- A React or Next.js application in TypeScript
- Reusable, documented UI components
- API integration with complete loading and error handling
- Deployment to Vercel with a live link
- Source code in your GitHub repository
Questions
Should my project use React or Next.js?
If the app lives mostly behind a login or inside the browser, React is often enough. If you need pages that load fast and appear in search, user accounts or a store, Next.js is usually the better choice. I'll recommend one based on your project, not habit.
Do you build the back end too?
My focus is the front end. I connect your interface to an existing API or service — like FreshCart, which runs on a ready e-commerce API — and I can work alongside your back-end developer.
Work that shows this
E-Commerce · Online Store
FreshCart
A complete online store: sign-up and password recovery, categories and brands, search with filters, wishlist, a cart that survives logging in, and checkout with cash or card.
Read the case study →Photography Blog · Arabic
Adasa
An Arabic photography blog with 28 articles — category filters, live search and pagination working together, shareable filtered links and a page for every article.
Read the case study →Travel Planning · Dashboard
Wanderlust
A travel-planning dashboard: pick a country and city, then explore holidays, long weekends, events, weather, exchange rates and sunrise times — and save the plans you like.
Read the case study →Related services
Figma to Code
Your Figma design turned into a pixel-accurate, responsive, interactive front end — built with clean, reusable components.
E-Commerce Front-End
Online store interfaces that sell — product catalogues, search and filters, wishlist, cart and checkout, connected to your store's API.
API Integration & Dashboards
Interfaces that come alive with real data — REST APIs wired in with loading, empty and error states handled, presented as clear dashboards.
Next Step
Have an idea worth building?
Let's turn it into an interface people remember — fast, responsive and built to last.
Usually replies within a day · Gaza, Palestine · working remotely worldwide
View my work