Devoria
Mehdi Azizi, iOS app maker.
iOS developer, founder of Devoria
I build my own apps and write down my method for anyone who wants to build theirs. On Devoria, I share the steps that move a project forward, the mistakes I ran into and the fixes I had to make.
From e-commerce to my first apps
In January 2026, I was doing e-commerce and hadn't published a single app. I started building with the help of AI, then learned to review the code, prepare builds and respond to Apple's rejections. Today Devoria brings together that studio and the kits I built from it.
My setup relies on React Native and Expo for the app, Supabase for the services that need it, and RevenueCat for subscriptions. Claude Code and Cursor help me build, but testing on a device, reading the guidelines and making product decisions are still essential.
Apps you can check out
The studio separates published apps from projects in progress. The Apple listings below let you check the released versions, their publisher and their public history.
- Solys: the alarm that puts your social apps to sleep. View on the App Store.
- TradaZen: trading practice on the real market. View on the App Store.
- Nolera: the wardrobe that builds your outfits. View on the App Store.
- Vigie: the App Store under the microscope. View on the App Store.
My App Store developer profile lists all my releases. I also document the TradaZen journey: first prototype, rejections, release and changes of direction. This case shows one experience, not a timeline or income promised for your project.
What I teach
The iOS Kit helps you scope a first version, build the core flow, plan monetization and put together your submission to Apple. You work on your own app, at your own pace: the kit and its skills guide you step by step. It's not a developer degree, not an income promise and not a guaranteed Apple approval.
You can check what the iOS course covers, what's in the iOS Kit and the price of each kit before deciding anything.
How to read Devoria's guides
- Lessons learned describe the work on my apps. They are not market research or a guarantee of results.
- Rules and commands point to the documentation from Apple, Expo or the tool in question. More recent official documentation takes precedence over a guide.
- Exercises and sample budgets are there to test a method. A calculation assumption is not observed income.
- Dates separate publication from content revision. A technical redeploy doesn't make advice more recent.
AI tools are part of my development work and how I prepare resources. I remain responsible for the content published under my name. Spotted a mistake or an outdated example? Email me with the URL and the passage.
Get started for real
- The Claude Code tutorial for a first iPhone app.
- Scope your idea and define a testable outcome.
- Free templates for scoping, budget and validation.
If you want to start from the code and the process I use on my own apps, it's all in the iOS Kit.