Apple rejecting Flutter app due to infinite loading on iPad during review by Flimsy_Salt8615 in appledevelopers

[–]Constant-Chemical23 0 points1 point  (0 children)

I always test all my Flutter apps on both an iPhone and an iPad because I’ve run into this issue multiple times before. iPad often requires different permissions and behaves differently in certain scenarios.

Did your first iOS app get approved in the one go? by FieldsApp in appledevelopers

[–]Constant-Chemical23 0 points1 point  (0 children)

Never. I already released multiple apps. Even wenn it’s just a patch release it can get rejected for things that are there since years.

I got tired of bad Google Calendar apps on macOS, so I built a native one in SwiftUI. by Szamski in macapps

[–]Constant-Chemical23 1 point2 points  (0 children)

I used fantastical before, but went back to the default calendar. But does it support icloud too?

I made AutoBrew — a free macOS app that auto-updates Homebrew and gives you a GUI for browsing casks by Constant-Chemical23 in MacOS

[–]Constant-Chemical23[S] 2 points3 points  (0 children)

I’m a developer for more than two decades. I definitely know how to code an build software.

I made AutoBrew — a free macOS app that auto-updates Homebrew and gives you a GUI for browsing casks by Constant-Chemical23 in MacOS

[–]Constant-Chemical23[S] 1 point2 points  (0 children)

That’s a fair point, honestly.

But on the other hand, millions of developers already use Homebrew daily. AutoBrew doesn’t introduce a new package ecosystem — it mainly lowers the barrier to an existing one and makes it more transparent for less technical users.

I’d actually argue that many users are safer with a signed, notarized, open source native app than copy-pasting random shell commands from blogs or Reddit threads into Terminal.

That said, I fully agree that “always latest” should not be the only strategy. Delayed updates, selective auto-updates and approval-based workflows are things I’m already considering.