Why Arabic projects outgrow the default setup
Lovable is a capable AI app builder. It turns a prompt into a React project, gives you a built-in backend called Cloud (database, auth, storage and edge functions, built on the open-source Supabase foundation), syncs both ways with GitHub, GitLab and Bitbucket, and publishes to a lovable.app address. For an English landing page or a SaaS prototype, that is a solid workflow.
The friction shows up when Arabic is the main language. When we checked Lovable's official documentation index on 5 November 2026, we found no guidance on right-to-left layouts or Arabic. That does not mean Arabic cannot work there; it means RTL is something you have to ask for, check and repair yourself, screen by screen.
In practice, Arabic builds made in English-first tools tend to show the same handful of problems:
- The whole page still reads left to right, so the logo sits on the wrong side and menus open the wrong way.
- Spacing uses physical left and right values, so cards and form labels look shifted once you flip the direction.
- Arrows and chevrons point backwards, which makes "next" look like "back".
- Phone numbers, prices and English brand names jump around inside Arabic sentences.
- The default font has no proper Arabic design, so text looks thin, cramped or mismatched.
If you are already on Lovable and only need to repair these, our step-by-step RTL fix guide for Lovable has the exact CSS and Tailwind changes, and there is an Arabic version you can share with your team.
What changes when Arabic is the starting point
Uttra was built for Arabic speakers from the first screen. The interface, the content and the generated layouts are Arabic and right-to-left by default, and the builder understands requests written in Modern Standard Arabic or in a Gulf dialect.
A few things matter for Arabic work in particular:
- Visual editing on the live preview. Click a heading, paragraph, button or section, then change its text, colour, size, alignment or font from a panel, without opening code.
- Targeted instructions. Select one element and type "make this section two columns" so the change applies only there.
- Self-testing. Uttra opens the pages it builds in a real browser, looks for errors, blank pages and overlapping elements, and fixes what it finds before telling you it is done.
- Arabic support. The team answers in Arabic over WhatsApp or email.
Each project also runs in a full environment with a terminal: Node, Python, PHP or Go, and SQLite, PostgreSQL or MySQL.
Lovable and Uttra side by side
| Topic | Lovable | Uttra |
|---|---|---|
| Arabic and RTL | No RTL guidance found in the official docs index (checked 2026-11-05) | Arabic-first interface and RTL output by default |
| Backend | Built-in Cloud on a Supabase foundation, or your own Supabase project | Backend and database run in the project environment: SQLite, PostgreSQL or MySQL |
| Code ownership | Two-way Git sync with GitHub, GitLab and Bitbucket; zip download on paid plans | Push to your own GitHub repo, import existing repos, or download through the terminal |
| Hosting | Publishes to a lovable.app address; custom domains on paid plans | Publishing from the Pro plan, automatic SSL, custom domain at no extra cost, .sa included |
| Pricing model | Credit-based plans, priced in USD on lovable.dev | Credit-based plans in SAR, VAT included, paid with mada, Apple Pay or cards |
You can see every Uttra plan, with credits and hosting limits, on the pricing page. The free Hobby plan gives you 600 one-time credits to try building and previewing; publishing to a public link starts with Pro at 99 SAR a month.
Where Lovable is the better pick
Lovable may suit you better if:
- Your product is English only and RTL will never matter.
- Your team already runs its backend on Lovable Cloud or Supabase and you do not want to move data.
- You rely on Bitbucket or GitLab sync; Uttra's documented Git workflow is built around GitHub.
- You want unlimited workspace members on a credit plan rather than per-plan seats.
If these describe you, staying put and fixing RTL with the guide above is reasonable.
Moving an existing Lovable project
Because both tools work with real code in Git, moving is mostly a repository move, not a rebuild.
Sync the project to GitHub
In Lovable, connect GitHub and let it push the full codebase to a repository you own.
Import the repository into Uttra
Create a new project in Uttra and import that repository. Uttra reads the code, installs dependencies and runs it in its own environment.
Plan the backend
If the app uses Lovable Cloud for data or login, export the data first and decide where it will live. Ask Uttra to set up the database and point the app at it.
Ask for the RTL pass
Request a full right-to-left review: direction, logical spacing, mirrored icons, Arabic font and mixed numbers. Then check the preview on a phone width.
Publish on your domain
Publish from the Pro plan and connect your domain, including a .sa domain, by adding the DNS records Uttra shows you.
For the Git side in more detail, see the GitHub sync guide.
When Uttra is the calmer choice
Choose Uttra when Arabic readers are your main audience and you would rather describe the business than debug the layout: a restaurant menu in Riyadh, a clinic booking page in Dammam, an abaya store that takes orders. You also get local billing in riyals with a tax invoice, and support in Arabic.
If you are unsure, build the same small page in both tools with an Arabic prompt and compare the first result on your phone.