This is a 10-lesson vibe coding course where each lesson teaches one concept and gives you one exercise to apply to your own project. You start by understanding how the AI works and writing your idea clearly, move on to planning and data, build step by step, then add sign-in, local payments, testing and deployment. By the end you have a real, published app and a method you can repeat on any project.
- vibe coding course for beginners
- learn vibe coding step by step
- free vibe coding tutorial
- vibe coding in arabic
- how to learn to build apps with ai
What is this vibe coding course, and how do you use it?
If you want to learn vibe coding in a practical way, in Arabic or English, this course is built for you: ten short lessons, each with one concept and one exercise for your own project. No coding experience needed, just one clear idea and about an hour per lesson. New to the term? Read What is vibe coding? first.
The premise is simple: vibe coding is not magic where one sentence produces a finished app. It is a skill with a method, and the lessons build on each other, so do not jump to deployment before the data lesson.
| Lesson | Topic | Exercise output |
|---|---|---|
| 1 | How the AI thinks | An understanding of the model's limits and context |
| 2 | The idea in one paragraph | A paragraph naming the user, problem and solution |
| 3 | Screens and journeys | A screen list and a 3–5 step core path |
| 4 | Data before interface | Tables and relationships in plain words |
| 5 | Ask for the plan first | An approved plan before any code |
| 6 | The smallest working version | A core path that works end to end |
| 7 | Changing and fixing | Small requests and restore points |
| 8 | Sign-in, payments, local touch | OTP, local payments and RTL |
| 9 | Testing and security | A completed checklist |
| 10 | Launch and first users | A live link and feedback from 10 users |
Lessons 1–3: understand the tool and write your idea clearly
Lesson 1: how the AI that builds for you thinks
A language model reads what you write plus whatever sits in its context window, then predicts the best code for your request. Whatever you do not say, it guesses, and guesses cause most surprises. A modern agent like the Fanann Agent plans, writes and tests, but it still depends on how clear you are.
Exercise: write down three things your customers know about your business that no model could: 'customers book after evening prayers' or 'we are closed on Fridays.'
Lesson 2: the idea in one paragraph
Write 4–6 sentences: who is the user, what is their problem, and what one thing must the app do brilliantly? If you need a page, trim the idea.
Lesson 3: screens and the core path
Turn the paragraph into a list of screens (home, details, booking or order, confirmation, admin) and write the core path in 3–5 steps: 'the customer opens the link from WhatsApp, picks a service, picks a time, confirms with their phone number.' Everything else waits.
Lessons 4–5: data before interface, plan before code
Lesson 4: design your data in plain words
Most problems in AI-built apps start with a database nobody thought about. You do not need jargon. Write down what your app stores and how those things relate: 'a customer has many bookings; each booking is for one service and one staff member; a service has a price and a duration.' Those sentences alone prevent a lot of pain later. Go deeper with database design for non-developers.
- List every 'thing' you store: customers, orders, products, appointments, staff.
- For each, write the 4–6 most important details: name, phone, status, date.
- Write the relationships: who owns what, and how many to how many.
- Write the rules: no double bookings, no order without a phone number, prices include VAT.
Lesson 5: ask for the plan first
Before anything gets built, send your paragraph, screens and data and ask the agent for a plan only: pages, tables, permissions and build order. Changing a line in the plan costs a minute; changing it after the build can cost hours.
I want to build a booking app for a home-service women's salon in Jeddah. Users: customers who book a service at home, and a supervisor who manages appointments and staff. Core path: the customer picks a service, then a day and time, enters her National Address, then confirms with an OTP code sent to her phone. Data: customers, services (price and duration), staff, bookings (status: new, confirmed, done, cancelled). Rules: a staff member can never have overlapping bookings, and Friday is a day off. The interface is Arabic-first, right-to-left. Do not write any code yet: show me the plan (pages, tables, permissions, build order) and wait for my approval.
Try it in FanannLessons 6–7: build the smallest working version, then change it wisely
Lesson 6: the core path, end to end
Once the plan is approved, ask for the core path only: no coupons, reports or notifications yet. A brand-new customer must be able to finish the whole flow. That is your first version, your MVP.
Lesson 7: changing and fixing without the spiral
- 1One change per message
Three edits in one message hide what changed. Send them separately.
- 2Describe bugs in three lines
What you did, what you expected, what happened. Add a screenshot.
- 3Keep a restore point
Before big changes, have a good version to return to.
- 4The three-attempt rule
If a bug survives three attempts, roll back to the last good version and explain the problem from scratch with a concrete example.
This method is covered in depth in build one feature at a time and how to fix bugs in an AI-built app.
Lesson 8: sign-in, payments and a gulf-ready experience
This is where a prototype becomes a product for real customers in Saudi Arabia and the UAE. Ask for each of these in conversation:
| Element | Why it matters | How to ask for it |
|---|---|---|
| Phone-number sign-in | The phone is the main identity, and passwords get forgotten | 'Sign users in with their phone number and an OTP code' |
| Local payments | Customers expect mada and Apple Pay, sometimes Tabby and Tamara | 'Add mada and Apple Pay, and confirm the order only after the gateway confirms payment' |
| A real RTL interface | A wrong layout direction kills trust instantly | 'Arabic-first, right-to-left, with English as a second language' |
| Dates and hours | Ramadan, Eid and the weekend change the schedule | 'Show Hijri next to Gregorian dates and apply Ramadan hours' |
For payment details read the guide to mada, Apple Pay, Tabby and Tamara.
Lesson 9: test like an annoyed customer
A beautiful screen does not mean a sound app. Spend this lesson testing, and ask the agent to review its own work too:
- Create two accounts and try, from the first, to view the second account's data by editing the URL.
- Complete the core path on a phone, in Arabic and then in English.
- Cancel a payment halfway and confirm the order is not marked paid.
- Enter bad data: a short phone number, a past date, an empty field.
- Confirm the admin dashboard only opens for the admin.
- Ask: where is customer data stored, and are there backups?
Review the app as a strict QA tester: list any page that could show one user's data to another, any form without input validation, any English text visible in the Arabic interface, and any place where an order counts as paid before the payment gateway confirms it. Show me the list and proposed fixes, and do not apply them until I approve.
Try it in FanannLesson 10: launch and invite your first 10 users
Launch is where the real learning starts. Connect your domain, make sure SSL is on, and deploy. In Fanann, apps deploy to in-region hosting with daily backups and instant rollback to any earlier version.
- 1Connect the domain
A domain with your business name builds trust.
- 2Write the invitation
A short WhatsApp message: what it is and what to try.
- 3Invite only 10 people
Real customers from your target audience.
- 4Watch and ask
Where did they stop, and what confused them?
- 5Turn feedback into small requests
Back to lesson 7: one change at a time, with a restore point before it.
An imperfect app that is live teaches you more than a perfect app nobody has seen.
Real iOS and Android apps are an extra step from the same Fanann conversation; start with the web first.
After the course: how to keep learning
The real skill is structured thinking: describe, plan, build small, test, adjust. Repeat the course on a second project and it goes much faster.
- Follow the idea to MVP in 7 days sprint
- Validate with customers before adding features
- Check commercial registration and payment requirements in your country
- Practice with Arabic prompts for building apps
- Build an internal tool for your team
- Read the exported code to understand what was built
Key takeaways
- Vibe coding is a learnable skill: clear descriptions, a plan before building, and small sequential changes.
- Every lesson has a hands-on exercise; apply it to a real idea, not a toy example.
- The two lessons beginners skip, and regret: designing the data before the screens, and testing before launch.
- For Gulf users, add RTL, phone-number sign-in and local payments like mada and Apple Pay early.
- The course project ends with a live link you share with your first 10 users.
Frequently asked questions
Is there a free vibe coding course in Arabic?
How long does the 10-lesson course take?
Do I need to know how to code before I start?
Should I prompt in Modern Standard Arabic or dialect?
What should my first course project be?
Ask your AI assistant about this
Copy this prompt into the AI assistant you use, then add the details of your own case.
I am reading this guide: “Vibe coding in Arabic: a practical 10-lesson course from idea to launch” https://fanann.com/en/blog/vibe-coding-course-arabic/ My question: vibe coding course for beginners Use that page as a source and explain the answer step by step for my situation, tell me what to check before I start, and cite the page link.