I’ve been in very rural parts of the UK for 4 days or so. I reported the slow down reported in this thread whilst I was in a big city but it got much worse when my network speed slowed down out in the countryside. I had 3G but I imagine a very weak version of it. Many other apps worked ok in these conditions though. I reinstalled the Monzo app as requested but it made no difference. You can see as you scroll up and down the iOS data spinner going and the feed getting stuck. It appears to be fetching lots of data and I conclude from this that there isn’t much caching within the app. Also I had a time where the balance wouldn’t update at all from £0 even though the app had known it previously. It’s a shame the app doesn’t remember the last balance relating to the last transaction seen. Fetching it every time might be an easy implementation choice with users on low latency networks but it’s pretty bad on a high latency network. The app wasn’t very usable.
I’m on iphone 8 and no issues with performance. A number of factors can affect performance besides the app but given the number of responses on here seems that the app itself is responsible. One thing I note with the iphone coming from android is that it will keep open a lot of apps with no crashes but this can impact app speed so worth killing them off then opening Monzo (double click the home button and swipe). I’d also be interested in whether this is on mobile or wi-fi, free space and iphone versions and that of the ios as there may be a common dominator.
Hi @MeganV just be aware that killing apps on iOS is completely unnecessary and can drain your battery faster. It’s far more efficient to let iOS manage your system resources. Than removing the apps from the app switcher. Also killing Monzo means you can’t take advantage of location based security features
This is true, but there is still quite a substantial lag for me either way. Leaving the app open or starting from cold (as you say and makes sense). I’ve even deleted the app and re downloaded. Make no difference.
It feels like it’s getting worse - trying to get into my account page, and scroll to pots, can take quite a long time. Could it be related to the large numbers of transaction history if it’s mostly those of us who have been using Monzo for a longer time?
I’m not an expert an ios but as a network engineer I know that feature rich content can cause web pages to slow down (if you use Chrome you can use developers tools to see this) so it would make sense. It could equally be a coding issue or device related. Do you have a lot of free space on your iphone or is it nearly full?
Hi. Sorry I think you are incorrect. Location based security can be set to when the app is in use or always. If as mine is, it’s always then security is not affected. Leaving apps open will not only drain battery but potentially use data and can be a security risk depending on the app as data will be visible and can be reopened without using the normal login verification. Monzo may not be affected but leaving apps running is not good practice.
I began noticing the issue around three weeks ago, in the TestFlight app. My first concern was that something in the new app had caused performance to deteriorate, but when I deleted and then reinstalled the App Store version, I had the same problem: when initially opened, the transaction history freezes for a couple of seconds, and then scrolling tends to stutter.
My second thought was that this might be due to the high number of transactions I’d accumulated over the past 2.5 years (over 2,200!) - and that perhaps the app’s performance deteriorated exponentially as the size of the table increased.
I raised it with the Support team, who suggested I delete and reinstall the app - but I’d already done that, so it didn’t help. It does feel to me like a genuine issue that requires resolving.
I’m using an iPhone X with 256 GB - and over 20GB free.
I’m afraid this isn’t true - talking specifically iOS here. Memory management on iOS is really clever, and looks after itself to optimise CPU, memory (RAM), battery life and storage.
For those not technically inclined, you can imagine RAM as a snapshot of an apps current state. It contains words, images, layouts that an app will reference to run smoothly etc.
When you have an app in the foreground, it actively runs, and can process tasks that use the CPU/RAM. This uses the battery.
When you click the home button, iOS quickly takes the app’s state from the RAM and put’s it into storage (and removes most of it from RAM). From that point, the app itself doesn’t call any of it’s usual code, and so doesn’t use the battery.
This happens in reverse when you reopen the app. The flash memory is super fast. it can load the apps old state and iOS injects that back into RAM before the animation of the app opening even finishes (most of the time )
iOS over time has included more and more specific actions a background app is allowed to run. These are run by the OS itself rather than the app. These include background location services, playing music, receiving phone calls etc. Having background apps can consume extra battery, for instance an app continuously requesting your location, but iOS manages this intelligently. If 3 apps regularly request your loc, iOS will only actually locate you once, and give each app the same loc, saving 2 further requests.
When you fully close down an app and reopen it, iOS has to read a lot of fresh information about the app and load that into RAM. Depending on the app, it might be a bit excessive to do this repeatedly.
Really, I would just recommend you leave iOS to manage it’s own resources. Fully killing apps is useful if there’s a bug with the app or if you have genuine concern that an app is killing your battery and you need it (like leaving Uber to do it’s thing when you’re in 10% ).
tl;dr it is definitely not bad practice to leave apps running. iOS looks after itself pretty well. Killing apps is usually unnecessary.
Since the last update yesterday it’s getting worse. When I try to click on the account tab once, most of the time it will wait 1 or 2 sec and then trigger the menu to switch to joint account even if I didn’t do a long press.
I also have to wait longer than before to see my list of friends leaving me with a illustration that I have no friends .