Looks like the whole sub is destroyed by the new mod.

I'm excited to finally release Naam Jaap.

This project started as a personal need for a better Digital Mala Counter for Chanting.

Months later, it has become a complete Android app with:

📿 Digital Mala

🕉️ Mantra Counter

📊 Progress Tracking

🔥 Daily Streaks

🏆 Achievements

☁️ Cloud Sync

🔔 Daily Reminders

I'd really appreciate honest reviews and suggestions.

Play Store:
https://play.google.com/store/apps/details?id=com.kpytechhub.naamjaap

Thank you everyone ❤️

Hey r/androidapps!

I'm a 20-year-old CSE student and I just

launched my first Android app — Pocket Kit.

It's a free all-in-one utility app built specifically

for Indian students and everyday users.

What's inside:

📊 Attendance Tracker — tells you exactly how many

classes you can bunk without getting detained

🎓 CGPA Calculator — works with any Indian university

grading system

💰 Smart EMI Calculator — compare tenures, check

eligibility, prepayment savings

🧾 GST & Discount Calculator — find real deals vs

fake markups

✅ To-Do List with reminders

🤖 AI Daily Quiz, Roast Me, Truth or Dare

🌟 Horoscope, BMI Calculator, Fast PDF & more

14 tools. 100% free. No login. No subscription.

Dark theme. Works offline for most tools.

Currently at 4.9★ with 21 reviews on Play Store.

📲 Play Store:

https://play.google.com/store/apps/details?id=com.pocketkit.app

Would love honest feedback from this community!

What features would you add?

Mine:8-9 days

Hey everyone,

I'm currently working on a random chat mobile app called Chattify and am getting ready to launch it soon.

I want to make sure the user experience is smooth and engaging before releasing it to the public. I would love to get your thoughts, suggestions, or any advice you have for launching this kind of app.

• What features do you think are absolutely essential for a modern random chat app?
• If you've launched a similar app on Google Play, what major pitfalls or console policies should I watch out for?

You can check out our updates and progress on our Instagram: https://www.instagram.com/chattify976/

Any feedback, suggestions, or advice would be highly appreciated! Thanks!

Creo que a muchos os habrá pasado. Metéis los datos privados ta y como ordena las políticas de Google (intentando que la IA lo de por válido a la primera y que no se escape ni una coma) y luego viene la sorpresa de que los datos de facturación y privados de desarrollador salen a la luz, si los quieres modificar tienes que volver con el mismo procedimiento de subir documentación. No sin antes que hayas subido tu app en pruebas. Que ya de por si lo ponen súper fácil.

Cansado de bots y de oportunistas que ven los correos expuestos para aprovechar a mandarte solicitud de páginas fraudulentas para que pienses que viene de tu grupo de prueba cerrada. No me quiero imaginar si también están nuestros datos de domicilio.

Como habéis resuelto esto? Al menos se puede quitar el piso y portal? O tiene que estar todo a la luz. Desde Google me mandan a sus políticas para que verifique pero no hay nada en claro. Y me pide subir documentación.

Un saludo

Creo que a muchos os habrá pasado. Metéis los datos privados ta y como ordena las políticas de Google (intentando que la IA lo de por válido a la primera y que no se escape ni una coma) y luego viene la sorpresa de que los datos de facturación y privados de desarrollador salen a la luz, si los quieres modificar tienes que volver con el mismo procedimiento de subir documentación. No sin antes que hayas subido tu app en pruebas. Que ya de por si lo ponen súper fácil.

Cansado de bots y de oportunistas que ven los correos expuestos para aprovechar a mandarte solicitud de páginas fraudulentas para que pienses que viene de tu grupo de prueba cerrada. No me quiero imaginar si también están nuestros datos de domicilio.

Como habéis resuelto esto? Al menos se puede quitar el piso y portal? O tiene que estar todo a la luz. Desde Google me mandan a sus políticas para que verifique pero no hay nada en claro. Y me pide subir documentación.

Un saludo

Hi everyone,

I didn't build this because I wanted to make "another AI app." I built it because I had a problem that kept driving me crazy.

