Dplatz
Dplatz is a dev blog — its Hitster-clone walkthrough shows vibe-coding a mobile game entirely from a phone.
Last verified:
What is Dplatz?
Dplatz (dplatz.de) is a developer blog whose standout piece documents building a playable Hitster clone entirely from a phone using vibe-coding techniques — prototyping, iterating, and deploying a mobile web app without a laptop. The walkthrough combines voice prompts, an AI coding agent running on a home server, instant preview via Tailscale, and direct deployment to hosting, emphasizing speed and low-friction iteration. Covered features include QR-code driven gameplay tied to Spotify, AI-generated UI and route code, live preview from mobile, and simple rules files for consistent behavior. Aimed at developers and power hobbyists wanting rapid weekend prototypes.
Dplatz pricing
Pricing model: Freemium
The article itself does not sell software or list commercial plans; it describes using a mix of free and third-party services (developer tools, Git hosting, and Spotify) and implies usage of AI coding tools which may have their own pricing. There is no single product pricing or paid plan described on the page; readers are expected to use whichever AI agent, hosting, and third-party services they prefer and follow their separate pricing and free-tier limits.
Dplatz pros
- Complete phone-first development workflow demonstrated
- Shows a full Hitster clone implemented end-to-end
- Uses voice prompts to control the coding agent
- Live instant preview over Tailscale from the phone
- Practical walkthrough of QR-to-Spotify gameplay integration
- Includes deployment steps to Git-based hosting
- Explains using a home AI agent for offline/private runs
- Discusses rules files to keep AI behaviour consistent
- Provides concrete examples of prompts and iterations
- Demonstrates how to create a playable game quickly
- Covers both frontend and backend glue (API routes)
- Shows how to add interactivity like voting/animations
- Details a simple approach to authentication and analytics
- Includes tips for minimizing token/context costs
- Offers guidance for pairing non-coders with developers
Dplatz cons
- Not a step-by-step beginner tutorial—assumes developer familiarity
- Relies on access to an AI coding agent and self-hosting knowledge
- Some steps require external services (Spotify, Git host, Tailscale)
- Security and privacy implications are noted but not exhaustively addressed
- Hardware/network setup (home server, mobile preview) can be tricky
- No packaged starter repo; readers adapt examples themselves
- Presumes comfort with deployment pipelines and CI/CD
- Mobile typing and debugging ergonomics remain awkward
Frequently asked questions about Dplatz
What exactly is built in the tutorial?
The post builds a mobile web Hitster clone: players scan a QR code, the app triggers Spotify to play songs, and players vote on cards — the article supplies the end-to-end approach (UI, routing, API glue, and deployment) to recreate that experience.
Can I follow this entirely from a phone?
Yes — the author demonstrates completing the core workflow from a phone using voice prompts and a browser-based preview over Tailscale, though some steps (like advanced debugging or repository management) are easier with a laptop.
Do I need to run my own AI server?
No, but the article shows both options; running a home AI agent gives privacy and offline control while cloud-hosted AI agents work too — choice depends on privacy, latency, and cost preferences.
Which third-party services are required?
The walkthrough uses Spotify for playback, Git hosting for source control and deployment, and Tailscale for instant preview; alternatives are possible but these services are used in the demo.
Is there a starter repository provided?
The post presents a worked example and prompt recipes but does not bundle a single ready-to-clone starter repository; readers adapt the prompts and snippets to their own project structure.
How are rules files used in the workflow?
Rules files (like a .cursorrules equivalent) document stack choices, conventions, and AI preferences so the agent produces consistent code across iterations and team members.
What level of developer skill do I need?
Intermediate web development familiarity is recommended: comfort with Git, deployment, simple backend routes, and understanding of OAuth/third-party APIs makes following and extending the demo straightforward.
Does the demo include authentication and analytics?
Yes — the article discusses adding authentication (e.g., Google sign-in patterns) and optional analytics (hosting-provider analytics) as part of polishing the prototype for multiplayer or repeated use.
How does the QR-to-Spotify integration work?
The app generates per-game QR codes that encode a session or track list; scanning opens the web app which uses Spotify playback endpoints or deep links to start songs, coordinated by the app’s API routes.
Are privacy and security considered?
The author flags privacy/security concerns and recommends reviewing anything that touches user data, using local/self-hosted AI when appropriate, and treating early projects as throwaway prototypes rather than production systems.