AppX for schools, universities and hackathons: 500 credits per student
Teach app building with AppX. Partner schools, courses and hackathons get 500 extra credits for every student and teacher, free. How it works and how to apply.
Ilyos Olimov · · 5 min read
I am looking for partners: schools, universities, coding courses, bootcamps, hackathons and startup clubs. If you teach people to make apps, or you run an event where people build one in a weekend, I would like to give your students credits to build on AppX.
The offer: 500 extra credits for every student and every teacher in your group, free. They come on top of the free plan, which already gives everyone 100 credits a month.
What AppX is, in one paragraph
AppX turns a description in plain words into a real mobile app. You write "a habit tracker with streaks and a weekly chart", AppX shows a plan of the screens, and after you approve it, builds the app. You see it running in a live preview, change it by chatting, and download the full code: a standard Expo + React Native project you can open in any code editor. The builder works in English, Russian and Uzbek.
What 500 credits buy
Credits pay for building and editing. These are real first-build costs of apps from our gallery:
| App | Screens | Credits |
|---|---|---|
| Tomato, a pomodoro timer | 1 | 11 |
| SipDay, a water reminder | 2 | 16 |
| Pocket Semester, an expense tracker | 3 | 21 |
| Crumbs, a recipe box | 5 | 29 |
| Reps, a workout log | 5 | 30 |
So 500 credits is about fifteen five-screen apps, or a few apps with many rounds of changes. That is enough for a semester project, a course module or a hackathon weekend. The partner credits do not disappear at the monthly reset. They stay until they are used.
Why this works for teaching
- Students see a working app in their first lesson. Not a diagram, not a tutorial project. Their own idea, running.
- The code is real and it is theirs. Every plan, the free one included, lets you download the whole project. A teacher can open it with the class and walk through the screens, the navigation and the data. Our guide on builders that give you the code explains what is inside.
- It teaches how to describe a product. The quality of the app depends on how clearly you explain what you want. That is a skill students need anyway, whether they become developers, designers or founders.
- The app opens on a phone. In the browser on any phone, and on Android in our own app, AppX Go. The iPhone version is waiting for Apple's review.
Who can apply
- Schools and universities: IT, design, business and entrepreneurship classes, and individual teachers.
- Coding courses and bootcamps: online or in a classroom, paid or free.
- Hackathons, startup clubs and incubators: credits for every participant of an event or a cohort.
There is no minimum group size. Uzbekistan or anywhere else.
How it works
- Write to support@appx.uz. Tell us the name of your school, course or event, who you are, roughly how many students, and the dates.
- Your students sign up on appx.uz with their own email, the normal free sign-up.
- You send us the list of emails they signed up with.
- We add 500 credits to each account, teachers included. We reply to every request within two working days.
We do not ask for a contract, a fee or your logo on our site. If you are happy to, tell us how it went, and with your students' permission we may show some of their apps in the gallery. That is optional.
What the credits do not include
To keep expectations honest:
- A database for the app starts on our Starter plan, $20 a month. Free and partner accounts build apps without a server database.
- Publishing to the App Store and Google Play is not included. It needs a developer account from Apple ($99 a year) or Google ($25 once). We can help with publishing for a separate, written price.
- Credits are personal. They are added to each student's own account and cannot be moved between accounts.
- Big apps use more. An app with ten or more screens can take a large share of 500 credits. Starting small and adding screens step by step goes further.
Why I am doing this
AppX is a small company, and I am its founder. Most people who try AppX for the first time ask for something small and personal: a tracker, a list, an app for their own shop. Students are the same, and a classroom is the best place to learn what to ask for. I would rather give a class real credits than run another ad.
If you teach, organise or mentor people who want to build apps, write to support@appx.uz. Start the subject with "Partner", so we see it first.
Keep going
More practical ways to move your app forward.
- How to describe your app to AI: a prompt template
Write a clear AI app-builder prompt with a copyable template, a practical example, acceptance checks, and focused follow-up edits.
- How to turn a client brief into a mobile app prototype
Turn a client brief into a mobile app prototype with a copyable AppX prompt, a practical test checklist, and a focused client-feedback workflow.
- The 5-backtick fence: stopping prompt injection via Markdown
We ship user input into an LLM architect prompt every turn. A reviewer caught that a 4-backtick string from the user could close our 3-backtick fence and run arbitrary instructions on the model. The fix is one weird Markdown trick.
- Investigators before builders: a 2-phase LLM workflow
Most teams dispatch coding agents straight to the build. We run a read-only investigator phase first — and the findings have rewritten our plan in 30-40% of cases. Here's the shape, the brief format, and what to do when findings contradict the plan.
- Step 0: delete dead code before you refactor with an LLM
Every byte you load into an LLM agent's context is a byte it has to keep track of. Dead code looks like signal — and agents preserve, extend, or mimic it. Our rule: a pure-deletion commit before any structural refactor of a file over 300 LOC.
Ready to try your idea?
Start with a clear description. AppX will help you turn it into an app you can test.