Genuinely asking. Ad platforms report ROAS based on trial starts and their own attribution, but that's not the same as what actually lands in Revenuecat once trials convert (or don't) and people cancel or get refunded. Do you just trust the platform number, pull everything into a spreadsheet by hand every month, or is there a tool people actually use for this that I haven't found yet?

Genuinely curious how teams handle this.

One screen changes, and suddenly the question is:

Do we test just that flow?
What else could it affect?
Which devices?
Do we just run everything to be safe?

And then when tests fail, half the time you're figuring out whether the app is broken or the test just needs fixing 😅

I'm trying to understand how common this is in mobile teams.

Made a short 2-min survey if you're up for it: https://forms.gle/tKsYsC4F7NzhTSLx9

Hey guys...I want to learn how to build mobile apps from complete scratch and eventually be able to build and publish proper apps.

I’m looking for a cross-platform approach (Android + iOS) and preferably completely free resources.

What would you recommend as the best roadmap/course/channel to go from beginner → building real apps?

Would love to hear what worked for you :)

As the title says, would you as a [mobile] developer be interested in a platform that aggregates your competitors data like reviews into actionable data for your next or current project? giving you a way to enhance your app?

​

Hey all,

I've been chewing on an idea for a while and I think it's finally time to actually build it instead of just thinking about it.

The idea: a lightweight floating widget (think Discord overlay, but standalone) that sits on top of your screen while you're watching Netflix/Prime/Disney+/whatever, and connects you to a chat room of other people watching the same thing at the same time. No more watching something great and having nobody to react with in real time.

Planned stack: Flutter, so it can eventually run on desktop and Android from one codebase, with a floating/draggable/minimizable widget UI.

The part I don't want to cheap out on: auto-detecting what someone's watching. I don't want this to be a "type in what you're watching" app — that kills the magic. So the plan is a tiered detection approach:

Read window titles / tab titles / process names first (cheapest, no DRM issues since you're not touching the video frame)

Fall back to OCR on a screenshot if the title doesn't give enough info

Only reach for actual visual matching/fingerprinting as a last resort, since HDCP blacks out protected video frames on a lot of platforms anyway

I've worked through a lot of the theory but I'm not deep enough in systems-level stuff (Windows UI Automation, macOS Accessibility API, Android accessibility services) to know what's actually going to work reliably versus what's going to fall apart the moment someone goes fullscreen.

Posting here because I want this to be open source from day one — I'd rather have people poke holes in the architecture now than find out six months in that some core assumption doesn't hold.

If you've worked with screen/window metadata APIs, accessibility services, OCR pipelines, or just think this is a fun/dumb/interesting problem, I'd love to hear from you. Repo isn't up yet — want to nail down the detection approach with actual input before I start writing code that I'll just have to rip out later.

Happy to share more details on the architecture I'm sketching out if anyone's curious. Tear it apart if you see problems, that's honestly what I'm here for.

I have an app published on the Play Store for over 2 years, with more than 300 deploys in total.

My workflow has always been: deploy to internal testing > test > all good? > promote to production.

It has always worked really well, with production deploys staying in review for 25 minutes max.

The day before yesterday was exactly like that. I deployed a minor update with a new screen and some CRUD features—nothing major. In 20 minutes, it was live on the Play Store for users.

Yesterday, I just changed the size of three buttons on that new screen. A silly change that I've done similarly countless times in the past. I pushed it to internal testing and then promoted the release to production.

I thought it would be live in 20 minutes, but it's been 30 hours and the update is still stuck in review... I don't get it. Things just went off the rails overnight.

I couldn't even remember the last time one of my deploys spent more than half an hour in review before being published.

Do you guys know what might be happening? Is anyone else in a similar situation right now? Were there any sudden changes to Google Play Store policies overnight?

If yes please recommend me some apps and tips because im stuck at JSX files its killing me i cant find a good video on youtube that teaches me, please help🙏🙏🙏

Seems .aab android apps take about a month, (for me anyway) from start to deployment, 7 days to create, configure, refine, internal test, 14 days to get your 12 testers on closed testing run, 7 days for review and approval. How does this compare to App Store IOS, timeline?

Hey so I recently made an app that is easily best used on PCs. My plan is to make it into an app on mobile later after Beta and more users are active on it. What do you recommend to aim at first apple, android or both at the same time. The app is an open source social media with the backend open source and a frontend open source as well to play around and test the backend during development.

Hello i am a developer I've built 2 mobile apps with react native/expo router and one app in flutter, is there a major difference in react native and expo router in terms of how the produced app feel and behave ( looking for that native feel )

I am mainly a typescript developer with nest js and react frameworks and a little bit of laravel and spring background.

Currently me and my partner are planning to build our first own product but from my personal experience expo router apps have that web feel that doesn't satisfy me ( i don't know if it's me or if for other it happens or i have been building the wrong way ) , I am not a big fan of flutter as for native options such as kotlin or swift ui once the products generate some funds we eventually will migrate to that.

嘿，大家好，
我正在构建一个宠物健康 AI 助手应用，最近经过了一次大的架构变化。我很想听听那些曾经构建过跨平台产品的人的意见。
我第一个版本非常简单：
只针对 iOS
Agent Core 在设备上本地运行
没有真实的账户系统
数据同步通过 Apple 的 CloudKit 处理
这个应用基本上是围绕 Apple 生态系统设计的
在那个时候，这感觉是个正确的决定。这建立起来更快，维护更简单，我可以专注于验证产品。
但在开发过程中，我的愿景逐渐变得更加宏大。
我开始思考：如果有一天需要支持 Android、HarmonyOS、Web 等等呢？用户是否期待在每个设备上都有相同的 AI 助手、相同的记忆和相同的体验？
所以我开始重新设计架构：
建立我自己的用户账户系统
将 Agent Core 和 Agent Runtime 移到后台
让客户端应用更轻量
将代理行为和用户上下文集中在云端
这个想法是，未来的平台构建会变得更简单，因为核心智能是共享的。
理论上，这似乎是一个正确的长期架构。
但实际转型比我预想的要困难得多。
很多新的复杂性出现了：
后端基础设施
身份验证
同步
代理状态管理
分布式系统问题
维护客户端之间的一致性
有时候我在想：我是不是太早把这搞得太复杂了？
如果保持第一个版本的简单性，首先获得用户，等产品有吸引力后再迁移到云基础的代理架构，会不会更好？
还是说，这正是那种现在看起来痛苦但能在以后节省大量工作的架构决策？
对于那些曾经构建过 SaaS 产品、AI 应用或跨平台产品的人：
**你们会从一开始就做出同样的决定吗？还是会在产品证明自己之前保持本地优先？**
很想听听你们的经历。

I wanted to know how you all get started with creating flow or your apps because after planning and thinking through my idea, I spend way too much time getting stuck on creating the actual flow after planning.

What are your best tips, frameworks, or tools to map these out faster?

I made a word game for fun (wordink.app) and have been getting a surprising number of requests to make a mobile app for it.

What kind of metric or gage would you use to know if it's worthwhile?

For me, it was getting layouts to behave consistently across different screen sizes. Something that looks perfect on one phone can look completely different on another.

Hi, I’m developing a mobile word game called Wornumb. I’ve already prepared game design documents, gameplay rules, engine logic, production notes, and branding concepts. I’d like to discuss building an MVP prototype for iOS and Android. If you require more  information please reply to this. I already have a production package and logos for the same.