Hi everyone! 👋

I'm curious to hear your opinions.

If you had to develop a single mobile app that runs on both Android and iOS, which technology would you choose today?

Some obvious options are:

• Flutter

• React Native

• Kotlin Multiplatform

• .NET MAUI

• Native (Swift + Kotlin)

• Others?

I'm especially interested in feedback based on real-world experience, such as:

• Performance

• Ease of development

• UI consistency

• Maintenance over time

• Community and ecosystem

• Long-term viability

• App Store / Play Store publishing experience

For context, I've already built and published my first Flutter app on Google Play, and I'm now considering the best approach for future cross-platform projects.

I'd love to know:

• Which framework are you using?

• Would you choose the same one again today?

• What are its biggest strengths and weaknesses?

Looking forward to reading your experiences! 🚀

Want to continue development on Windows without switching to mac ? or don't have a Mac at all ? Nc problem.

You can now run / test your iOS apps on iPhone directly or in a paired from Windows. VS Code extension, CLI & GUI support. Try CapMac

Our iOS app launches in three weeks and the code is still changing too much to justify days of tagging buttons that'll probably move next week we need visibility into onboarding and the main conversion flow at minimum leaning toward mobile app analytics tools with so we can add targeted events once real usage shows up if you launched this what did you track from day one and what could wait ?

Is anyone here currently building a mobile app? I'd love to connect with other people who are working on apps, share ideas, talk about projects, and maybe become friends along the way.

Doesn't matter if you're experienced or just getting started. Always down to meet like-minded people!

We've been on amplitude for about a year and it's fine for event reporting, but our app is mobile first and click style events don't answer much about gestures and navigation. swipe to archive, long press menus, pull to refresh loops, none of that shows up in a useful way mixpanel is on the list too has anyone moved to an alternative to amplitude for mobile apps that handles touch interactions better ? did debugging behavior actually get easier or was it the same data in a different dashboard ?

I'm currently working on client projects and I'm trying to figure out what stack to use for new ones. I’ve done some cross-platform projects before but I still have reservations about performance and maintenance in the long term. What are you guys using currently and why?

I’ve been developing Android apps since 2012, and sometimes I wonder how many times I’ve had to start over with this ecosystem.

Every 3–4 years, it feels like something major changes. Eclipse to Android Studio, Java to Kotlin, XML to Compose, different architecture patterns, libraries becoming obsolete, and Google constantly changing what’s recommended.

Don’t get me wrong, a lot of these changes have made Android development better. But after spending years mastering something, it can be frustrating to see it slowly become outdated.
What bothers me isn’t learning new things. I actually enjoy that part. It’s the constant feeling that you need to keep up with everything just to stay relevant.

Last year, I decided to shift my career more towards software architecture and technical leadership. I still enjoy coding, especially Android, but I wanted to spend more time designing systems, solving larger engineering problems, and making technical decisions rather than constantly chasing the next framework.

Sometimes I miss the old days when I could just sit down, build an app, and not worry too much about whether the recommended way of doing it would change in two years.

Curious if anyone else who’s been developing Android apps for 10+ years feels the same.

Has anyone here moved from Android development into architecture, backend, engineering leadership, or something completely different? Do you miss being a full-time Android developer, or are you happy you made the switch?

I know there are so many options to build mobile apps nowadays! Overall, I heard that there are both key advantages and disadvantages for each framework!

Personally, I have been using flutter to build ios and android mobile apps since December 2025! I used SwiftUI one time back in the beginning of October 2025 and I was not as familiar with it. That is because SwiftUI limits building apps only for ios and compiling for ios and android is my priority! Before flutter, I used react native for a while and I did not enjoy it as much! That is because the javascript bridge in react native was too fragile to use!

Which mobile app framework do you use to compile for which platforms?

App: Cartoon Weather

It has animated characters that react to real weather. The one shown in the widget "Memling" theme. Pretty fun to use!

Link if anyone's interested: https://apps.apple.com/app/id6757344541

I ran into the rotation bug where my app resets every time I turn the phone. From what I understand Android recreates the Activity on rotation so normal variables lose their values. I’ve read that ViewModel survives rotation so I’ve been putting my screen state there. I also found rememberSaveable, which apparently survives rotation and even the app getting killed in the background. Is that right? Also what do you actually do in real projects? Do you keep almost everything in the ViewModel or do you use rememberSaveable and SavedStateHandle for some things too? Would love to hear what works for you.

I’ve been working on Argent, an open-source MCP server that lets your agent (Claude Code, Codex, Cursor, etc.) use any app running on an iOS Simulator or Android emulator, whether it’s native, React Native, Flutter or KMP. It can tap through flows, read logs and network calls, inspect the view hierarchy, profile performanxe aaaaand many more 😂

If you’re already letting an agent drive your app, what’s working, and where does it fall apart? We really want to keep improving the experience 🤭

Senior backend engineer here (Laravel/NestJS) trying to decide between Flutter and React Native for my first serious mobile product.

I'm strong in Vue, would need to revisit React, and have no Flutter experience.

The app itself is a fairly standard business application (authentication, listings, search, maps, chat, payments, push notifications, QR scanning).

I'm not asking which framework wins benchmarks. I'm more interested in the experience of living with the choice.

If you've maintained a production React Native or Flutter app for a couple of years:

Would you choose the same framework again today?

What pain points only became obvious after the honeymoon phase?

If you were starting from scratch in 2026, what would you pick?

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?

