WeWeb developer · Xano + WeWeb

WeWeb developer with production migration experience

I've built WeWeb front ends on Xano backends, and I worked on a production WeWeb app that evolved for about 1.5 years before we replaced it with React + TypeScript. So I can tell you honestly when WeWeb is the right tool and when it's time to move on.

📅 Book a free call ✉ Email me CV

Xano + WeWeb, end to end
WeWeb → React migration shipped
Role-aware screens
Remote, UTC+1

Results

Measured on real projects.

~1.5 yrsa production WeWeb app evolved before the React move
3Xano + WeWeb products at Soraia
BatchesReact pages shipped inside WeWeb while the app stayed live
React 19 + TSthe replacement frontend

Case studies

WeWeb work on real products. Client code stays private.

Production ATS, CRM & AI recruitment platform for a Spanish recruitment company

Built at Soraia (Italian AI/software agency) for a Spanish recruitment company · 2024–2026

Production WeWeb front end on a Xano backend: candidates, companies, contacts, activities, opportunities, Kanbans, dashboards and settings.
As the product grew, page and component loading felt slow; the team tested React on an internal dashboard, agreed it with the client, then replaced the WeWeb frontend.
New React pages were embedded into WeWeb during the transition, with WeWeb authentication kept until the final cutover; the client tested pages before each batch shipped.
Cloudflare deployments mirrored Xano's development, staging and production environments.

React
TypeScript
PostgreSQL
Xano
OpenAI
WeWeb

Guest management MVP

Saudi events client · built at Soraia · 2024–2026

Guest intake, flight information, accommodation and transport logistics in one platform.
JotForm → Make.com → Google Sheets automation synced to the platform database, with project-specific routing.
Airport pick-ups with driver and car assignment; responsive for staff on the move.

Xano
WeWeb
Make.com
JotForm
Google Sheets

Confidential public-sector MVP

Confidential public-sector client · built at Soraia · 2024–2026

Built a confidential public-sector workflow MVP with Xano and WeWeb.
Project details remain confidential.

Xano
WeWeb

What I can do on your WeWeb project

Build WeWeb apps on Xano: auth, CRUD screens, forms, data grids, dashboards, Kanban boards
Connect WeWeb to Xano endpoints and design the backend behind them
Responsive internal tools that work for staff on phones
Role-aware screens that match backend permissions
Speed up slow pages by fixing the Xano side (indexes, pagination, smaller responses)
Plan and run a staged WeWeb → React + TypeScript migration when you need one

FAQ

Quick answers before we talk.

Do you do both WeWeb and Xano?

Yes. My WeWeb projects ran on Xano backends I worked on, so I can fix a slow page wherever the real cause is. See my Xano developer page.

When should I move from WeWeb to React?

When the product has grown enough that loading speed, maintainability or consistency become a daily cost. We did it on a production ATS/CRM after validating React on an internal dashboard first. If WeWeb is still the cheaper choice for you, I'll say so.

Can you migrate without a big-bang rewrite?

Yes. We embedded new React pages inside the live WeWeb app, kept WeWeb authentication until cutover, and shipped pages in batches. See my React developer page.

Do you work remotely?

Yes, fully remote, from Oran, Algeria (UTC+1). English, French and Arabic.

How do we start?

Book a free call or email me at abdelmoulabilel2000@gmail.com with a short description of the app.

Let's build it properly

Tell me what's slow, messy or missing. A short call is enough to see if I can help.

📅 Book a free call ✉ abdelmoulabilel2000@gmail.com