Devoria
One idea. The files to move forward.
Resources by Mehdi Azizi ·
Five free templates to scope your first iOS app, work with an agent and prepare your checks before publishing. Download the file that fits your current step and adapt it to your project. No email, no sign-up.
Pick the next problem to solve
Idea still fuzzy? Start with the spec. Already have a prototype? Move on to the test grid. If you're getting ready to submit to Apple, use the App Review notes once you've checked the main flow.
Markdown files open in any text editor. CSVs import into Numbers, Excel or Google Sheets with commas as the separator and UTF-8 encoding. Keep a copy of the template, then fill in your results in your own file.
The spec for your first app
Describe the person you're helping, their problem, the main flow and what you're leaving out of the first version. Finish with observable acceptance criteria.
How to use it: Instead of "a reading app," write "add a book, log the page I reached and find that progress again after closing the app."
Download the Markdown template (in French) · Read the user guide
A CLAUDE.md to stay in control
Set the stack, the project's limits, the useful commands and the checks you expect before handing a screen to the agent. The template includes a persistence exercise.
How to use it: Ask the agent to explain which files it will change and to list separately what it tested and what it couldn't verify.
Download the Markdown template (in French) · Read the user guide
The budget to fill in before you build
Separate publishing fees, your development tool and the services your app consumes. Write down your assumptions and the date you checked the prices.
How to use it: A subscription to your coding tool and an AI request made by one of your app's users are two different line items.
The test grid before TestFlight and App Review
Sixteen scenarios, each with a setup, an action to perform, an expected result and a column for your proof. Covers persistence, network, small screens and subscriptions if your app offers them.
How to use it: A button that works once doesn't validate a flow: relaunch the app, deny a permission and repeat the test on the smallest supported screen.
App Review notes that explain your flow
Prepare a precise path for the reviewer: access, main feature, any test purchase, hardware requirements and how to respond to a rejection. An English template to fill in comes with instructions in French.
How to use it: Spell out the path through the screens and the expected result. Demo credentials go in App Store Connect, never in a public document.
Download the Markdown template (in French) · Read the user guide
Keep proof, not just a checked box
For each scenario, note the app version, device, OS and observed result. A test you haven't run stays "To test." A scenario that doesn't exist in your product can be marked "Not applicable" with a reason. When something fails, write down the steps to reproduce it before asking for a fix.
The grid doesn't replace Apple's rules and doesn't guarantee your app gets approved. The App Review Guidelines and the TestFlight documentation remain the references. The TradaZen case study shows why a working prototype isn't always enough.
Not sure where to start?
The iOS Kit walks you from idea to App Store, step by step. The templates on this page stay free, with or without the kit.