The most useful posts in this topic, by likes from the community.
last year we rebuilt the rider app for a logistics client (react native this time, the client already had a RN team). riders move between areas where network is good, then 2G, then nothing, then a filling station wifi that says "connected" but nothing loads. the old app treated network as always on and riders were losing deliveries, double submitting, and calling dispatch to confirm everything manually here's what…
so we build a delivery and payments app for a client here in lagos and most of their users are on phones with 2 or 3GB ram, android 9 to 11, storage almost full because of whatsapp media. our app was "smooth" on the dev team phones and absolute garbage on the real ones. here is what moved the needle for us, roughly in order of how much it helped 1. stop judging performance in debug mode sounds obvious but half the…
abeg help, this one is killing me. app works perfectly in debug and profile on all our test phones. the release build from the play store crashes immediately on launch on some samsung A series phones (android 11 and 12). not all of them what i've tried: flutter clean, rebuilt, same thing crashlytics shows a native stack trace with obfuscated names, something like a ClassNotFoundException deep inside a plugin bumped…
small story that cost us almost two weeks, maybe it saves someone we submitted an update for a client's fintech app and google play rejected it for using QUERY_ALL_PACKAGES without a valid reason. problem: we never added that permission. i searched the whole codebase, not there. resubmitted with an explanation, rejected again. the client is calling me every morning at this point turns out android builds your final…
