Nandita Chakrapani
Nandita writes the pages where the question is "which app is this, really?" — the home page and the page on the 365 name. Her habit is simple and slightly obsessive: before anyone taps Install, she reads the four lines of a store listing that most people skip. The category. The developer name. The first sentence of the description. The date of the last update.
She started doing this for family. An uncle who wanted a cricket score app ended up with a wallpaper app of the same name; a cousin installed a "loan" app that was nothing of the kind. In both cases the listing said exactly what the app was. Nobody had read it.
Independent app check · not the operator · no files, no sign-in
What she looks at
- Names that collide. Short, catchy names get reused across unrelated products. A dating app, a puzzle game and a betting exchange can share a word, and search engines will happily mix them on one page. Her pages separate them without calling any of them bad.
- Numbers in names. When "99", "365" or "247" travel from an address into an app's name, people read them as versions. She explains where the version really lives and why the number in the name never tells you.
- What a listing cannot say. A store page shows who published an app. It cannot show whether that publisher is the brand you meant. She is careful to say where the listing's evidence stops.
Independent app check · not the operator · no files, no sign-in
How she works
Every check she writes, a second author repeats on a different phone before it goes up. If the two phones show different screens, the page describes both. She does not accept files from brands or readers, and she has never been sent one by Instamatch.
Independent app check · not the operator · no files, no sign-in
Outside the desk
Nandita keeps a paper notebook of app names that turned out to mean two things. It is longer than she expected. She is happiest when a reader writes back to say a check caught something before money moved.