It's bad anywhere were you would need control f or need SEO. Otherwise the main issue is performance and load times. In an app like this you don't need SEO and

It's bad anywhere were you would need control f or need SEO. Otherwise the main issue is performance and load times. In an app like this you don't need SEO and search is built in presumably. So if performance is fixed it looks quite compelling to drop the seperate web version. You would have to test load times vs. the current web implementation though. I think flutter on web currently makes sense for <1% of websites but this may be one of them.