MOBILE GAME DEVELOPMENT

Замовник: AI | Опубліковано: 14.01.2026
Бюджет: 750 $

MOBILE GAME DEVELOPMENT BRIEF Game Name: Smarty-Pants Type: Brain-training puzzle game Platforms: iOS (required), Android (optional but preferred) Launch Goal: Public App Store release (not prototype) ⸻ 1. Vision Smarty-Pants is a fast, addictive brain game that challenges logic, speed, and problem-solving. It should feel: • Easy to start • Increasingly challenging • Competitive • Replayable • Visually smart and playful The game is designed for short sessions (10–60 seconds per level) with a strong “one more try” effect. ⸻ 2. Core Gameplay The game is based on logic puzzles, such as (but not limited to): • Connecting dots / paths • Sorting mechanics (bottles, tiles, colors, etc.) • Constraint-based puzzles Requirements • One main mechanic at launch • Progressive difficulty • New mechanics or constraints unlocked gradually • Levels become harder by logic, not randomness • Unlimited play (not once per day) Each level should be: • Quick to understand • Increasingly complex • Skill-based ⸻ 3. Game Modes A. Solo Mode • Unlimited levels • Clear progression system • Level map or progression indicator • Track: • Best time • Attempts • Level reached ⸻ B. Friend Challenge Mode Users can: • Invite 1–5 friends • Play the same level • Compete to finish first Core requirements: • Winner = first to complete the level • Ranking based on completion time • Results screen showing order of completion Live Progress UI: • A progress bar at the top of the screen • Each player represented by their avatar • Avatars move toward a finish line based on real-time or near-real-time progress • Progress updates while players are actively playing Async or live implementation is acceptable as long as the experience feels competitive. ⸻ 4. Progression & Engagement • Level-based progression • Visual feedback for unlocking new mechanics • Streaks or performance indicators • Optional lives / energy system (not overly restrictive) • Replayability encouraged (beat your best time, beat friends) ⸻ 5. Design & Branding Visual Style • 2D • Clean, modern, playful • Funky but smart • No emoji-based UI • Custom illustrations and UI elements Logo & Mascot • Logo concept: pants wearing glasses • Simple, iconic, suitable for app icon • Character can be reused in UI, loading screens, rewards Typography • Custom or semi-custom funky font • Readable and distinctive • Used consistently across UI ⸻ 6. Technical Requirements • Clean, scalable architecture • Easy to add: • New puzzle mechanics • New game modes • Events or challenges Backend Requirements • User profiles • Friend invites • Match creation • Match results • Completion times • Leaderboards Preferred (open to recommendation): • Unity (2D) or equivalent • Firebase / Supabase or similar backend • Real-time or near-real-time data syncing ⸻ 7. AI Usage (Allowed) The developer may use AI tools to speed up development, including: • Code scaffolding • Level generation • Puzzle variations • Asset drafts Conditions: • All code must be clean, original, and understandable • No copy-paste template apps • Full source code ownership must be delivered • Developer must be able to modify and explain all code ⸻ 8. Deliverables • Fully functional, publish-ready game • iOS build (Android if included) • Source code and assets • Backend setup • App store–ready build • Basic documentation • Post-launch bug-fix support (to be agreed) ⸻ 9. Timeline Open to discussion based on scope and approach. Milestone-based delivery preferred. ⸻ 10. What the Developer Must Provide • Relevant mobile game examples • Proposed tech stack • Development timeline • Total cost or phased pricing • Clear list of inclusions and exclusions ⸻ 11. Long-Term Vision This game is intended to scale with: • More puzzle types • More social features • Competitive modes • Events and challenges Looking for a developer who can think beyond launch, not just deliver code. ⸻ Final Note (Important) This is not a hyper-casual template game. I am looking for: • Strong game feel • Clean UX • Thoughtful progression • Long-term scalability