Create
Astrologers can upload videos, books, articles, news, courses, and bundles with titles, descriptions, thumbnails, language-aware search, and paid/free settings.
What made it different
The product was discovered while building it.
AstroVista began as a marketplace concept for astrologers and developed into a creator operations platform. The build clarified that the product needed to support digital content, pricing, access, payments, audience engagement, and creator-side administration.
That changed the center of the app. The important workflows became content creation, course packaging, price-duration options, free vs paid content, Razorpay checkout, purchased access, dashboards, comments, revenue visibility, and the ability for astrologers to run campaigns around their own content.
Client context
The product was evaluated as a business system.
The client evaluated the product as a business platform, which shifted the discussion from basic content listing to pricing behavior, paid access, payout history, creator workflows, content search, and operational scale.
The important question became: how should the platform work when many astrologers each manage large libraries of videos, books, courses, articles, and campaigns? That pressure made the product more practical and more workflow-led.
How it developed
From idea to operating platform
Feb 2024
Requirements begin
The project moved from concept discussion into documented requirements and product scoping for the astrologer platform.
Apr 2024
Live app and payment readiness
The app was shared through Google Play, and Razorpay live transaction credentials were obtained. The next phase focused on workflow testing before treating the product as ready for broader usage.
Apr-Jun 2024
Screen-by-screen product review
Core workflows were tested directly: upload content, create courses, manage videos and books, display thumbnails, reduce loading, search content, sort lists, and validate buyer flow.
May-Aug 2024
Pricing became the core problem
The product moved from fixed-price checkout toward campaign-style pricing: multiple price-duration options, free/paid toggles, active and inactive options, and one-time payment with timed streaming access.
Nov 2024
Commercial structure
Maintenance, development, revenue sharing, and partnership models were discussed after the technical build matured, showing the app was becoming a business platform rather than a one-off app.
Jan 2025
Terms documented
Discussion terms were documented formally. The product entered the stage where operations, support, payout handling, and future expansion mattered as much as screens.
The product matured around creator control: content, pricing, access, payments, and visibility into the digital business.
Manage
Content can be searched, sorted, edited, listed, delisted, priced, and organized through creator-side workflows designed around repeated daily use.
Run
Pricing became campaign-like: up to three active price-duration options, one-time Razorpay payments, timed streaming access, and dashboard/reconciliation history.
Key design decisions
Built from feedback
- Thumbnail-first video display to avoid loading heavy content on navigation.
- Latest-first ordering everywhere so active astrologers see recent content first.
- Separate creator thinking around create content, manage content, and run campaigns.
- One-time payment model, not recurring subscription, because access duration is controlled by app logic.
- Tamil and multilingual search for audiences beyond English-speaking users.
What shipped
Platform scope
- Flutter Android app on Google Play.
- Firebase and Firestore backed content workflows.
- Razorpay checkout for paid content.
- Content types: videos, books, courses, articles, news, and bundles.
- Dashboards for likes, comments, transaction history, and creator visibility.
- Mode switching between astrologer and user experience.
Outcome
Why this case matters
AstroVista shows how Codeforge approaches product discovery when the business model is still forming. The engagement moved from app screens into creator workflows, pricing complexity, payment integration, mobile UX iteration, and the operating details behind a digital content business.