New post on /r/flutterdev subreddit:
<b>Why we chose Flutter Web to build our production website instead of Tailwind or Bootstrap</b>
When building a new website for <a href="
https://codelessly.com/">Codelessly</a>, we had to make the difficult choice of which platform to use. Initially, we dismissed Flutter Web as a viable option. This is the story of how we ended up choosing Flutter Web in the end.In the beginning, we considered the possibility of building our website in Flutter but quickly dismissed that idea. Our website needed to be production quality. It was going to be seen by users, not to mention investors. The website had to work and work well.Flutter Web has not been declared "production-ready" yet by Google and has quite a few usability issues. In our previous experiments building Flutter websites, we discovered the following issues:Scroll lag - long webpages don't scroll well on mobile.
Unable to scroll - scrolling is broken on some browsers.Text clipping - text rendering is incorrect.Non-native behaviors - unable to select text, no hand cursor over links.So, having ruled out Flutter Web, we turned to other frameworks.First, we tried Bootstrap. Our lead developer worked with Bootstrap for many years and was familiar with the framework. However, we quickly ran into CSS styling issues.Getting started with Bootstrap, the first thing we did was begin customizing the CSS styles and Bootstrap elements to match our design elements. We styled buttons, setup the H1, H2 text styles, and in general themeing Bootstrap. The process was very time consuming and 4 hours in, we still didn't have any layout elements. That's when we started thinking about Bootstrap's legacy problems and decided that it was taking too long and wasn't worth our time. Most of all, we realized that we weren't having fun and were getting bored. So we decided to move on to something new and give Tailwind a try.None of us had too much experience with Tailwind so it was very exciting to dive into a new framework. Very quickly though, we realized that we needed to take time to learn the framework. But because we also needed a website by the end of the day, we decided to get a head start from existing templates.We found some very beautiful templates with wonderful components that somewhat matched our design and got to work customizing them right away. The next 4 hours were an exercise in frustration. For the life of us we couldn't figure out how to free float a background image and have it frame our animated UI image on different screen sizes. We also had trouble combining elements from multiple templates together to get our desired design. To this end, we realized that trying to skip the proper setup and development process meant we couldn't create our exact design and would end up with a non-professional website.It was getting late so out of desperation, we started trying out website builders. All we wanted to do was position our page layout elements and add an input form. We must have tried over a dozen website builders but they all fell short some way or another. Most did not support background images and stacked layouts, instead forcing us to use existing layouts. The ones that did support custom layouts had one issue or another with input fields.The email input field is critically important and our input field design was very specific. We specified conditional behavior that shows a vertical layout on mobile and a horizontal layout on desktop. The input field also needed to switch to capture first name and last name after the user entered their email. From a business side, we wanted to enrich emails with a first or last name for more personalized correspondence.Trying to hack together what we wanted within the limited and very poor functionality provided by website builders was a nightmare. In short, website builders do not have good form builders.By this point, we were too exhausted to continue and decided to call it a day. The most frustrating part of…