Consulting
React development for web apps and portals
I build and improve React and TypeScript web products, from customer portals to internal dashboards. Based in Barcelona, I work remotely with teams in Europe and the US. We choose client rendering, server-side rendering or prerendering based on how people find and use the pages; authentication, API access and permissions are part of the product design.
What you get
- React interfaces and product flows shaped around your users and agreed requirements.
- TypeScript components and data flows integrated with your APIs and authentication.
- A rendering approach selected for the product, including SSR or prerendering when it serves the content and discovery needs.
- Accessibility and browser checks, useful tests, and a documented handover to code and accounts you own.
How it works
- Map users and access Clarify the key journeys, roles, data permissions, existing code and how each page needs to be discovered or used.
- Build the web experience Implement the React and TypeScript interface, connect APIs and authentication, and choose rendering to match the product.
- Review and hand over Check accessibility, behavior and performance across agreed browsers, then document the code and deployment setup.
A good fit if
- You need a browser-based product such as a portal, dashboard or interactive customer app.
- You want React and TypeScript work on a new product or an existing codebase.
- You need public content and private, permission-based product areas designed together.
Choose rendering around how people use the product
A public page that needs to appear in search can have different rendering needs from a private dashboard behind sign-in. We choose client rendering, server-side rendering or prerendering based on the content, discovery path and operating setup, then check the result in real browsers.
- Identify which pages are public, indexable or restricted to signed-in users.
- Plan API calls, loading states and access rules around each user role.
- Check navigation, keyboard use and performance across the browsers in scope.
Make permissions and delivery part of the design
Portals and dashboards often bring sensitive records and different user roles together. Define what each role can see and do, how the app handles API errors, and what your team needs to run the product after handover. Keep QA and production settings distinct where the agreed environment calls for it.
- Agree roles, permissions and API boundaries before building the main flows.
- Include accessibility, browser coverage and monitoring needs in the scope.
- Estimate the product slice with the calculator and confirm the engagement details.
FAQ
Is React web development the same as React Native?
No. This service covers browser-based websites and web apps built with React. React Native is a separate approach for mobile apps; the choice depends on whether your product needs a web experience, a native mobile app or both.
Can you improve a React app we already have?
Yes. I can inspect its components, routing, data access, authentication and build setup, then propose changes that fit the existing project where practical.
What affects the cost and scope?
User roles, workflows, API integrations, rendering needs, accessibility and browser support all affect scope. Start with the app cost calculator, then review pricing and agree a specific plan.
How does handover work?
The code and project access remain in accounts you own. Handover can include setup and deployment notes, plus a clear separation between QA and production configuration when that is part of the agreed scope.
Contact
Discuss React web app development
Tell me what you're building. Remote-first from Barcelona — we start with a short intro call.
Skip the form and grab a slot straight away.
Book a 30-min call