How We Built Balaji Astro Guide: The Engineering Team Explains

Balaji Astro Guide is a live astrology consultation platform that Appic Softwares built for Balaji Telefilms. People top up a wallet, then chat, call or video call verified astrologers who charge by the minute. It went live on the App Store on 7 November 2025, has more than 15 lakh registered users and more than 1 million downloads on Google Play, and our team still maintains it and ships new features.
I'm Shubham Pareek, CEO of Appic. A year after launch, I asked the people who built and run it the questions founders ask us when they want to build an astrology consultation app of their own. Here are their answers, edited for length.
Key facts
- Client: Balaji Telefilms (balajiastroguide.com, App Store, Google Play)
- Products: user app, astrologer app, website and admin panel on one backend
- Stack: Flutter, Node.js, MongoDB, Redis, ZegoCloud, Razorpay, Google Cloud (Mumbai)
- Scale: 15 lakh+ registered users, 1M+ Google Play downloads, 75 lakh+ chat messages
- Reliability: uptime above 99.99% since launch, 99.8% crash-free sessions, 99.4% call connection success
- Biggest lesson: the server, not the phone, must run the per-minute billing clock
The team:
- Devendra, Flutter developer: user app and astrologer app
- Mohammad Imran Khan, backend developer: API, billing, payments
- Himanshu, DevOps: cloud, deployment, scaling
- Harshita, QA lead: testing across both apps and real devices
- Ajeet, frontend developer: website and admin panel
What did we build for Balaji?
Imran (backend): Four products on one backend. The user app and the website are where people recharge, find an astrologer and consult. The astrologer app is where astrologers accept requests, run sessions and track earnings. The admin panel is where Balaji's operations team manages astrologers, pricing, refunds, payouts and reports.
Devendra (Flutter): For users, that means free tools such as Kundli and divisional charts (built on an astrology API), matchmaking, Panchang, horoscopes, tarot and numerology, and then the paid part: chat, voice and video consultations, booked instantly or scheduled, paid from a prepaid wallet.
Imran: The platform now has more than 15 lakh registered users and has carried more than 75 lakh chat messages.
Every feature that touches money or a live session involves two people on two phones at the same time. That shaped every decision below.
Why Flutter for the mobile apps?
Devendra: We had two apps, each on Android and iOS, and a small team. Flutter gave us one codebase per app for both platforms. The user app and the astrologer app also share the same data for charts, messages and consultations, so when a user starts a session, the astrologer sees the user's birth chart on screen straight away without typing anything in.
The detail that mattered most was keeping the screen calm during a call. A timer, typing indicators and wallet updates all change constantly. We made sure each of those redraws only its own small piece of the screen, so the video and chat never stutter.
How does per-minute billing work without overcharging or undercharging?
This is the question every founder asks, and our answer changed during the project.
Imran: In the first version, the phone told the server when each minute had passed. That fails both ways. If the app went into the background or lost signal, minutes went unbilled, and when the signal came back, delayed updates could arrive in a burst.
Harshita (QA): I reproduced it deliberately: a user with four minutes of balance could keep chatting for nearly six if the phone was put aside for a while. Phones slow down background apps to save battery, and the in-app timer slowed down with them.
Imran: So we took billing away from the phone completely. The server keeps the clock and charges each minute itself, in a way that can never charge the same minute twice. When the session ends, every started minute is billed.
Devendra: The apps just display what the server tells them. When the balance gets low, the user sees a warning with a quick top-up button. At zero, the server ends the session.
Harshita: We retested under battery saver, changed device clocks and forced network drops. Every deduction landed on the minute, and every session ended the moment the wallet ran out.
If you're building an app like AstroTalk, don't let the phone decide what to charge. The server holds the money, so the server has to hold the clock.
How do chat messages reach the right person on a busy platform?
Imran: Once the platform runs on several servers, a user and an astrologer can end up connected to different machines. We added a shared messaging layer between the servers, so a message reaches the right person whichever server they're on, with no added delay.
Devendra: We also kept two kinds of traffic apart. Chat, availability, session control and wallet updates travel on one real-time channel. Audio and video travel on a dedicated calling service, ZegoCloud. A bad video connection never interferes with billing or chat.
Harshita: On two phones side by side, an astrologer going online shows up in the user app in under 1.5 seconds. The moment an astrologer takes a call, everyone else sees them as busy, so two users can't book the same astrologer at once.
What happens when the network drops during a paid call?
Devendra: We don't end the call on the first drop. The app shows "Reconnecting" and gives the connection time to recover in the background, and both sides pick up where they left off, including any chat messages sent in the gap. If a regular phone call comes in, the consultation pauses and resumes afterwards. On Android, live calls keep running when the app is minimised.
Harshita: I tested it by switching airplane mode on mid-call and by walking from office Wi-Fi onto weak mobile data. Audio and video came back within a few seconds and the wallet stayed correct.
What was the hardest bug?
Devendra: A frozen black screen after some calls. The rating screen never appeared, and users had to close the app.
Two parts of the system were each trying to end the call at the same moment, and the second one tripped over the first. We put one coordinator in charge of ending a call, so any later signal simply joins the clean-up that's already running.
Harshita: Before the fix, I could trigger the freeze most of the time by ending a call from both phones at once. Afterwards, 50 deliberately messy hang-ups all returned to the home screen and showed the rating screen.
How do astrologers avoid missing incoming calls?
Harshita: On locked iPhones, consultation requests were arriving silently, with no ring and no vibration. On some Android brands, battery savers closed the astrologer app in the background, so calls never arrived at all.
Devendra: On iOS, incoming consultations now ring like a normal phone call, even when the phone is locked. On Android, they open a full-screen incoming-call screen. After the fix, astrologers on iPhone answered more than 96% of consultation requests, up from under 65%.
Harshita: For the Android brands with aggressive battery savers, we added an in-app checklist that walks each astrologer through the right settings for their own phone.
Imran: On the server, unanswered requests expire after a short wait, and an astrologer stuck on "busy" is reset automatically.
How do wallet payments get credited exactly once?
Imran: Payment confirmations can arrive more than once and in any order. Every payment is verified with Razorpay and credited only once. A background job regularly finds any payment that went through but didn't credit, and fixes it automatically.
Devendra: Android added its own twist. When people paid through a UPI app like PhonePe or Google Pay, the phone sometimes closed our app in the background to save memory. The payment went through, but the wallet still showed the old balance when they came back. Now the app checks with the server every time it returns to the screen.
Harshita: I forced that worst case on every test run. The wallet updated within two seconds of returning to the app each time.
What does the infrastructure look like?
Himanshu (DevOps): Production runs on Google Cloud in Mumbai, with a load balancer in front of a group of servers that grows automatically with traffic. Every code change goes through an automated pipeline that deploys it and checks it responds before it counts as live.
For automatic scaling to be safe, no single server can hold anything important on its own. Sessions, real-time events and billing are shared across all servers, and scheduled jobs such as reports run once, not once per server.
Before launch we load-tested the platform with 50,000 concurrent simulated users. It stayed stable throughout, and uptime since launch has been above 99.99%.
How do you protect a platform like this from abuse?
Imran: OTP logins cost money every time someone requests one, and bots try to guess codes or flood the system. We set limits on how often any number, device or network can request or verify an OTP and call the API, shared across every server. Accounts that keep hitting the limits are slowed down and, if it continues, blocked for a while. That stops spam without getting in the way of normal users.
What did the website and admin panel need?
Ajeet (frontend): The website, balajiastroguide.com, is where people browse astrologers, read horoscopes and explore pooja services, then move to the app for paid consultations. Getting that handoff right took work: early on, people coming back from the app store could get stuck in a redirect loop. Now they land back where they started.
Astrologers, poojas and horoscopes change every day, so the site updates its sitemaps automatically and every astrologer profile carries structured data for search engines.
The admin panel is how Balaji runs the business: approving astrologers, setting commissions, payouts, refunds, coupons, banners, horoscope content and a support desk. It has more than 70 screens, and each staff role sees only what it should: support can't open payout reports, finance can't read support chats. New support tickets and completed pooja bookings appear as live alerts, and moderators keep a list of blocked words that filters abusive language in consultation chats.
How do you test an app that needs two phones at once?
Harshita: Emulators would have missed most of these bugs. We test on real iPhones and Android phones, from budget 3 GB Samsung models to Xiaomi, Vivo, Oppo and Pixel. The cheap phones find memory problems; some brands find battery-saver problems.
Every consultation flow is tested on two phones side by side, so we can watch both wallets, both timers and both screens. A short smoke test runs on every build, and more than 450 test cases run before every release.
One example: switching quickly between Kundli chart tabs crashed a budget Samsung within two minutes, with memory climbing past 700 MB.
Devendra: The app was recalculating every chart each time you opened a tab. Now it calculates once and reuses the result.
Harshita: After the fix, 300 tab switches in a row held memory at about 180 MB, with no crash.
Releases go out gradually, to a small share of users first, while we watch crash reports. In production, the apps run at a 99.8% crash-free session rate and 99.4% of calls connect successfully.
Did the app stores push back?
Devendra: Apple's review team first asked whether wallet recharges should go through Apple's in-app purchase. Consultations are live, one-to-one services from real people, which Apple's App Review Guidelines allow to use other payment methods under the person-to-person services rule. We explained that with a demo and it was accepted.
Android 14 also brought new rules for apps that use the microphone and camera in the background. We updated the apps ahead of time, so no release was held up.
What would you do differently?
Devendra: Make more of the app editable from the server. Some promotional screens were built into the app, so every marketing change needed a store release.
Imran: I'd keep the same core choice: one well-organised backend rather than many small services. Sessions, wallet and earnings are closely linked, and one system is far easier for a small team to keep correct.
Harshita: Bring QA into architecture discussions even earlier. The billing and hang-up problems were both catchable on paper.
AstroGuide by the numbers
| MeasureFigure | |
| iOS launch | 7 November 2025 |
| Registered users | 15 lakh+ |
| Google Play downloads | 1M+ |
| Chat messages handled | 75 lakh+ |
| Uptime since launch | Above 99.99% |
| Load test | 50,000 concurrent simulated users |
| Crash-free sessions | 99.8% |
| Call connection success | 99.4% |
| iPhone consultation requests answered | Over 96%, up from under 65% |
| Test cases before each release | 450+ |
Figures are from Appic's production monitoring and QA records for Balaji Astro Guide; the download count is from the Google Play listing.
FAQ
How long does it take to build an astrology app like AstroTalk?
AstroGuide's user app, astrologer app and admin panel went from plan to first store submission in about three months, with work continuing after launch. Timelines depend on scope: an app with Kundli, live chat, calls, a wallet and astrologer payouts takes far longer than a horoscope-only app. See our astrology app development page for typical ranges.
What tech stack does an astrology consultation app need?
AstroGuide uses Flutter for the user and astrologer apps, a Node.js backend with MongoDB and Redis, a real-time channel for chat and session updates, ZegoCloud for audio and video, Razorpay for payments, Firebase for notifications, CleverTap, Mixpanel and AppsFlyer for analytics, and Google Cloud with automatic scaling.
How does per-minute billing work in an astrology app?
The server runs the billing clock, not the phone. It charges each minute itself and can't charge the same minute twice, so billing stays correct even when the app is in the background or the network drops. The app only shows the balance the server sends and ends the session when the server says the balance is gone.
Do astrology apps have to use Apple in-app purchase for consultations?
Not for live consultations. Apple's App Review Guidelines let apps that sell real-time, person-to-person services use other payment methods. AstroGuide's wallet pays for live consultations with real astrologers, and Apple accepted that after review. Digital content sold inside an app is a different case.
How many users can an astrology app handle?
That depends on the architecture more than the framework. AstroGuide spreads traffic across servers that scale automatically with demand, shares sessions and messages between them, and passed load tests with 50,000 concurrent simulated users. It now serves more than 15 lakh registered users.
How do astrologers receive consultation requests when the phone is locked?
On iOS, AstroGuide rings incoming consultations like a normal phone call, even on a locked screen. On Android, they open a full-screen incoming-call screen, and an in-app checklist helps astrologers set battery-saver options on their phone brand. iPhone answer rates rose from under 65% to more than 96% after the change.
How do you stop two users booking the same astrologer at once?
Availability travels on a real-time channel shared across all servers. The moment an astrologer accepts a call, every user sees them as busy, and status changes reach the user app in under 1.5 seconds. Unanswered requests expire after a short wait, and an astrologer stuck on "busy" is reset automatically.
How do you make sure wallet top-ups are credited exactly once?
Every payment is verified with the payment gateway (Razorpay for AstroGuide) and credited only once, even if confirmations arrive twice or out of order. A background job finds any payment that succeeded but didn't credit and fixes it, and the app re-checks the balance with the server each time the user returns from a UPI app.
How should you test an astrology consultation app?
On real devices, with two phones side by side for every consultation flow, so both wallets, timers and screens can be watched together. AstroGuide is tested on budget and flagship Android phones and iPhones, runs a smoke test on every build and more than 450 test cases before each release, and rolls releases out gradually.
Shubham: Across all these answers, the hard parts of an astrology app are money and live sessions, not the horoscope screens. If you're planning one, see the AstroGuide case study for screens and the system overview, or talk to us about your astrology app.
Sources
- Apple, App Review Guidelines, 3.1.3(d) Person-to-Person Services
- Android Developers, Foreground service types are required (Android 14)
- Google Play, Balaji Astro Guide listing (publisher Balaji Telefilms Limited)
- App Store, Balaji Astro Guide listing
- Appic Softwares, AstroGuide case study
Related Articles

Astrologer Marketplace App Development: Revenue Model and Tech Stack

App Like Astrotalk: Features, Architecture and Business Model (2026)






