Performance Issues on Android and Unimaginably bad Support!

[silentdrummer]

Hi guys,

I’ve been trying to update my Android App version for months but can’t roll it out due to the massive performance problems of native Android Apps! iOS App is fine and even the Progressive Web App on Android works like a charm!

Support keeps asking me the same questions all over again (Test User credentials and videos, which I have provided several times …) and never providing any useful information, tips or anything.

I’ve tried to migrate my “old” app to the new responsive app platform, but both versions are equally slow.

Here is a new video of the PWA on my Google Pixel 9 Pro (that’s how it should work!):

https://www.dropbox.com/scl/fi/xgz606mxqf4fk6kzmv3ek/XRecorder_20250207_04.mp4?rlkey=2thz5w4df9wkavrro7hhq01hq&dl=0

Here is a new video where I tried to do the same steps in the native Android version on my Google Pixel 9 Pro:

https://www.dropbox.com/scl/fi/h1hegqfhdpn1grru6zpkq/XRecorder_20250207_05.mp4?rlkey=9ev4jfxiwpxs172o0lluuco7c&dl=0

(please note the touch indicators which I enabled on the screen)

Even looking at this video makes me wanna throw the whole thing at the wall.

Does anybody have similar issues? Any suggestions on how to resolve this? I can’t provide test login credentials here, since this is a company internal app with sensitive data.

I’m frustrated to a point where I’m benchmarking alternative no-code platforms …

[Edward357Johnson]

Hello!
I’ve struggled to update my Android app due to significant performance issues, even though the iOS app ParentVUE and Progressive Web App work perfectly. Despite providing support with test credentials and videos, no useful solutions have been offered. Both the old and new responsive app platforms are slow.

[silentdrummer]

Hi Edward! it’s good to hear, that I’m not the only one! The more people report this, the higher the chances it get’s fixed!

How “big” is your app in terms of screens and/or database entries?
I was wondering if the “simplest” app (e.g. two screens with not much database) would already cause the same issues but haven’t taken the hassle to test it.