Skip to main content

Attack of the Clones (Part 1): Drishti and vMeet


Background: India recently banned certain Chinese Apps from being used and also with that launched a campaign of being vocal for local. Essentially promoting industries and app developers alike to encourage building and using homegrown solutions. And along with that came a plethora of apps replicating different features of popular Chinese + non-chinese but popular apps trying to capitalize on the national sentiment of vocal for local.

In this series, I will try to look into a few of recently launched apps which I will call "clones" functionality wise. And also look at some of their claims where, in my opinion, they peek into the grey area too much. This is purely for archival purposes so that I can catalog my own findings and direct others here from social media debates.

Part 1

Drishti

In short, this is a Zoom rival with a very similar UI and feature set (exactly like JioMeet which we will cover in a future post). The developer claims 
"Dristi is a video-conferencing application. Which completely made in India. I have used encrypted technology . So , Your data is total secure. Not only that , I have added an extra layer of security. None can save and snapshot and record screen.
No third party login activity can access your meeting until you reveal your meeting code.
You can lock your meeting room by password also."
To assert what the application actually does and if the claims in news and play store are correct we are going to take a peek inside the app. We will go with the 1.0.5 version of the app which is the latest version available at the time of writing this blog and Play Store tells me it's last updated on 18th July 2020.

Backend:

The app utilizes public jitsi servers as it's backend. It uses a public jitsi server to establish your calls.

The application:

If we delve a little deep into the app. We start finding a reference to another app called "meet" in the source code. Including icons of the app in resources folder.
The code references are available in the following files among a lot others

Upon searching for it, we can see that an app with the exact name exists in Codecanyon which anyone can buy

This app has exactly same UI design as Drishti apart from the color scheme and logo. However you will see they also provide rebranding service for a $100 fee, if you want.

Going back to Drishti we can see it still has old icons and assets inside the apk 

With this we can safely assume that Drishti is actually vMeet. And the developer probably just bought the license to use the app and reskinned it to release in playstore.

Privacy Concerns

Once we have established that Drishti is actually just vMeet. Lets see what vMeet offers a developer, to glean what kind of data Drishti exposes as well.
If you goto the codecanyon listing of vMeet, you will realize they also allow a developer to have a web Dashboard to monitor users of the app. A demo dashboard gives us a glimpse of what Drishti's Developer has access to.

So essentially a Drishti's Developer probably has access to:
  • Names of User
  • Their meeting history along with the duration
  • Meeting Statistics
  • Ability to deactivate or activate any user profile
  • Send mass notification
And might have potential access to their emails as well. I could not confirm this just from the demo dashboard.

Recommendation:

It is sufficiently clear that Drishti is just a reskinned vMeet. According to the license agreement of vMeet, it is not illegal to buy it, reskin it and publish it. So it's not breaking any law. Claiming it to be made by someone else, completely secure and made in India are the claims we found we cannot agree with. And vMeet itself seemed like a client of Jitsi meet with the purpose of being a clone to Zoom.

Our recommendation is if you need a separate solution other than zoom, you might want to consider Jitsi Meet which has a separate app in Play Store. Which also is  open source and is the underlying server technology Drishti uses anyway.

endnote: You might have noticed JioMeet uses exactly same  UI as vMeet and Zoom. However, the codebase behind Jiomeet and vMeet is not same. It does have some interesting other caveats too which we will discuss in another blog post.

Comments

Post a Comment

Popular posts from this blog

Racecraft (Project Koru) · Prologue — The Origin Story

Racecraft · Prologue , The Origin Story It Started With a Wine List and a Question About Racing How a happy-hour conversation in the Bay Area turned into a trustable AI race coach , and then into a second version that runs entirely on a phone, on the NPU. This is the prologue to a five-part series. Two years ago(1st November, 2024) I was in the Bay Area for a GDE Summit. If you've never been: it's a couple of days of talks among Google Developer Experts, the kind of people who get unreasonably excited about a new on-device runtime, and then , mercifully , a happy hour where everyone stops performing and just eats. We ended up at a restaurant(Puesto Santa Clara), a long table of GDEs, and I was doing the most important engineering of the evening: trying to decide which wine to order. Across the table was Ajeet Mirwani . I don't even remember how the wine talk turned into racing talk , these things drift , but the moment the word "racing" ...
Post a Comment
Read more

The Throughput Trap: Benchmarking vLLM on OpenXLA and the Reality of Production LLM Serving

vLLM Systems · DevLab 2026, Deep Dive I was recently invited by the Google TPU team to speak at the OpenXLA Summer DevLab 2026 . This post breaks down our deep-dive evaluation of the matured vLLM + OpenXLA stack, the fundamental engineering mismatches between CUDA and XLA serving paths, and why traditional capacity metrics are lying to you. If you are operating large language models at enterprise scale right now, your platform architecture team is likely staring at a massive infrastructure crossroads: Should we migrate our core serving workloads from GPUs to TPUs? Historically, NVIDIA's CUDA ecosystem was the only serious option for user-facing, low-latency LLM generation. But here in 2026, the economics and infrastructure options have transformed. Google TPUs are highly available, cheaper per chip, and the open-source serving stack built around vLLM and OpenXLA has officially achieved absolute production readiness. Yet, when our infrast...
Post a Comment
Read more

A Split‑Brain Neuro‑Symbolic Training Method for High‑Velocity Autonomous Coaching from Telemetry

 Author: Rabimba Karanjai Scope: Problem statement + data methodology + model training (no deployment discussion) Abstract Real‑time coaching in motorsport is a safety‑critical learning problem : a system must map noisy, high‑frequency telemetry to short, actionable guidance that remains physically consistent and avoids hazardous recommendations . This paper proposes a “Split‑Brain” training formulation that separates (i) a semantic coaching target (what action/critique should be expressed) from (ii) a reflexive interface (how actions are represented as compact, verifiable tokens). The approach trains a Small Language Model (SLM) in the Gemma family [1] using QLoRA fine‑tuning [2] , and introduces a telemetry tokenizer plus teacher‑student synthesis pipeline to generate instruction‑action pairs at scale. Core contribution: a reproducible method to convert “ golden lap ” differential tel...
Post a Comment
Read more