r/android_devs

▲ 150 r/android_devs+62 crossposts

I developed Weather World because I wanted a simpler, more helpful way to stay ahead of the forecast. I truly believe that a weather app should be a tool that makes your life easier, not a source of distraction with ads and confusing menus.

How it helps you: The core of the app is all about visual clarity. I’ve focused on creating intuitive graphs that let you see temperature shifts and precipitation trends at a single glance. Instead of reading through long lists of numbers, you can visualize exactly how your day will unfold. It’s minimalist, lightweight, and built for speed—perfect for anyone who values a clean Android experience.

I’d love your support! Please give it a try and see if it helps your daily routine. If you find it useful, please recommend it to your friends! As a solo developer, your support and word-of-mouth are what help me improve and grow.

In compliance with the community rules, I’ve shared the link via IndieAppCircle. Check it out there and let me know what you think!

Find it here: https://play.google.com/store/apps/details?id=com.danie.pocasisveta

u/Tough_Deer_3756 — 18 hours ago

Android interviews help

Hello fellow engineers,
Is there a community/channel on Reddit or discord for android engineers helping each other out for interview preparation!?

Peer to peer android interviews.
I am unable to get a valuable (human like) feedback with these AI mock interview platforms.

Would appreciate if someone can point out to a group helping each other. Or if there are enough people who are looking for something similar, we can help each other out.

reddit.com
u/bitterchocolate26 — 5 days ago

Help Needed! Beta Testers for My New Android App (Will Reciprocate!)

Hi everyone!

My new app is almost ready for its public launch on Google Play!

To proceed, Google requires 12 beta testers to opt-in and install the app from the Play Store. This is a crucial step for the final release.

Here's how you can help:

  1. Click an opt-in link I'll provide.
  2. Install the app from Google Play.
  3. Keep it installed for at least 14 days and use it a few times.
  4. Share any feedback or issues you might find with me.

Your support is incredibly important to get the app out to everyone!

If you're willing to be one of the first 12 testers, please reply or message me directly. I'll send you the link and instructions.

Also, if you have an app that needs testing, I'd be happy to reciprocate and test yours!

Thank you so much!

reddit.com
u/Tall_Yam7894 — 6 days ago

ViewModel.init{...} considered harmful

Recently I had a problem in my app where after changing some options on the Settings screen and then returning to the Home screen I realized it seems that said option has not changed.

Let's assume we have an option for haptic feedback in the app (clicks, scrolls, etc) that can be changed in the Settings.

So of course the problem was that I'm using \`init\` block and Hilt to initialize my VMs.

I'm aware that using \`init\` was frowned upon but I would say what the hell, I don't see any performance or even huge architectural issues with it.

Reading some articles I'm still not convinced why it's a big no no since to me some pros don't justify cons especially when proposed solutions are a bit silly, expiring subscribers after 5 seconds? (\`SharingStarted\` shenanigans) What a sick joke! Why 5? Why not 10 or even a 6 million?

BTW recreating ViewModels after any navigation seems dumb to me, a part of idea behind ViewModels is preserving data across changes.

I consider changes like activity being paused, resumed; a concern of UI rather than ViewModel, a VM should provide ways to refresh data based on UI concerns but not actively monitoring and referencing them so implementing a built-in mechanism for VM to actively refresh data independently is wrong, all I'm saying that they're UI events.

If race conditions are a concern I don't see whether loading data on \`init\` or using cold flows change anything, if any operation is blocking in nature it doesn't matter how you run it as long as you separate UI with your logic, race conditions exists or not should not be any of concern for Composables as long as you have a well defined UI.

Fundamentally I'm against making things complex, I see a simple problem, if the best solution exists is a complex one, I rather stick with that problem because I don't want to create more problems by implementing a half-ass complex solution to minisculely improve the state of affairs.

But enough of me ranting, I accept its harmfulness for now. I was reading those articles but I couldn't wrap my head around how to implement them sanely without overcomplicating everything. I'll provide links.

A simple VM in my app that I intend to change.

https://github.com/yamin8000/freeDictionaryApp/blob/master/feature\\\_about/src/main/kotlin/io/github/yamin8000/owl/feature\\\_about/ui/AboutViewModel.kt

Some articles regarding the issue

https://funkymuse.dev/posts/properly-load-data/

https://pavelkorolev.xyz/blog/2024-09-30-viewmodel-initialization/

reddit.com
u/yaminsia — 10 days ago

**I want to build a tool that checks your Google Play Store listing for policy violations before you submit. Is this stupid?**

Hey r/startups —

I'm an india developer from India and I'm trying to validate an idea before I build it.

The problem I noticed: Google rejected 1.75 million apps in 2025. Most rejections happen because of simple, avoidable mistakes in the store listing — not the code. Things like:

- Privacy policy URL is broken or incomplete

- App description has a "misleading" phrase Google doesn't allow

- Wrong content rating selected

- Permissions list has 2-3 extras that trigger a flag

- Data Safety form doesn't match what the app actually does

Google has a tool called "Checks" but it only scans your APK (the code). Nothing checks your store listing TEXT before submission.

My idea: a simple web tool. You paste your description, title, permissions, and privacy policy URL → it scans everything and gives you a red/amber/green report with exact fixes.

Before I spend 2 months building this I want to ask:

**Is this a real problem or am I overthinking it?**

If you've ever submitted an app to Google Play:

- Did you get rejected? For what reason?

- Would you have used a free pre-checker tool?

- Would you pay $9/month for unlimited checks?

Tell me I'm wrong if you think so. I'd rather hear it now. 🙏

reddit.com
u/Adventurous-Let-1740 — 13 days ago

FLAG_SECURE not working on Google Pixel devices

I am developing an Android application using the View/XML approach and need to prevent screenshots and screen recordings. To achieve this, I have enabled FLAG_SECURE using:

window?.addFlags(WindowManager.LayoutParams.FLAG_SECURE)

window?.setFlags(
    WindowManager.LayoutParams.FLAG_SECURE,
    WindowManager.LayoutParams.FLAG_SECURE
)

This works as expected on most devices, where screenshots and screen recordings are blocked successfully.

However, I have observed different behavior on Google Pixel devices (tested on Pixel 4 and Pixel 9). When a video is played in fullscreen mode using JW Player, users are still able to capture the screen, suggesting that FLAG_SECURE is not being enforced for the fullscreen video view.

Am I missing any additional configuration or implementation step for fullscreen video with JW Player?

reddit.com
u/Mckayfolker1830 — 14 days ago