How did he build the platform?
Abdul Osama (عبدول أسامة) built his learning platform with AI assistance, but distinguishes a project that looks ready from a version people can use. He began with a visual identity and an initial landing page, then worked on the platform’s functions and revisions. The result is a beta that still has issues.
“I built my entire learning platform with AI.” — Abdul Osama
From design to beta
AI refers here to the tools he used to help design and build the project. Claude Design is the name he uses for the design tool: he gave it his simple logo and asked it for a visual brand. After adjusting details such as the fonts, he requested a landing page—a page that introduces the project to visitors. He found the initial page’s content unsuitable, then took the work into Claude Code, a coding assistant that helps build software from text instructions.
He had considered an existing Arabic learning platform that, he said, handles payments, organization, page creation and video hosting for a fee of approximately 8%. He chose to build his own because he wanted more control over the landing page, visual identity and user experience.
| Option | Benefit or reason he described | |---|---| | Existing learning platform | Handles payments, organization, a page and videos. | | Building with AI assistance | Gives him room to shape the design and experience, but requires revisions and fixes. |
What does the current version include?
He calls it a beta: a version available for use that still has problems to fix. It has a landing page, currency displayed according to the user’s location, sign-in through Telegram or Google, a dashboard, and a course page with progress tracking and lessons divided into sections. These are the essential features he wanted for an MVP, or minimum viable product: an initial usable version.
“I’ve marked it as beta because it still has problems and errors.” — Abdul Osama
In numbers
- About 8%: the fee he cited for the existing-platform option.
- Two sessions: enough for something that looked nearly ready, not a finished product.
- Six to seven more sessions: his account of the work needed to reach a usable beta.
- About 25 hours: his estimate for revisions and fixes beyond the quick initial build.
- About 30 hours: his estimate for building the version he showed.
- At least 10 years: the experience he mentioned when putting that effort in context.
What should you do next?
Define the visual identity and essential features first, but do not treat an attractive first page as a finished product. Test sign-in, course progress and the rest of the user journey, and allow time for revisions before relying on the beta.
Claude Code
