codeyy documentation: Your complete guide to all platform features

Start from the welcome page, then move to the Quick Start section. This is the fastest path to find answers to any technical question insidecodeyy documentationin less than two minutes. You don't need a programming background; the documentation is written in language a business founder understands before a developer does. I'll explain here how to access each section, when to use it, and what mistakes most beginners make. Think of this article as your personal map before you press your first build button.
How do I access codeyy documentation and navigate between its sections?
Open the linkcodeyy.ai/docsthen select the section from the left sidebar menu. Sections are arranged according to your actual journey: Quick Start, then Product Guides, then Account and Billing. Each page has a search box at the top for direct access.
The menu isn't random. It's organized to follow the way a Gulf entrepreneur builds an app: get to know the platform, create, preview, launch, then track your credit.
Always start from the pageWelcome to codeyy. It gives you an overview of the entire structure before you get lost in details. After that, check outWhat is codeyy?if you're still comparing the platform to others.
Pro tip from experience: use the search box with one word instead of a full sentence. The word "publish" gives you more accurate results than "how do I publish my app to the store". This saves real time, especially when you're in the middle of building and need a quick answer.
The documentation interface works in Arabic and English. If you prefer Arabic, make sure to set the language at the top of the page once, and it will stay saved on your future visits.
Where should I start if I'm completely new?
Start by creating your first app directly, don't read everything first. Open the guideCreate your first appand follow the five steps, and you'll have a working interface in minutes. Learning by doing is much faster than learning by reading alone.
Many entrepreneurs spend two hours reading before they try anything. Don't do that. Write your app idea in a simple sentence, like "a dental appointment booking app for a clinic in Riyadh", and let the platform build the initial structure.
What nobody tells you: your first attempt is rarely perfect. And that's completely normal. The idea is to see the result quickly and then adjust it with the description. The platform is designed for rapid iteration, not perfection on the first try.
After building your first app, go back to the documentation to understand what you did. You'll find that the terminology has become familiar because you saw it work in front of you. This order — trying first, then reading — is most effective for non-technical people.
Bookmark the Quick Start page. You'll return to it often in your first week, and it's designed to be your daily reference, not a one-time visit.
What do you find in the Product Guides section?
The Product Guides section is the practical heart of codeyy documentation. It explains every feature you actually touch while building: dashboard, tools, preview, security, and deployment. Each page is short and focused on one task, with illustrative screenshots and numbered steps.
Start withDashboard basics. This is your main screen, and from it you manage all your projects. Understanding it well saves you confusion later.
Then move toWorkspace tools. Here you learn how to organize your files and access quick settings. The side tools save you minutes in every work session.
Each stage has its own page. Want an initial build? CheckFirst build and preview. Want to fix a problem that appeared in the app? OpenPreview and diagnostics, which is the page that reveals to you the reason for any error in clear language.
The section is organized so you don't need to read it in order. Jump straight to the page related to what you're doing now. This design is intentional and suits those working under time pressure.
How do I preview my app and fix errors?
Click the Preview button at the top of your workspace to see your app running live, and if an error appears, open the Diagnostics page to read the problem in plain language along with a suggested fix. The preview updates itself instantly with every change you describe.
The preview isn't just a static image. You can click inside it and navigate between screens like you're a real user. Try the registration journey, add an element, and make sure everything responds before thinking about publishing.
A common mistake among beginners: ignoring diagnostic messages and thinking they're complicated. The truth is the opposite. The Diagnostics page in codeyy writes you the problem in Arabic and suggests a fix step. Read it, and usually you'll solve it with one description to the platform.
If you see a blank screen or a button that doesn't work, don't rebuild everything. Identify the broken element and ask to fix it specifically. This is faster and preserves your credit.
Check the guidePreview and diagnosticsbefore publishing any major update. Think of it as a final quality check, just like a restaurant owner reviews a dish before serving it to a customer.
How do I protect my app's data and my users' data?
Enable two-factor authentication on your account first, then review data permissions settings inside each project. codeyy documentation dedicates two sections to security: one to protect your account and another to protect your app's data and your users' data. Both are necessary before any real launch.
Start from the pageYour app security. It explains how to secure login and control who accesses your project. A simple step but it protects you from many problems.
For Gulf markets specifically, data protection regulations have become stricter. In Saudi Arabia, for example, there are clear requirements for storing and processing user data. CheckData and securityto understand how the platform handles data storage.
A tip many get wrong: don't collect data you don't need. Every extra field in a signup form is a legal responsibility on you. Ask for phone number and name only if that's enough.
Review access permissions regularly. Anyone who leaves your team should have their permissions revoked immediately. This simple habit protects you from embarrassing leaks, especially as your project grows and more people work on it.
How do I publish my app to web and mobile?
To publish to web, follow the guidePublish a web appand choose a custom link or your own domain. For mobile, prepare your app according toPrepare a mobile appbefore uploading it to Apple and Google stores. Each path has its separate requirements.
Web publishing is easier and faster. With one click your app becomes available at a link you share immediately with your customers. Perfect for first testing and gathering feedback.
Mobile publishing requires more patience. Apple's store in particular reviews apps manually, and that can take days. Prepare a clear icon, a precise description, and screenshots, because the store rejects these elements if they're missing.
What we learn from experience: don't wait for launch day to read the store requirements. Check them early. An Apple developer account costs around $99 annually, and a Google Play account costs a one-time fee, and both are unavoidable requirements for publishing to mobile.
If you're testing a business idea quickly, start with web only. Get your first hundred users, make sure the idea works, then invest your time in mobile stores. This order saves you weeks of waiting.
How do I track my credit and billing?
Open the Activity and Credit section to see your current usage and operation history. Every build and preview consumes credit, and the documentation explains how these operations are calculated and how to recharge. Tracking your credit weekly prevents it from running out in the middle of an important project.
Check the pageCredit and billingTo understand the credits system. The idea is simple: heavier operations consume more, and regular previews barely register.
For whoever manages credits within the team, theActivity, Credits, and Billingpage gives you a detailed record of every operation. This is very helpful when you want to know exactly where your credits went.
Mistake that costs money: rebuilding the entire project instead of partial edits. Every time you request building the project from scratch, you consume much more than if you requested a specific partial change. Describe the change precisely to save your credits.
Set a personal alert when your credits drop below a certain limit. Nothing is worse than work stopping before a client's delivery deadline. Pre-charging is easier on your nerves than emergency charging at the last minute.
Can I migrate my project from another platform?
Yes, the documentation provides a dedicated guide for migrating your projects from other building platforms. Check theMigrating from Another Platformpage to learn what can be imported and what needs rebuilding. Migration isn't a literal copy, but an intelligent reconstruction of your app's structure.
If you're using another platform and feel it's slow or expensive, migration is a practical option. But be realistic: some highly customized elements may need to be re-described from scratch.
Start by exporting your data from the old platform first. Keep a copy of user lists and important content. This is a safety step nobody mentions but it saves you if something goes wrong.
Is migration worth the effort? In my view, yes, if you'll be developing the app continuously. But if it's a static project that works without changes, staying might be cheaper sometimes. Decide based on your growth plan, not enthusiasm.
Take migration in stages. Migrate the most important screen first, make sure it works, then continue with the rest. Doing it all at once will confuse you and make it harder to spot any issues.
Frequently Asked Questions
Is codeyy documentation fully available in Arabic?
Yes, codeyy documentation is available in both Arabic and English, and you can switch languages from the top of the page. The Arabic content is written in simplified language suited for non-technical entrepreneurs, with examples close to the Gulf market. Your preferred language is automatically saved on your next visits, so you don't need to adjust it every time.
How much time do I need to build my first app using the documentation?
You can get a working app interface within minutes by following the first app creation guide. The longer time comes later in editing and polishing. In practice, most entrepreneurs reach a demo-ready prototype for clients within a single workday, then develop it gradually based on feedback.
What's the difference between publishing a web app and publishing a mobile app?
Web publishing is instant—one click gives you a shareable link directly. Mobile publishing requires preparing icons, descriptions, and review from Apple and Google stores, and may take days. It's recommended to start with web to test the idea quickly, then move to mobile after confirming the project's success and readiness for official release.
How do I avoid consuming credits quickly during development?
Avoid rebuilding the entire project, and rely on describing partial changes precisely. Review the Credits and Billing section to understand which operations consume the most. Set an alert when your credits drop, and pre-charge before important deadlines. Regular preview consumption is very minimal, so don't hesitate to test your app repeatedly before publishing.
Practical summary to start now
Save the documentation page as a daily reference, not a one-time read. Start with the welcome page, create your first app quickly, preview, secure your data, then publish. This simple order covers 90% of what you need.
Don't wait until you understand everything. Try, fail, adjust. The platform is designed for you to learn from it while working. And each time you return to the documentation after hands-on experience, you'll find it clearer and faster to understand. Start today with a small project, and you'll be amazed how natural everything becomes within just one week.