DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run MobileCode from source to change it with Mobilecode

Clone the repo, install with Bun, and run the backend, web UI, or desktop app.

Who it is forA developer who wants to modify MobileCode itself or test changes to its mobile preview features before using a release build.

The problemUsing a release binary does not let you test changes to the device preview code or the fork's mobile detection.

The outcomeA local backend and web UI run from source, and you can run the typecheck and tests before sending a change.

What you need first

  • macOS with Xcode for iOS previews
  • Node 20 or newer (serve-sim needs it)
  • Android SDK platform-tools with at least one AVD for Android previews
  • A JDK that your project's Gradle version supports
  • Bun, for the install from source path

Steps

  1. Run git clone https://github.com/hsandhu/mobilecode.git and then cd mobilecode.
  2. Run bun install in the repo root.
  3. Run bun run --cwd packages/opencode src/index.ts serve --port 4096 to start the backend.
  4. Run bun --cwd packages/app dev -- --port 4444 and open http://localhost:4444 for the web UI.
  5. Run bun typecheck inside the package directory you changed, then bun test in packages/opencode before sending changes.

Prompt for your agent

Clone https://github.com/hsandhu/mobilecode into a local folder, run bun install, then start the backend with `bun run --cwd packages/opencode src/index.ts serve --port 4096`. Expected output: the backend running on port 4096. Verify by confirming the server responds locally before reporting that the source build works.

Caveat. The README gives development commands only and does not describe a contribution process, so check the repo before opening a pull request.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page