Tepnot Live- Go LIVE & Connect

The setup reality the second you open it

The app loads to a login screen that asks for a phone number. No email option. No social login. Just a country code dropdown and a number field. After entering the number, a one‑time password arrives via SMS. The verification process takes about twenty seconds. Once inside, the home feed appears with a mix of posts, Shots (short videos), and suggested creators. The interface is clean but busy. A bottom navigation bar holds five tabs: Home, Shots, Explore, Live, and Profile. The Live tab is the most prominent, with a pulsing red icon. Tapping it opens a page showing current live streams, but you cannot start your own stream until you have at least 1,000 followers. That requirement is not mentioned during onboarding. New users see a message saying "You need more followers to go live" with no clear path to gain them. The app pushes you toward watching others first. The profile setup is minimal. You can add a photo, a bio, and link your social accounts. The settings menu is where you find the privacy controls—end‑to‑end encryption for chats, who can see your posts, and data deletion options. The app does not prompt you to explore these settings. Most users will miss them entirely.

The messaging section works like any other chat app. You can send text, images, videos, and voice notes. Group chats support up to 500 members. Calls are HD and encrypted, but they require a stable internet connection. The app does not fall back to lower quality when the network drops. Calls simply disconnect. The Shots feature is a direct clone of Instagram Reels. You record or upload a video, add music from a library, and post it. The music library is limited. Many users complain about the lack of regional Indian songs, which makes the feature less useful for local content creators. The Explore page shows trending creators and viral content. It is algorithm‑driven, but the recommendations feel repetitive. The same faces appear multiple times. The app does not explain how the algorithm works or how to get featured.

How the gift goal and spin wheel interact in a real stream

The Play Store description mentions gifts and a spin wheel, but it does not explain how they work together. During a live stream, the host can set a gift goal—a target number of diamonds (the in‑app currency) that viewers must send. Viewers buy diamonds with real money. Each diamond costs about one rupee. When a viewer sends a gift, it adds to the host's goal. If the goal is reached, the host receives a bonus or a special badge. The spin wheel is a separate mechanic. The host creates a wheel with custom activities—like "dance," "sing," or "tell a joke." Viewers spend coins to spin the wheel. Coins are earned by watching ads or by completing tasks in the app. They are not the same as diamonds. A viewer can send a gift (using diamonds) to help the host reach a goal, but they cannot use diamonds to spin the wheel. They must earn coins separately. This creates a two‑step engagement loop. A viewer who wants to participate in both mechanics must spend real money on diamonds and also watch ads for coins. The app does not explain this distinction anywhere in the onboarding flow. New users often assume diamonds and coins are the same thing. They send gifts expecting to also spin the wheel, only to find they have no coins. The support pages confirm this confusion, with multiple troubleshooting guides for "gift not working" and "spin wheel not available." The host, meanwhile, sees the gift goal progress but has no control over who spins the wheel. The wheel is entirely viewer‑driven. This separation is intentional—it drives both ad revenue and in‑app purchases—but it is not transparent.

The Battle Live mode adds another layer. Two creators compete in a 1v1 or 2v2 format. Viewers send gifts to their preferred creator. The creator with the most gifts at the end wins. The spin wheel is not available in Battle mode. Only gifts count. This means the engagement mechanics change depending on the stream type. A creator hosting a Single Live can use both gifts and the wheel. A creator in Battle Live can only use gifts. The app does not warn creators about this difference when they switch modes. Several creators have reported losing engagement because they planned a wheel‑based activity, only to find the wheel disabled. The official guidelines state that Battle Live is "for competitive engagement," but they do not explain the feature restrictions. This gap between the advertised features and the actual implementation is a recurring theme across the app.

Ads, bugs, and the real cost of going live

The app is free to install, but the ad experience is aggressive. Banner ads appear at the bottom of the home feed and the Shots page. Interstitial ads play after every third video in the Shots feed. During live streams, a banner ad remains visible at the bottom, covering part of the chat. Viewers can close it, but it reappears after a few minutes. The premium tier removes ads and unlocks additional features, but the pricing is not listed clearly. The in‑app purchase page shows various diamond packs, but no subscription option. The ad‑free experience is tied to a one‑time purchase, but the price varies by region. Indian users see a lower price than users in other countries. This is not documented anywhere in the app or on the Play Store. Users have reported being charged different amounts for the same pack. The support team responds with a generic message about "regional pricing," but they do not provide a breakdown.

Bugs are common. The Shots feature occasionally fails to upload videos. The progress bar stalls at 99% and never completes. Restarting the app sometimes fixes it, but not always. The editing tools—speed control, filters, and trimming—are basic and prone to crashing. Several users report that applying a filter causes the app to freeze. The only workaround is to force‑close and try again. The messaging section has its own issues. Messages sometimes fail to send, showing a red exclamation mark. The app prompts you to check your internet connection, but the connection is fine. Clearing the cache resolves the issue temporarily. The support pages acknowledge these bugs but provide no permanent fix. The changelog mentions "bug fixes and performance improvements" in every update, but the same issues persist across versions. This suggests the fixes are superficial or the bugs are deeper than the developers are willing to address. The rooted device warning is another red flag. The app explicitly states that using it on a rooted phone may lead to "unexpected behavior" and "compromised data security." This is a standard disclaimer, but it also implies the app does not actively protect against rooted devices—it simply refuses to take responsibility.

The permission that actually limits your experience

The app requests standard permissions: camera, microphone, storage, and contacts. These are expected for a social app. The permission that causes the most friction is the "draw over other apps" permission. Tepnot uses this to display a floating button that lets you start a live stream from any screen. The app prompts for this permission during the first live stream attempt. If you deny it, you cannot start a stream at all. The app does not offer an alternative. You must grant the permission or you cannot go live. This is not mentioned in the Play Store description. New users are caught off guard when they try to stream for the first time. The app explains that the permission is "needed for floating controls," but it does not clarify that the stream cannot start without it. This is a hard dependency, not a convenience feature. The permission also raises privacy concerns. A "draw over other apps" permission can theoretically be abused to overlay content on other apps. Tepnot's privacy policy states that it does not use the permission for anything other than the floating button, but the policy is vague about data collection. The app collects location, personal info, and nine other data categories. It shares some data with third parties. The encryption protects messages in transit, but the app still stores metadata. The data deletion request is available, but the process is not automated. You must email support and wait for a response. The average response time is not published.