Remix

Make your own version of Dihari Rewards

Get an exact, working copy in your account, then change anything with chat.

Original by Ali Fraz

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

PROJECT NAME: DIHARI REWARDS — WHITE-LABEL WATCH & EARN APP

Act as a senior full-stack developer, mobile app developer, UI/UX designer and software product architect.

Build a professional, production-oriented Watch & Earn rewards application designed for the Pakistani market. I want to develop this application as a software product and sell licensed copies to multiple clients.

The application must be a real, functional product, not just a static UI prototype.

1. BUSINESS MODEL

Build a reusable white-label rewards platform that I can sell to multiple businesses.

Each client should be able to customize:

- App name and logo
- Brand colors and splash screen
- Support contact and terms
- Reward points and approved reward limits
- Minimum withdrawal threshold
- Available reward campaigns
- Referral program settings

Keep each client's users, transactions, configuration and financial records isolated.

Include a licensing system that lets me manage client subscriptions, license expiry, permitted features and renewals.

Do not use one shared wallet or database for unrelated clients.

2. USER APPLICATION

Create a beautiful, modern, mobile-first interface with:

- Sign up and login
- User profile and account settings
- Home dashboard
- Available rewarded video advertisements
- Daily check-in
- Optional quizzes and eligible referral rewards
- Points and wallet balance
- Complete transaction history
- Withdrawal request screen
- Notifications
- Help and support
- Privacy policy and terms

Use a professional green, white and navy theme with a clean card-based layout.

Support English and Urdu, PKR currency formatting and responsive mobile screens.

3. REWARDED ADVERTISEMENT SYSTEM

Integrate a legitimate rewarded-ad provider that permits the intended app model.

Requirements:

- Display eligible rewarded video ads.
- Verify completed rewards using trusted server-side callbacks or the provider's approved verification mechanism.
- Credit points only after valid verification.
- Prevent duplicate reward claims, replayed callbacks, bots and suspicious activity.
- Enforce daily limits and advertiser/provider rules.
- Display honest earning history and reward rules.
- Use test advertisements during development.

Never fabricate ad views, ad revenue, users or payouts. Never reward users for invalid ad activity.

Keep the ad provider configurable so I can change the integration when supported.

4. WALLET AND TRANSACTIONS

Implement a secure server-side wallet ledger.

Each transaction must include:

- Unique transaction ID
- User and client account ID
- Transaction type
- Amount and currency
- Timestamp
- Status
- Reference to the relevant ad, reward or withdrawal

Use atomic database operations to prevent duplicate credits and negative balances.

Separate pending rewards, approved rewards, available balance and withdrawal amounts.

Make the points-to-PKR conversion rate configurable and clearly visible to users.

Do not treat points as withdrawable cash until the corresponding reward is eligible and funded.

5. JAZZCASH WITHDRAWAL WORKFLOW

Create a withdrawal interface where users can submit:

- Requested amount
- JazzCash mobile number
- Account holder name, where required

Include withdrawal statuses:
Pending, Under Review, Approved, Paid and Rejected.

Build an admin review queue, transaction references, rejection reasons and payout reconciliation.

Use an authorized payout provider or official supported payment integration if available. If automatic integration is unavailable, provide a secure manual-review workflow.

Never display a request as Paid until the payment has actually been confirmed.

Protect mobile numbers and financial information. Never ask for JazzCash PINs or OTPs.

6. ADMIN DASHBOARD

Create a separate, secure administrator dashboard.

Features:

- Overview of registered users
- Client and license management
- Ad integration settings
- Reward campaign management
- Reward rates and limits
- Withdrawal review and reconciliation
- Transaction and audit logs
- Fraud alerts
- User support management
- Application settings
- Revenue and reward-liability reports

Use role-based permissions. Record sensitive administrative actions in an audit log.

Never expose administrator credentials or private API keys in client-side code.

7. OWNER / SUPER-ADMIN PANEL

Create a separate owner panel for me as the software seller.

Allow me to:

- Register new business clients
- Create and revoke licenses
- Set license expiry dates
- Manage plans and feature access
- Customize branding for each client
- Track installation and activation status
- View software subscription payments
- Manage product versions and updates
- Export client configuration
- Provide support and documentation

The owner panel must not allow me to access a client's private user information or withdraw their funds without explicit authorization.

8. REFERRALS AND ANTI-FRAUD

Include optional referral codes and referral rewards.

Implement:

- Duplicate account detection
- Rate limits
- Suspicious activity flags
- Server-side reward validation
- Withdrawal eligibility checks
- Idempotent payment processing
- Abuse review and appeal workflow

Do not collect unnecessary personal data or use invasive device surveillance.

9. TECHNOLOGY STACK

Use an appropriate, maintainable technology stack:

- Flutter or another suitable cross-platform framework for mobile
- A responsive web dashboard
- Firebase or Supabase for authentication and database services, where appropriate
- Server-side functions or a secure backend API
- A transactional ledger with appropriate access controls
- Environment variables and secure secret management
- Automated tests and error logging

Choose a stack that supports deployment, maintenance and future customization.

Do not place privileged database credentials, payment secrets or signing keys in the client application.

10. SOURCE CODE AND SELLING PACKAGE

Deliver:

- Complete, organized source code
- Database schema and migrations
- Backend functions and API documentation
- Environment variable example file without real secrets
- Admin and owner dashboard
- Sample branding configuration
- Test data clearly marked as test data
- Unit and integration tests
- Installation instructions
- Deployment instructions
- Backup and recovery guide
- Client handover manual
- Software license template for legal review
- A demo account using non-production data
- A list of all external services and their costs or approval requirements

Include a demo mode that works without real advertisements or real-money payments.

11. TESTING AND DEPLOYMENT

Test:

- Registration and login
- Tenant isolation
- Reward verification
- Duplicate reward prevention
- Wallet calculations
- Withdrawal status transitions
- Admin permissions
- License activation and expiry
- Error handling
- Backup and recovery

Provide a clear list of incomplete integrations. Never claim the app is production-ready until security testing, required approvals and real integration tests are complete.

12. DEVELOPMENT WORKFLOW

First, create the architecture and database schema.

Second, build the user app and admin dashboards.

Third, implement the backend and wallet ledger.

Fourth, integrate test-mode rewarded ads.

Fifth, implement the withdrawal workflow.

Sixth, build white-label branding and license management.

Seventh, run tests and fix issues.

Finally, provide the complete source code, setup guide and deployment checklist.

If any feature cannot be implemented automatically, explain exactly what manual setup, credentials, provider approval or paid service is required.

Prioritize security, transparency, maintainability and a product that I can legally license and sell to multiple clients.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.