I want to know which competitors can show exactly where checkout friction happens in a native shopping app mobile checkout converts significantly worse than desktop and we need to see why not just funnel percentages but the actual user experience most ecommerce analytics tools are strongest on web for native app checkout the friction points are different curious what tools people are using to see where native app checkouts break down ?

Since I have access to Fable 5.2 till 11/16/2026, I just spent a few days using my cheap subscription to the max. I won't comment on the price, but generally, I see no reason to use it over Opus 5.5 beyond very rare investigations. I am NOT building a 3d game. Observations:

a) Give me ideas to make more money from my app: It gave me only 1-2 out of 10+ that I came up in a 15 min of a self-brainstorm. Missed the largest ones. FAIL.

b) Make targeted code changes in existing code base: the quality of the fixes is EXACTLY the same as Opus 5.5. Both the good and the bad: the ability to fix is present. The inability to do it with a single prompt is also present. The same reluctance to do large pieces of work in one shot. Same.

c) Design - again, the same. It produced the same design that Opus 5.5 does with the same common sense flows. Same.

d) ML work: Feels better. Fable was able to find a new training set and it gave less of the obvious non-sense of Opus. It still feels a bit crippled, but maybe it is my perception.

Overall, using Fable 5.2 consistently doesn't give me any advantage. What is your experience?

our product team sends me maybe a dozen small questions a week about the mobile app and every one turns into a query we're around 40k mau events land in the warehouse fine and amplitude covers dau and basic funnels but anything like what were people doing on this screen before they quit ends up in my queue and by the time i answer the sprint has moved on has anyone set up mobile product analytics without sql that PMs can actually self serve on without it becoming a second source of truth that disagrees with the warehouse ?

i want to build a flutter app that is actually difficult to make and not just another basic app

i am a first year csda student at iit patna and i want to work on something that can challenge me technically and help me learn new things while building it

i am looking for ideas that are unique or solve some real problem. it can be anything like a complex mobile app, a tool, something involving networking, offline support, databases, system level features or anything else interesting

i dont want another todo app chat app or ai wrapper. i want something where i might have to spend weeks figuring out how to make things work properly

i will be building it solo using flutter and i am open to ideas that sound crazy or too difficult at first

what is the most challenging flutter app you can think of that one developer could realistically start building?

also if you have built something difficult yourself i would love to hear about it

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🙏🙏🙏

Hi folks. 8 years of experience in the software engineering industry, most of them in machine learning and data engineering. I'm beginning to dabble into mobile applications dev and am having trouble finding good resources (or don't know where to look) on how to architect a "full-stack" mobile application.

I attempted to create a PWA for a personal finance tracker, and while it looked like a mobile application, it didn't feel as snappy since every action was backed by a network call. This was a very stark contrast to other personal mobile-native applications that I was using wherein the network faded into the background, since every action was quick, snappy, and felt like everything was running locally.

I want to build such applications, but I'm not sure where to start. I'm hoping you kind folks will guide me on how these things work in concept/theory, so I know what best practices look like.

Just to share, my personal research pointed out to me that how these mobile-native apps work is that their primary persistence layer is an on-device DB like SQLite, that's why everything is snappy and blazing fast. The data is persisted through cloud via batch syncs. Would be helpful to know whether I should follow in this direction or not.

Last thing I wanted to share is that, now that I think about it, I might be completely off base here. I suppose the main advantage of having a mobile application is that not everything has to be backed by a server, since you can completely process everything offline in your device.

Any guidance would be appreciated. Thanks!

Let's say i know programming and i have worked on so many project previously but some of reasons i have not access of my laptop so can i build big projects only using my phone? If yes then what tool i can use to code my project end to end, Let's it's a full stack web app!

Eager to know!

It's good for stack traces but we are still guessing at the steps behind some of our rarer crashes a few only happen on specific devices and we want to know which screens users hit or if the app froze first Im looking at mobile app crash tracking with user context alongside included what have other mobile teams paired with crash reports and did it make the hard to reproduce stuff easier to investigate ?

What are the best ways to create store screen shots for 4/5 languages.

I tried few open source website/apps available, but that requires me to run my app in all the language, manually keep taking each screenshots and then going to such app and then inserting it.

What are some best approaches to go about creating such assets?

What are some tips to create successful localised store fronts for localised audience?

Any help and guidance is much appreciated!

We’re picking a session replay tool for a banking app and masking is basically a yes or no for us if compliance can’t see proof that account numbers balances and anything typed into a form stay masked in recordings, it doesn’t get deployed

the big enterprise options seem to handle this fine but they’re priced and scoped for a team a lot bigger than ours. We’re small but the compliance bar is the same as at a large bank for anyone who’s been through this in fintech, what did your compliance or security team actually ask for before signing off? things like masking by default vs opt-in, whether it happens on the device or on the server, audit logs, that kind of thing, and if you found something that cleared review without the enterprise price tag would love to know what it

i keep going back and forth on this a hand maintained event schema is cleaner when people actually maintain it but it's easy to miss something in a release and discover the gap weeks later when someone asks a question you cant answer auto capture looks convenient until youre cleaning noisy data for people using product analytics tools with auto capture in production how much do you rely on it day to day and which events do you still insist on defining manually ?

I have recently launched an app on android as well as iOS. I have added analytics to it but they are strictly opt in only. I give user a pop up and then if user consents, then app starts sending the analytics. There is explicit toggle to disable it in prefs.

What are common norms and regulations related to sending app analytics? Is it common to send analytics by default? Does it violate any regulations if its enabled by default?

How are other devs building the analytics?