React development
React applications for the work a website cannot do.
Dashboards, customer portals, internal tools and product MVPs. Built in React and TypeScript, delivered with the repository, the pipeline and the documentation in your own accounts.
In one paragraph
Latx Technologies builds React web applications — role-based portals, dashboards, internal tools and workflow systems — with React on the front end and a Java or Node back end. Projects are scoped in writing, priced fixed against that scope, and delivered with the repository, the deployment pipeline and the documentation in the client’s own accounts. Our largest to date is a scholarship management portal running an entire application lifecycle end to end.
A worked example
What one of these actually looks like.
Abstract capability lists are easy to write and hard to judge. Here is a real system instead, described in enough detail to argue with.
A scholarship management portal, React and Java
It runs an entire scholarship programme: publishing the opportunity, collecting applications, gathering recommendation letters, scoring with judges, picking winners, sending the letters, and keeping every record queryable by cycle year.
Applications move through nine states the system enforces, five roles have permissions checked on the server for every request, and every state change writes an audit entry that cannot be edited afterwards.
The interesting decision was not technical. Recommenders have no reason to learn your software, and the whole cycle stalls on them, so they get a single expiring link and no account at all.
What we build
Four shapes of React project.
Different problems, but the same underlying job: give a set of users a screen that holds the state of something real.
-
Internal tools and admin panels
The dispatch board, the approvals queue, the inventory screen. Usually replacing a spreadsheet that has outgrown itself and a group chat nobody can audit.
-
Customer portals and dashboards
Where your customers check status, download documents, raise a request, or see their own numbers — without emailing someone on your team to ask.
-
SaaS MVPs
Scoped to answer one question about the market. Everything that does not help answer it is cut from version one and written down for later.
-
APIs and integrations
The layer between your application and the systems it has to talk to — payments, logistics, accounting, a CRM, or an existing database you are not replacing.
How it runs
Five stages, in this order.
The same five stages as every other project, with the React specifics named at each one. The full version is on the process page.
-
Stage 01
Write down what it must do
User roles, the screens each role needs, and the rules that decide who can see and change what. Written as plain sentences you can check, not as a technical document you have to take on trust.
- You approve
- The scope and the fixed quote
-
Stage 02
Data model before interface
What entities exist, how they relate, and what happens to each one over its life. Nearly every expensive rewrite we have been called in to fix started with skipping this step.
-
Stage 03
A thin slice, end to end
One real workflow built all the way through — interface, API, database, deployment — before the rest is started. It surfaces the wrong assumptions in week two rather than week ten.
- You get
- a working URL you can use, early
-
Stage 04
Build out, with tests where they earn it
Typed end to end, tested on the logic that would cost money if it were wrong, and reviewed. Not a coverage target for its own sake — tests on the parts where a bug is expensive.
-
Stage 05
Handover into your accounts
The repository, the hosting, the database and the domain all in your name, plus a README that lets another developer run the project locally on their first day.
Common questions
React, answered plainly.
When do I need a web application instead of a website?
When users sign in and each one sees their own data, when permissions decide who can do what, and when the content is generated by usage rather than edited by a person. If none of those are true, a WordPress or Shopify site will do the job for less money.
What does a React project include?
A written scope of roles and screens, a data model agreed before the interface, one workflow built end to end early, then the rest built out with tests on the logic that matters. Delivery includes the repository, the deployment pipeline and documentation in your own accounts.
Can you build an MVP first?
Yes, and it is usually the right call. An MVP should be scoped to answer one specific question about the market, with everything that does not help answer it deferred and written down. We will push back on an MVP that quietly contains the whole product.
Who owns the code?
You do, with the full commit history, in a repository in your own account. Hosting, database and domain are registered to you. There is no framework of ours in the middle that you would have to keep paying for.
Proof
React projects.
Each case study covers the brief, the build, what went wrong, and what changed after launch.
-
Scholarship Portal
The whole scholarship lifecycle in one system: applications, letters, judge scoring, awards and records.
Start here
Tell us what the site has to do.
A few lines is enough. A developer reads it and replies within one business day — with questions, or with a rough shape of the work.