POCKET WORKSHOP / FEATURE MANUAL
Build real Android apps on your Android phone. Describe your idea, let the AI write and build it, then install it and try it. This guide covers the phone app and the online store, with directions for finding each feature. PocketBuilder is an early preview: use the latest version, and expect some features to depend on your account, server settings and Android version.
The project files, coding tools and APK builder run on your phone. AI requests go through the PocketBuilder server, so AI work needs an internet connection, an approved account and credits. You need an ARM64 phone running Android 8 or later.
Download PocketBuilder from this website and follow the Installation guide. Open the app to register or sign in.
Request an email code, verify it, then choose your user name and password. During the preview, new accounts wait for administrator approval and credits before starting AI work. You can explore the interface while waiting. A download invitation may be required; website sign-up can be disabled.
On first launch, follow the registration screens. Existing users can choose Sign in. Use Request access on the website if you need an invitation.
PocketBuilder needs permission to install the apps it builds. Automated UI testing also needs its accessibility service. Permission banners take you to the relevant Android settings. If accessibility looks enabled but is not connected, switch it off and on again. Automated screenshots require Android 11 or later.
Tap the permission banner in PocketBuilder and follow the Android settings screen. Read the Installation guide before changing any security settings.
When a newer published version is available, PocketBuilder can offer to download and install it with your permission. It does not replace a newer development build with an older published version.
Open PocketBuilder while online and follow any update prompt. Find your installed version and build date in Settings / Control panel.
PocketBuilder is currently in beta and is not yet available on Google Play. Because it can build and install other Android apps, publishing it through Google Play requires additional compliance and distribution work.
For now, PocketBuilder is distributed directly as an APK for sideloading. I realize this also creates a trust factor, since users need to install an app from outside Google Play, so building that trust is an important part of the beta.
You can find more information how to participate in the early testing of PocketBuilder here - https://pocketbuilder.app/#get-pocketbuilder
Keep separate projects for different ideas. Rename them, change their description, clone a project to try a different direction, or delete one you no longer need. Cloning starts with the source, not the old build output or agent conversation.
Open Projects → Create. Use a project’s menu for Edit details, Clone project or Delete.
Ask for a new app, an improvement, an explanation or help with a problem. The agent works with the project files and can build an installable Android APK. Apps can use native Android code or web content inside an Android app; describe what matters to you.
Open a project → Agent. Type your request and press Execute. Continue in the same conversation to ask for changes.
Attach screenshots to explain a bug or reference images to show the look you want. The images you submit become part of your request to the online AI service.
In Agent, tap + beside the prompt, choose images, then send your request.
Choose how much AI capability you want to use. The server decides which model each level uses and whether it is available. Approximate relative costs help you compare them; they are not a fixed price for a whole project. A higher level may cost more without being faster.
Open Settings → AI Intelligence and choose an available intelligence level.
Concise mode asks the agent to keep routine explanations short. You can change the communication preference for each project without changing its model or tools.
Select your project, then Settings → Project agent communication. The change applies to the next run, including Resume.
Send an adjustment while the agent is busy. Steering takes effect at the next safe point; it does not erase completed changes. Stopping asks for confirmation. You can resume interrupted work with a follow-up request.
While the agent is running, type your adjustment and tap Steer. Use Stop to end a run, or the available Resume action / a new prompt to continue.
A compact activity line and timer show what the agent is doing. You can open development diagnostics for more detail. A notification can show progress on the lock screen if Android allows it. The animated robot is optional and uses no AI credits.
Watch the activity in Agent. Expand View Developer Diagnostics for logs. Settings contains Agent notification settings and the Robot companion switch.
Copy your submitted prompt or the agent’s final explanation to use elsewhere, without copying the stream of activity messages.
Tap the small copy icon on your prompt or the completed agent answer.
The agent has tools for generating artwork and searching the web when a task needs them. These depend on the services enabled on the server and their allowances. Generated assets and AI output still need your review.
Ask in Agent, for example: “Create an icon for my app” or “Research this before changing the project.”
PocketBuilder compiles and packages the app on your device. You can install or update it, open it, and request a home-screen shortcut. Android may ask you to confirm installation. An APK is not a guarantee that an app is ready for Google Play submission.
After a successful build, use Install APK or Open app in the agent result or Build tab. Use Pin to home to request a shortcut.
Automated testing can open the built app, interact with controls and inspect results. The PB TEST banner marks active testing. Do not touch the screen during those interactions. Testing has limits and cannot prove that every feature works.
In Projects, create or edit the project and choose Automated testing. Enable the requested permissions, then ask the agent to build and test.
Human feedback mode still lets the agent build the app and offer installation. You try it yourself and describe what to improve. This is especially useful for fast games, controls and anything that depends on how the app feels.
Projects → project menu → Edit details → Human feedback. After installation, try the app and send your observations or screenshots in Agent.
Automated testing can use Basic independently of your coding model, or use your selected intelligence level. When the testing budget is reached, you can choose more automatic testing or return to PocketBuilder and test yourself. More AI testing can use more credits.
Choose the testing intelligence preference in Settings. When a testing-limit dialog appears, choose whether to continue or finish testing.
The Build tab keeps the build result and technical output available separately from the conversation. Scroll through it when a build fails or you want more detail.
Open your project → Build. Use the result actions or scroll through the build output.
See the source code and resources behind your app, preview images and edit text files directly. Internal agent bookkeeping is hidden by default so it does not clutter the file list.
Open Workspace → Files and select a file. Save any text edits before leaving. Advanced developer settings can enable Show internal files when troubleshooting.
Restore points keep earlier project states so you can go back after an unwanted change. When restoring, unsaved current changes are preserved in a safety point; an identical saved state is not copied again. Later conversations stay readable, but the agent starts fresh with the restored files. Rebuild before installing; restoring does not roll back published apps or online data.
Open Workspace → Restore points, select a point and choose Restore from here.
A completed agent run with a successful build saves a restore point automatically. You can also save current progress yourself before experimenting. The latest five automatic build points are kept; manual saves and recovery points remain until you delete them.
Wait for active work to finish, then open Workspace → Restore points → Save current progress.
Edit a restore point’s title and description, inspect storage use, or delete points you no longer need. Shared file content reduces repeated storage. Deleting one point does not remove files still needed by another.
Workspace → Restore points. Use the selected point’s edit or delete action. Review the confirmation before deleting.
Your working projects live on your phone. Signing in is not an automatic cloud backup. Publishing an APK does not publish its source unless you choose that option. Private support snapshots are a separate, explicit action.
Choose sharing options carefully in Build → Publish. Keep your own backups before deleting projects or clearing PocketBuilder’s app data.
The agent can look up approved libraries on the server and download versions suited to your project. These can provide features such as 3D graphics or object detection when those packages are published. Availability is controlled by the catalog; arbitrary Android libraries are not guaranteed to work.
Describe the feature in Agent. The agent selects a suitable available library or asks when the choice matters. Ask it to explain any missing capability.
If an important capability is missing from the library catalog, the agent can ask your permission to send a concise request to the administrator. This is a suggestion for review, not a promise that the library will be added.
Explain what you need in Agent. Approve the library-request question only if you want the request sent.
Apps can use server-backed rooms, lobbies, shared data, persistent app data and server-side rules. This lets people on different phones participate without one phone having to run all the game rules. The app still needs appropriate connection and recovery behavior.
Ask Agent for an online or multiplayer app and describe who joins, what is shared and what should happen when someone disconnects.
Generated apps can request AI through PocketBuilder’s server library. Each user approves access and spending from their own PocketBuilder account, with limits. They need PocketBuilder installed for this approval flow. The server keeps provider API keys out of the generated app.
Ask Agent to add PocketBuilder AI. When using the built app, follow the Allow AI spending screen. Manage approvals in Settings → PocketBuilder Account → Connected AI apps.
Generated apps can use the server-backed search library after the user approves access. Search is subject to provider and server allowances; the app should explain when the allowance is unavailable rather than pretend it found results.
Ask Agent to add PocketBuilder web search. Manage approvals in Settings → PocketBuilder Account → Connected search apps.
Prepared library information helps the agent include third-party licence notices where required, usually in a discreet About / Licences entry. Sharing source or artwork still requires the appropriate rights.
Ask Agent where the app’s licence information is shown, and review it before distributing the app.
Browse public apps made by other people and search titles or descriptions. New additions get a temporary spotlight; recent download activity and ratings help determine normal ranking, rather than old lifetime downloads alone.
In PocketBuilder, open Store → Discover. On this website, open Explore apps.
App pages show the description, developer, release information, screenshots when supplied, and download details. Basic Markdown makes website descriptions easier to read. Community uploads are not a promise that an app is safe or suitable for you.
Open an app from Explore apps on the website, or inspect its listing and reviews in Store on the phone.
Download the APK from the website or install through PocketBuilder’s store. Android controls the installation confirmation. Check that you trust the publisher before installing.
Choose an app → Download APK on the website, or its install action in Store → Discover.
Give one to five stars and optionally leave a comment. Signed-in users can choose to post under their user name or anonymously. Comments are checked before publication and may be rejected or unavailable when the daily allowance is exhausted.
Open the app’s review area on the website or tap Reviews in the phone’s store. Choose stars, optionally write a comment, and submit.
If the creator shares editable source, download a separate copy and continue developing it. The original listing stays unchanged. Services and account connections may need setup for your account; the agent can help. Source availability and third-party licences vary.
In the phone store, choose the source action on an app that offers it, then open the imported project and use Set up my copy. On the website, use Download editable source to obtain the archive.
Share a successfully built app in the PocketBuilder store. You may also share the current source and resources so others can make their own copies. Restore history, private chat and known credentials are excluded, but inspect files yourself because automatic checks cannot find every secret.
Open your project → Build → Publish to PocketBuilder Apps. Set the listing details and optionally select Also share editable source before confirming.
Update the name and description, attach up to six screenshots, and put them in the order you want. The first screenshot is the main preview. Changes appear on the public website as well.
Store → My published apps → Edit listing. You can also manage listings through My Account on this website.
Use an unlisted listing when only people with the link should find it. Publish a new build to update your app. Deleting a listing removes the server listing and its files, not copies already downloaded by other people or your project on the phone.
Use Edit listing for the Unlisted option. Publish the rebuilt project from Build for updates. Use Delete in My published apps only when you want to remove the listing.
Your published-app cards show APK downloads and, when source is shared, source downloads. These counts measure downloads, not unique people or active users.
Open Store → My published apps, or view the app’s public page and your website account.
The top balance shows remaining credits without the temporary reservation jumping in and out. AI use deducts credits according to the actual model and usage. Settings shows more detail, including reserved credits. Credit purchases are available when enabled for your approved account.
Tap the credit balance at the top of PocketBuilder, or Settings → Credits → Buy credits. The website account also offers credit purchases.
Your website account brings together your balance, usage history and purchase transactions, with available receipt links. Actual AI costs vary with the model, input, output and caching; a prompt is not a fixed-price unit.
Settings → PocketBuilder Account → Manage account online opens the website sign-in handoff. Or select My Account on this website.
Manage your public user name and account details. If you forget your password, request a reset email and choose a new password through the website. Password fields have a visibility toggle so you can check what you typed.
Use Settings → PocketBuilder Account for your user name or sign-in. Use My Account on the website for profile, email and password changes, or Forgot password on a sign-in screen.
Send a message to the PocketBuilder administrator and continue the conversation when they reply. You can explicitly attach a private project snapshot to help investigate a problem. Review what you share; it is not a public store upload.
Open Settings → Feedback & Support and start or open a conversation. After sending a message, use Attach project / Manage snapshots if support needs the project.
The website includes illustrated installation help, Android-on-phone development guides and comparisons of development approaches. Discord and contact links provide other ways to ask questions or share experiences.
Use Installation guide, All Guides, Discord or Contact Us in the website footer.
Advanced settings provide server selection and connection diagnostics, internal-file visibility and diagnostic checks. These are for development and troubleshooting; most users can leave them hidden. Switching servers signs you out, but keeps projects on the phone.
Use the developer settings in Control panel if already enabled, or ask support for help. Per-run logs are available through View Developer Diagnostics in Agent.
Need more detail? Read the guides or contact us.
We use optional analytics cookies to understand how PocketBuilder is used and improve the site.
You can accept or reject analytics cookies. Your choice does not affect access to PocketBuilder.
You can change your choice later in Cookie settings.
We use Google Analytics on public pages only, after you accept. Google receives technical data such as your IP address and browser information. No advertising features are enabled. We remember your choice for 180 days; analytics cookies are configured with a 180-day lifetime. Closing this notice does not change your choice or grant consent.
AI can make mistakes. Messages go to our AI provider; don’t share secrets. IP and usage kept for 30 days for cost/abuse monitoring. No account access. Chat clears when you leave.