The whole cyclical thing is interesting - I wonder if the previous generation app actually regresses while the next gen is coming together, or whether it's just

The whole cyclical thing is interesting - I wonder if the previous generation app actually regresses while the next gen is coming together, or whether it's just perceptual that the next-gen is so much better than the previous one, the previous one feels stale? It's not like we've been deliberately trying for cresting & crashing cycles, so I wonder what the explanation really is. (Separately, it's obviously a questionable choice that we've rewritten the Android app 3 times now: once from old-school Android 2 (Riot) to using Kotlin+Realm (RiotX/Element), to now using rust-sdk (Element X)). About the only instance I can think of where an app has concretely regressed are the stuck notification problems on Element Web over the last year (caused by trying to fix thread notification reliability - but causing way more problems in the process, which have then been a nightmare to hunt down efficiently). Totally agreed that the transition to supporting Matrix 2.0 needs to be easy and seamless, and we'll do our best. Thanks for holding the faith...