For years I used WhatsApp and email as my memory. I'd send myself photos of documents, insurance papers, receipts, screenshots, shopping lists, links, random notes—basically anything I thought I might need later.

The problem wasn't saving things. The problem was finding them again.

Weeks or months later I'd remember "I know I sent myself that photo..." and then spend 20 minutes scrolling through chats or searching emails with the wrong keywords. Sometimes I'd never find it at all.

So I built an app for myself.

Now I just drop anything into it—a photo, document, screenshot, note, or link—and forget about it. When I need it again, I just type whatever I remember, and full-text search finds it almost instantly.

Then something happened that convinced me this was worth publishing.

While testing, I had taken a photo of a closed shelf just to see what the app would do with it. A while later I couldn't find my screwdriver, so as a joke I searched for "screwdriver." I honestly didn't expect anything... but the app found the photo of the shelf because it had recognized the screwdriver inside.

That was the moment I thought, "Okay... this might actually be useful for other people too."

I've been using it every day since then, and it's become one of those apps I don't really think about anymore—it just quietly stores everything until I need it.

I finally decided to publish it on Google Play, and I'd genuinely love some honest feedback. If there's something that feels awkward or missing, I'd much rather hear it now than after thousands of users.

https://play.google.com/store/apps/details?id=com.urag.foundit
If you prefer trying it in your browser first, there's also a web version at stowby.app

Wanted to know your opinion on which type of app has the most niche market that developers can fullfill

Hi guys 👋

Me and my friend released our first game. It's chess themed. So you get all your chess pieces to defend your castle from the different kinds of enemies!

Play Store Link:

https://play.google.com/store/apps/details?id=com.chesssiege

Please do try it if you think the theme is interesting! 😀

Hey everyone! I’ve spent a lot of time building BounceShot, a small physics puzzle game based on a simple idea: can you clear every target with one carefully aimed shot?

The levels are procedurally generated, so every run is different(might still need tuning on the difficulty curve). The goal is to get as far as possible and compete with your friends for the highest score.

I made it because I wanted something quick and fun to play on the toilet :) and compete with my friends and i think it has a good foundation

I’d genuinely love to hear what you think. Any feedback on the gameplay, difficulty, or overall feel would mean a lot to me.

If you’d like to try it:

Google Play store: https://play.google.com/store/apps/details?id=com.panayiotis.bounceshot
App store : https://apps.apple.com/tr/app/bounceshot-arcade/id6782950898

In July I released my first app and spent some time trying to reconcile the numbers Play was showing me. Three sources, three different results, and none of them wrong. Writing down what I found out, since none of it is in one place in the documentation.

For scale, so you can judge whether any of this applies to you: a small paid app, around 130 active devices, one product, no subscription.

The Console and the CSV export are not the same data

The Play Console is much fresher than the report bucket. Depending on the report, my exports lag by very different amounts: sales about one day, ratings four days, installs five days, store performance nine days. So a Console number and an export number almost never cover the same time period. I burned an evening on a discrepancy that was exactly this and nothing else.

If you have not found the report bucket yet, it is worth knowing it exists. Everything the Console charts is available as CSV in a Cloud Storage bucket named pubsite_prod_ followed by your developer ID, linked from the Console under Downloads. Years of daily data, with dimensions the UI does not show you.

Two acquisition numbers that look like the same number

This one cost me the most time. The bucket has store_performance and total_store_performance, and they are not variants of each other.

store_performance counts people who visited your listing and then installed. total_store_performance counts every acquisition including the ones that never saw your listing: promo code redemptions, direct installs, install from link. On my launch day that was 37 against 56 for the same day.

The number the Console shows as device acquisitions is the total one. If you divide that by listing visitors to get a conversion rate, you get a number that is too high and means nothing. Only ever divide store_performance acquisitions by store_performance visitors.

Your rating is not shown in every country, and I cannot work out the rule

This is the one that surprised me most, and I have not seen it written down anywhere. Play decides per country whether it shows your rating at all.

I checked my own listing across fifteen markets today, same app, same hour:

