Screenshot pending
XORV AnswerRank
A platform that helps brands understand how they appear, compete and get referenced across AI-generated answers.
Services
React & Next.js Development
This is the product side of my work. It is where XORV AnswerRank is built, and where the constraint is different: not “does the page look right” but “is the number on screen true, and does the interface say so honestly”.
Who this is for
Product teams and founders who need interface and front-end work on an application, not a brochure site.
Stack
ReactNext.jsTypeScriptPostgreSQLPHPLaravel
Problems
What this actually solves.
- The frontend derives its own truth
- When the interface computes analytics itself, two surfaces eventually disagree. The frontend should render truth, not derive it.
- Missing data rendered as zero
- Not measured, not available, refused and zero are four different states. Collapsing them into one number is how an analytics product loses trust.
- Density mistaken for insight
- More information on screen is not more understanding. Hierarchy is a product decision before it is a styling one.
- Bilingual added late
- Retrofitting RTL into a React application built without it is expensive. Locale and direction belong in the routing and layout architecture from the start.
What’s included
- React and Next.js App Router applications
- TypeScript end to end
- Server-rendered and statically generated surfaces
- Data-dense dashboard interfaces
- Design systems and reusable component libraries
- Bilingual routing with first-class RTL
- Accessibility and keyboard support
- Performance budgets and Core Web Vitals
- Interface implementation from design files
Approach
How the work runs.
Decide what a number may say
Every figure states what it counts and what it counts out of. If one input is unknown, no confident number is shown.
Server-first
Analytical work stays on the server. Critical content exists in the initial rendered HTML rather than behind a client fetch.
Typed contracts
One typed contract from the data layer to the interface, so a shape change fails at build time instead of in a user's dashboard.
Budget the bundle
Libraries are a cost. This site ships no animation library at all — the scroll reveal is one IntersectionObserver and a CSS transition.
Quality
What “done well” means here.
- Evidence one click away
- Claims drill down to what produced them. An analytics product that cannot be checked will not be trusted twice.
- Accessible by default
- Semantic landmarks, logical heading order, visible focus, keyboard paths and reduced-motion support — checked, not assumed.
- Long-term ownership
- Shipping a client site ends. A product does not — which changes how everything is written, named and structured.
Evidence
The projects that evidence this.
Every capability claim on this page is backed by delivered work.
Questions
Questions people actually ask.
- What have you built with React and Next.js?
- XORV AnswerRank, the SaaS product I am building — its data model, application logic, dashboard interface and the analytical layer behind it. This website is also a Next.js application, built statically and bilingually.
- Is this instead of your WordPress work?
- No — they answer different problems. WordPress and WooCommerce are where most of my commercial delivery happens. React and Next.js are where the product work happens. Knowing both is why I can tell a client which one their problem actually needs.
Contact
Have a site or store that needs to work better?
Tell me what is happening and on which page. A diagnosis is a useful first deliverable on its own.
I read every message myself and reply within one working day — usually with a question or two before anything else, because a scope worth quoting needs them answered.
Available for remote work aligned to EST hours
Mostafa Nouh
Full-Stack Developer & Product Builder
- linkedin.com/in/mostafanoah
- Location
- Egypt · Remote