No. I used Flow on a daily basis for the better part of two months, to coordinate a team of six on a major product feature we were developing. The things I me

No. I used Flow on a daily basis for the better part of two months, to coordinate a team of six on a major product feature we were developing. The things I mention above are chronic issues I ran into every day, not superficial things I saw once before dismissing the thing. They're also 100% fixable. If you're going to do this sort of "empty container" app, it's worth modifying your approach a tiny bit and instead going with "filled container". That is, sending the actual page content over the wire, then doing all your smartness and auto-updating behind the scenes where the user can't see it. You get all the benefits that the browser gives you for free such as cache management and back-button support, and you can also build in all your rich UX just like before. And of course, if you're going to rip out a 20-year-tested native control like the scrollbar, it's up to you to make absolutely certain that the thing you replace it with is better. Theirs is demonstrably worse in pretty much every way a scrollbar can be worse, and actually fails the simple case of "scroll the document", as it tends to lose its position. The fix for this is as obvious as it is easy to implement: use the native scrollbar to scroll your list. If they do those things, they may win me and my team back.