@Joel Denke I’m also an Android dev, but use a iPhone for my private stuff since years, so I compare them quite frequently:)
All few months i’m looking at the state of the art Flutter apps, and test them how “native” they feel. Some month back I found a Travel app, that was created by an agency paid by Google to create a state of the art Flutter app to showcase its capabilities (I tried to find the link, but cannot remember the name). So Google paying for a Flutter app - that needs to be top nodge - was my thinking. When running this medium complex app on my iPhone it was not “butter smooth”. What I mean by that? Let’s say there is a bigger dropdown and when tapping it there is a slight delay in it opening. Or the ripple on a button would start not when my finger presses the button but shortly after. It just “felt” slow(er) compared to native apps.
What is satisfying performance? Good question. I would answer that question with “it has to be fun using the app”. Maybe that’s me seeing apps 8hrs a day - but I don’t enjoy when I feel a slight lagginess. And because iPhone users are the users that pay for in-app subs mostly, the iOS app needs to be great. so my hopes for Compose iOS are high.
@Kashismails I installed your app on my iPhone and am surprised, I don’t feel the lagginess I know from Flutter in the key areas of the app (like buttons). Great work you guys did there! Considering it’s an Alpha version of Compose, i’m impressed!
The only thing as a die-hard iOS user that I noticed, was that the “swipe right from the left screen edge” to go to the previous page does not work everywhere. I know I know, that’s how Compose works and how the navigation style on Android is - but this could be optimised maybe
like this in the future? Then my dev hearth would be satisfied😂
Great app again!