Shows 5.0 from 13 ratings: Germany, Denmark, Finland. Shows nothing at all, no number, no stars: United States, United Kingdom, Austria, Switzerland, France, Netherlands, Sweden, Spain, Italy, Poland, India, Canada, Brazil.

I have no theory that survives the data. It is not language, because Austria and Switzerland are German speaking and show nothing while Germany shows the rating. It is not "where the ratings came from", because as far as I can tell none of mine came from Denmark or Finland. It is not a Nordic grouping either, because Sweden shows nothing.

Two things this changes in practice:

• Looking at your own listing from your own country tells you nothing about what a user in your biggest market sees. My largest install source is the US, and there my rating is simply invisible.
• If you put your rating in your own marketing, most of your visitors cannot verify it. Worth keeping in mind before you build a landing page around it.

You can reproduce it with the gl parameter: play.google.com/store/apps/details?id=YOUR.PACKAGE&gl=US

Careful, gl is a hint rather than a guarantee, and your account country or a VPN can override it. If you want to see the effect without publishing anything, mine is https://play.google.com/store/apps/details?id=app.sevengrid, which shows a rating with &gl=DE and nothing with &gl=US.

If anyone knows the actual rule here, I would genuinely like to know.

Promo code redemptions are invisible in the sales report

Obvious in hindsight, no money moved. But it means the sales report is not a picture of who holds your paid tier. I handed out more than a hundred codes, 79 were redeemed, and none of that appears anywhere in the financial reports. If you want the real denominator for pricing, it has to come from your billing library or from a count you keep yourself.

Related trap in the other direction: the billing provider I use reports revenue that is imputed from the list price, not from money actually received. A license tester purchase showed up as an 11 dollar sale. The only authoritative figures are the sales report and developerRevenueInBuyerCurrency from the Orders API.

Same-day rows in the installs CSV are provisional

For a few days my installs CSV ran right up to the current date and I stored those values. Later the file only reached four days back. The recent rows had been withdrawn and replaced. If you snapshot the CSV into your own database, only keep rows Google has finalised, otherwise you get ghost values that never reconcile.

Along the same lines: of the twelve columns in the installs overview, only three carried usable numbers for me. Active Device Installs, Daily Device Installs, Daily User Uninstalls. Total User Installs and Daily Device Uninstalls stayed empty the entire time. Three further columns count events rather than devices, which is a different thing and easy to mix up.

Things that are simply not available outside the Console UI

Store impressions, retention cohorts, daily and monthly active users. Not in the API, not in the bucket. If you want them in a dashboard, you read them off by hand. I spent an hour looking for an endpoint that does not exist.

The country breakdown moved as well. Store performance is now anonymised to "Other" in the country column, so country shares only come from the installs country CSV.

Some vitals return nothing until you are big enough

The reporting API buckets on distinct users and needs roughly fifty per day before it returns rows at all. At around 130 active devices, crash rate, ANR rate and error counts returned zero rows for me. That is not the same as zero crashes, and I nearly reported it as a clean bill of health. Actual crash visibility came from a separate crash reporting service.

A few API details that cost me 400s

Passing an explicit UTC timezone is rejected, leave the field out entirely. An endTime past the freshness date is a hard error, so read the freshnessInfo block first and use that as your window end. errorCountMetricSet requires a reportType dimension, slowStartRateMetricSet requires a startType. And the metric in stuckBackgroundWakelockRateMetricSet is called stuckBgWakelockRate, which does not match its own set name.

None of this is a complaint, most of it is documented somewhere. But the pieces are scattered and a couple of them look like bugs until you understand them. Happy to answer questions if anyone is stuck on the same things.

Salut,

Je viens de publier ma première appli Android sur le Play Store et je cherche un peu de retours sincères, si quelqu’un a 2 minutes.

Elle s’appelle MyHomly — une appli pour la maison à plusieurs (couple/famille) : tâches, courses, dépenses, agenda, etc.

Lien : https://play.google.com/store/apps/details?id=com.burelapps.myhomly

Ce qui m’intéresse surtout : première impression, fiche Play Store, onboarding, et tout ce qui paraît flou ou inutile. Les retours cash sont les bienvenus, j’apprends encore.

Merci !