Skip to content

[Feature] End-to-end dApp builder: from idea to deployed dApp in the browser #28

@Nadai2010

Description

@Nadai2010

Summary

Transform ARBuilder's Playground from a developer-focused API tester into a full end-to-end platform where users can go from an idea to a live dApp without ever touching the terminal.

Think Remix + OpenZeppelin Wizard + Bolt.dev, but for Stylus / Arbitrum.


Motivation

The current Playground is powerful but outputs raw JSON — the developer still needs to:

  • Install Rust
  • Compile locally
  • Deploy via CLI
  • Set up the frontend manually

The technical foundation already exists (contract templates, frontend generation, ABI extraction, wagmi hooks), but it’s not tied together into a guided flow.

This came up during testing and discussion with the team (Wei Meng, Gian). The consensus was that evolving the Playground into something like a “Lovable or Bolt.dev for full-stack dApps” is a natural next step.


Proposed Flow

  1. Choose template or describe with AI
  2. Customize (wizard-style parameters)
  3. Review / edit code (in-browser editor)
  4. Compile (server-side, no local Rust needed)
  5. Connect wallet → Deploy contract
  6. Pick UI template → Auto-generate frontend
  7. Deploy frontend (Vercel / Cloudflare Pages)

Step Breakdown

Step What the user does What ARBuilder does
1. Template / AI prompt Selects ERC20, NFT, Staking, DAO, custom, etc. or describes in natural language Uses generate_stylus_code with the right template
2. Wizard customization Fills in name, symbol, supply, toggles (mintable, burnable, pausable, ownable) Injects parameters into the template
3. Code editor Reviews and optionally edits generated Rust code Monaco / CodeMirror editor with Rust syntax highlighting
4. Compile Clicks "Compile" Runs cargo check --target wasm32-unknown-unknown server-side (Docker/Cloudflare), returns errors inline
5. Deploy Connects MetaMask, clicks "Deploy" Uses cargo stylus deploy or constructs deployment tx
6. Frontend generation Picks UI template Uses generate_frontend / orchestrate_dapp with ABI
7. Frontend deploy Deploys to Vercel / CF Pages Pushes repo or deploys via API

Key Technical Pieces Needed

  • In-browser code editor (Monaco / CodeMirror with Rust support)
  • Server-side compilation API (Docker-based cargo check endpoint)
  • Wallet-connected deployment (MetaMask signing)
  • Frontend template picker (UI previews + generate_frontend)
  • One-click frontend deploy (Vercel / Cloudflare Pages API)

What Already Exists

  • 19 MCP tools for contract + frontend generation + orchestration
  • ABI extraction (abi_extractor.py)
  • Compiler verification (compiler_verifier.py)
  • Frontend templates (wagmi + RainbowKit)
  • Backend templates (NestJS / Express)
  • Full orchestration (orchestrate_dapp)

Future Additions (Post-MVP)

  • Security audits (pattern checks + AI review)
  • Auto-verification on Arbiscan
  • Gas estimation before deploy
  • Contract interaction panel (read/write UI)
  • Subgraph auto-deploy (The Graph)
  • Multi-contract projects (token + staking + governance)

Vision

ARBuilder becomes the Thirdweb / Caldera for Stylus & Arbitrum.

Not just a code generator — a full platform where anyone can launch a dApp in a few clicks.

The hardest parts are already built (templates, RAG, verification). What’s missing is the UX layer that connects everything.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions