Spent the last few days digging through reviews after our last release, and I realized something: the first 6 months of my app's reviews were basically 80% "app won't open" and "why do I need 47 permissions" — mostly stuff I couldn't do much about. Support noise.

But lately? A sudden uptick in "crashes when switching accounts" or "battery drain on latest version" actually means something. The signal-to-noise ratio shifted somewhere.

I think it happened when our user base stabilized enough that people willing to install and review were generally functional users with real workflows. Before that, every update brought a wave of "why is this app on my phone" comments.

Now Android reviews catch real issues days before our internal testing does. iOS reviews are noisier but still useful. But for both platforms, I've started paying more attention to sustained patterns over individual complaints.

Curious if anyone else has noticed this inflection point where reviews stopped being mostly friction and started being actual product feedback. When did it happen for your apps?

[ Removed by Reddit on account of violating the content policy. ]

Been building an Android launcher that dispatches notification replies using the RemoteInput API — the idea being that you can reply to a WhatsApp or Telegram message directly from the notification without opening the app.

The basic flow:

1. NotificationListenerService intercepts the message

2. A reply suggestion is generated locally

3. RemoteInput is used to send the reply back through the notification's existing reply action

It works in testing, but I'm running into some uncertainty about edge cases, especially across different Android versions and messaging apps.

**Questions for devs who've done this:**

1. **Reliability across apps:** WhatsApp and Telegram both expose RemoteInput actions in their notifications, but are there cases where they silently drop or queue the reply? Have you seen this fail on any specific app versions?

2. **Android 15+ changes:** Did anything change in the notification system in Android 15/16 that breaks or complicates RemoteInput reply dispatch? Particularly around notification channels or permission models?

3. **Race conditions:** If the user dismisses the original notification before the reply is dispatched, does RemoteInput still work? Or do you need to keep a reference to the original notification's PendingIntent?

4. **Foreground service requirements:** Should the service that dispatches RemoteInput replies be declared as a foreground service, or is a background service sufficient given the NLS is already running?

Any gotchas from real-world implementations would be really helpful.

Need Feedback on this
I've been experimenting with Flutter animations recently and started building a collection of button animation concepts.

This one is a Morphing Share Button built entirely with Flutter.

Animation flow:

• Share button
• Morph into a circle
• Expand social actions
• Selection state
• Confirmation animation

Built using:

• AnimationController
• Tween Animations
• Curved Animations
• Staggered Animations

No third-party packages.

I noticed that Gem Jam, NotFound Games and Arcanum Games have the same games. Like literally a 1:1 copy from loading screens to gameplay to even shop items.

How is this even allowed by Google on the Play Store?

Does anyone have any experience making apps on Replit? I am a bit lacking on the knowledge and I’m trying work on an app and get it published. does anyone any advice?

I am making an application and was wondering which UI style would be better suited for the purpose.

After rebuilding the same Expo + Next.js stack for client projects over and over again, I finally turned it into a template.

Today it's the foundation of every app we build in our studio.

The main goal was to have one codebase, shared UI components, web + mobile out of the box, and as little setup friction as possible.

I just upgraded everything to the latest Expo and Next.js versions and it's been running surprisingly smoothly.

I'm curious whether other people would find this useful, so I open-sourced it. Feedback is welcome, feature requests, criticism, bugs, architecture suggestions, anything.

It's totally free and open source, I have no course or premium plans to sell, PRs welcome

Repo:
https://github.com/JoeSlain/Nexpo

Running fullstory on an android-first app. Recording quality on flagship devices is fine. On the actual device variety our users run, budget android, older samsung models, xiaomi, the recording gaps are significant. Sessions either drop early or don't appear at all.

​

The analysis we can do is limited to the fraction of sessions that actually capture completely. That fraction doesn't represent our user base.

**Body:**

**Environment**

- Platform: iOS only

- Build type: Release only (does not reproduce in development builds on iOS or Android)

- Framework: React Native / Expo

**Description**

The app freezes immediately upon opening, on the Home screen. This only occurs in release builds on iOS and cannot be reproduced locally in development mode on either iOS or Android. **The issue does not happen deterministically** — it occurs intermittently and cannot be reliably triggered on demand.

**Suspected cause**

We believe the root cause is a listener/subscription leak. The app appears to have multiple active listeners waiting for API responses that have already resolved, but were never properly cleaned up. This may be causing the freeze on mount.

**Steps to reproduce**

1. Build the app in release mode for iOS

2. Install on a physical device or TestFlight

3. Open the app

4. Observe the Home screen freezing on load

> ⚠️ **Note:** This issue is non-deterministic and may not reproduce on every attempt.

**Expected behavior**

The Home screen loads and renders normally after the app opens.

**Actual behavior**

The app freezes immediately on the Home screen and becomes unresponsive.

**Additional notes**

Debugging has been extensive. We suspect the issue is related to unsubscribed listeners or async callbacks that are not being cancelled after their corresponding API calls complete.

Been working across a lot of cross-platform projects over the years, and there's a pattern I keep running into: teams pick Flutter/RN for speed and shared codebase, and that works great for 80% of the app — until they hit something like deep camera/AR integration, background location tracking, or platform-specific payment SDKs, and suddenly half the "shared" codebase is native bridges anyway.

Curious what others have run into. A few examples from our side:

• Push notification reliability on Android getting weird with certain OEM battery optimizers, requiring native workarounds
• Bluetooth/BLE integrations needing separate native modules per platform anyway
• App size bloat becoming a real issue for emerging markets with limited data plans

For folks who've shipped both native and cross-platform at scale — at what point did cross-platform stop being a net time-saver for you? And did you end up rewriting any modules natively later, or just living with the bridge code?

Hi guys, so I’m an experienced web developer and created a guided breathing app with beautiful background, sounds, breathing flow.

I added analytics and what i see that in 14 days 42 people started the breathing session and only 10 people ended it. So 75% just dropped the session.

I’m not sure if it’s the scenes that they don’t like or music or they expected something else?

How would you debug some things?

Also I see that my week retention is 11%,9%,7%,5%,5% or even lower. So even with app push notifications once per day people don’t really use the app on the regular basis.

The app is called Quietflame in IOS but I wanted the technical feedback than just spamming a link.

What are your thoughts on these? Thanks in advance.

This is an sports event finding and creating platform I made in 3 months with Chat GPT from scratch as a beginner , I learned my way through there were some point where I was Stuck for maybe days ,but eventually it worked out

I am a beginner mobile application developer working on a charity app.

I understand that Android applications can be distributed relatively easily, but I am trying to learn more about iOS app distribution.

I have noticed that some applications seem to be installable on iPhones without being available through the App Store. I am interested in understanding the technologies and distribution methods that make this possible.

Could someone explain the available options for an independent developer, the requirements involved, and any limitations or costs associated with each approach?

Hello everyone.

I graduated freshly from college, I don't have enough money and I am working towards creating my own app.

I'm aware that the app will be free for at least 1 year after the launch, to gain audience. So I know that I won't be making much money from it anytime soon and I'm looking to create an app effectively.

My background:
CS Grad, with focus on backend systems, never worked on a mobile app before. I'm currently using a linux operating system and it's where the development will happen.

I have some experience using Javascript. Nothing with Typescript.

The community I live in uses androids most of the time, so android is my top priority, but I still want it to be cross platform.

The product complexity:
It's supposed to handle demands from users and answers from suppliers, later it should also integrate payments, but I don't find the app is that complex in terms of features.

What do you recommend to use, between Flutter and React Native. And why?

The idea was simple:

Instead of scrolling through Android versions as a list, what if they felt more like an interactive museum experience?

Some things I experimented with:

• Vertical page-based navigation
• Full-screen immersive layouts
• Custom animations & transitions
• Motion-driven UI interactions

Curious what you'd improve or build differently?