🔜 Update transaction feed faster

[nathanthomson8 (Nathan)]

@pshores

I’m sure a lot of user frustration on this site would be toned down with a more visible roadmap

Couldn’t agree more with this. Real disconnect now from when the monthly emails, making monzo twitter where in full flow.

[gmclean]

Publish a High Level Product Roadmap

I’ve been saying this in a number of comments recently, so thought I’d sling a new topic and see if others agree and will vote for it. I know that Monzo had a visible Product Roadmap (in Trello?) in the past, but I don’t think we need that level of visibility, a simple infographic/list that shows which features are being built: Now Next Later And yes, I think Next could also be called “Soon ” Publish this on a regular basis (quarterly/monthly) and just make sure that the only …

Vote now!!

[Rykurex (Ryan)]

I’ve found my feed isn’t updating quickly since the new update was rolled out.

[james (James Nicholson)]

@james

This is our focus now, and we’re going to keep the updates flowing so you can see the work we’re doing

Quick update!

• HTTP/2 is now rolled out in Production (we’re monitoring, but so far looks happy).
• Changes are coming in 3.4.0 to take advantage of it, so you should see a decent speed-up in next week’s release.
• We’ve added some performance monitoring (key one is “time from app foreground to latest balance drawn onscreen”) so we can see our impact as we make improvements.

Next up:

• Combining some responses with nested dependencies (I’m looking at you, Pots).
• Communicating update status better (priority of this depends on the impact of performance changes).
• Investigating some “performance-adjacent” bugs (e.g. feed updates not always happening correctly in background).

Happy Tuesday

[MalaiseForever (Ethan)]

Brilliant to hear. Looking forward to this as the performance for me has been really bad. Thanks for the update.

[jaisullivan]

@james

Investigating some “performance-adjacent” bugs (e.g. feed updates not always happening correctly in background).

Thanks for the update @james

Something I’m experiencing a lot at the moment is when opening the app after a first transaction is made for the day, that transaction sits in ‘yesterday’ with the rest of my transactions rather than ‘today’. Force closing the app then completes a proper refresh and it resolves itself.

Is this something that’s on your radar?

[james (James Nicholson)]

@jaisullivan

Is this something that’s on your radar?

Very much so!

[Liam_W]

@james

HTTP/2 is now rolled out in Production (we’re monitoring, but so far looks happy).

It’s been a while since I checked, but is this available for the developer API as well? I can’t rememeber whether the app and developer APIs are actually the same endpoints or not…

[james (James Nicholson)]

@Liam_W

It’s been a while since I checked, but is this available for the developer API as well?

It is indeed!

➜ curl -v https://api.monzo.com

* Using HTTP2, server supports multi-use

> GET / HTTP/2
> Host: api.monzo.com

< HTTP/2 200

[Jami (Jami Welch)]

Hey all,

We just posted an overall update on New Nav, your feedback, and what we’re focussing on improving first:

What's next for the new look Monzo app? We're improving it using your feedback