Zynga Poker Chip Panel
Budget: $30 – $250 USD
I need a straightforward multi-platform panel that lets me move Zynga Poker chips between users, display current balances, and keep a simple transaction log. The same codebase must run smoothly on the web, on standard mobile browsers, and as a lightweight desktop build (an Electron or PWA wrapper is fine).
Two roles will sign in:
• Administrators – full access to every balance, the ability to process or reverse transfers, and a clear overview of all chip movement.
• Players – view-only access to their own chip balance plus the option to initiate a transfer request.
For this first phase, I’m only after a basic, working prototype:
• Secure login with role-based permissions.
• Clean UI with three core screens: Balance, Transfer, History.
• Backend logic that records each transfer and updates balances in real time.
• Well-commented source code, a short read-me, and simple deployment steps so I can host it myself.
Feel free to choose the stack you deliver fastest—PHP + MySQL, Node.js + MongoDB, or another mainstream option—as long as it’s documented and easy for me to set up. Focus on clarity, security, and a smooth user experience over advanced extras; we can iterate on polish in later stages.
Two roles will sign in:
• Administrators – full access to every balance, the ability to process or reverse transfers, and a clear overview of all chip movement.
• Players – view-only access to their own chip balance plus the option to initiate a transfer request.
For this first phase, I’m only after a basic, working prototype:
• Secure login with role-based permissions.
• Clean UI with three core screens: Balance, Transfer, History.
• Backend logic that records each transfer and updates balances in real time.
• Well-commented source code, a short read-me, and simple deployment steps so I can host it myself.
Feel free to choose the stack you deliver fastest—PHP + MySQL, Node.js + MongoDB, or another mainstream option—as long as it’s documented and easy for me to set up. Focus on clarity, security, and a smooth user experience over advanced extras; we can iterate on polish in later stages.