Remix

Make your own version of InstaZone Social

Edit the prompt below and generate a customized version in seconds.

Original by Bablu Balla

Describe your app

==================================================
28. COMPLETE CODE GENERATION REQUIREMENT
==================================================

Generate the actual working source code for the complete InstaZone application, not merely a description, wireframe, mockup, or prototype.

The generated project must contain all required frontend, backend, database, authentication, storage, API, routing, security and payment code needed for the requested functionality.

Generate complete code for every required file.

Do not leave important functions as:
- TODO
- Coming Soon
- Placeholder
- Dummy function
- Fake API
- Mock database
- Example-only code

Every important button and feature must be connected to real application logic.

If the generated project is large, generate the complete project in multiple files while keeping all files connected and compatible.

Target a large complete implementation of up to 10,000+ lines of source code where required. Do not artificially add useless code just to increase the line count.

Create a proper project structure such as:

/frontend
/backend
/components
/pages
/services
/database
/api
/assets
/styles
/utils
/config

Use clean, maintainable and production-oriented code.

==================================================
29. VERIFICATION SUBSCRIPTION
==================================================

Create an InstaZone Verified system.

Do NOT claim that the verification is officially provided by Meta.

Use:
“InstaZone Verified”
or
“InstaZone Verified Badge”

Only the owner/admin account has permanent verification initially.

Normal users have NO verified badge by default.

Create configurable verification plans:

1 Month
3 Months
6 Months
12 Months

The admin must be able to configure the price of every plan.

When a user chooses a plan:

1. Create a payment order on the server.
2. Send the user to the legitimate payment gateway.
3. Verify the payment on the server.
4. Only after successful verification activate the badge.
5. Save payment information required for subscription management.
6. Save subscription start date.
7. Save subscription expiry date.
8. Display the verified badge next to the user's username.
9. Automatically remove the badge when the subscription expires.

Never activate the badge only because the browser says payment was successful.

Never store raw card/UPI credentials.

Use secure payment-gateway webhooks/server-side verification.

==================================================
30. PERMANENT OWNER VERIFICATION
==================================================

Create an owner/admin account identified by a secure owner ID.

The owner account receives:

- Permanent InstaZone Verified badge
- Admin access
- Owner controls

The owner's verification must never expire automatically.

Do not expose owner/admin controls to normal users.

==================================================
31. FOLLOWER-BASED PERMANENT VERIFICATION
==================================================

Create an optional automatic permanent-verification rule controlled by the admin.

Default threshold:

5,000,000 followers.

If enabled by the admin and a user legitimately reaches 5,000,000 followers:

- Mark the user as permanently verified.
- Give them the InstaZone Verified badge.
- Store permanentVerified = true.
- Do not assign permanent verification based on fake/manually edited follower counts.
- Permanent verification must not expire.

The admin must be able to enable/disable this rule.

==================================================
32. VERIFICATION PAGE
==================================================

Create a working verification page.

Show:

Current verification status
Verified badge status
Current plan
Purchase date
Start date
Expiry date
Days remaining
Payment status
Permanent verification status
Available plans
Plan prices
Purchase button

If not verified:

“Get InstaZone Verified”

If subscription is active:

“InstaZone Verified — Active”

If expired:

“Verification expired”

Automatically update the UI based on the real database subscription status.

==================================================
33. SUBSCRIPTION EXPIRATION
==================================================

Implement automatic expiration.

When:

current date >= subscription expiry date

then:

verified = false

unless:

permanentVerified = true

or:

owner/admin account

The expired user's profile must automatically stop showing the verified badge.

Do not delete the user's account, posts, followers, messages or profile.

Only the subscription verification status should expire.

==================================================
34. USER DATA ISOLATION
==================================================

This is extremely important.

Each account must have a unique authenticated user ID.

Never use hardcoded profile data for normal users.

When a new user registers:

Create a completely new profile.

Default:

posts = 0
followers = 0
following = 0
verified = false
permanentVerified = false
savedPosts = []
stories = []
conversations = []

Do not copy the owner's profile into the new user's account.

Do not copy the owner's followers.

Do not copy the owner's verified badge.

Do not copy the owner's posts.

==================================================
35. REAL-TIME DATABASE
==================================================

Use a real database/backend for:

users
profiles
posts
comments
likes
followers
following
stories
reels
conversations
messages
notifications
savedPosts
subscriptions
payments
verification
reports
blockedUsers
settings

All relationships must use authenticated user IDs.

==================================================
36. ERROR HANDLING
==================================================

Add proper error handling.

If:
- Login fails
- Signup fails
- Upload fails
- Payment fails
- Database fails
- Network fails
- Message fails
- Post fails

Show a clear user-friendly error.

Never silently fail.

==================================================
37. FINAL TEST
==================================================

Before completing the generated project, test all major flows:

1. New user signup
2. Login
3. Logout
4. Profile creation
5. Profile editing
6. Create post
7. Like
8. Comment
9. Follow
10. Unfollow
11. Story
12. Reel
13. Search
14. Chat
15. Notifications
16. Settings
17. Saved posts
18. Verification purchase
19. Payment verification
20. Subscription activation
21. Subscription expiration
22. Permanent owner verification
23. New-user data isolation
24. Owner profile
25. Admin access control

Fix all compilation/runtime errors before returning the project.

IMPORTANT:
Return the complete source code/project structure required to run the application.

Do not return only explanations.

Do not create fake functionality.

Do not create fake payment success.

Do not create fake follower counts for normal users.

Do not create fake chats.

Do not create fake posts for new users.

Build the actual InstaZone application.

Free to use. No credit card required.