Do you care about the responsiveness while building your MVP?
Building an MVP in the quickest possible way means building only the necessary basic functional features with a lot of "coming soon" overlays.
When the product is kind of a dashboard it takes serious efforts to make it responsive for for both and desktop devices.
I have been building a product in the makers space, for makers to do better and quick user research. I think most makers will use my product from a laptop only and thus planning to skip working on the mobile web UI for now and will rather show a message saying "Please access the website from a laptop, mobile UI is coming soon".
But obviously the landing page and all other public pages will be responsive. I'll be doing a beta release first, so I'll get a chance to work on various features of the product and improve them before going public with the product.
Do you care about the responsiveness while building your MVP?
I use TailwindUI components to build a landing page and other public pages. They are all responsive out of the box.
I am using Tailwind internally but not the pre-built components, will surely give it a try. Thanks!
Hey Naman 👋
IMO, if you're confident your product will mostly be used AND discovered on laptop by your users, you can "skip" the responsiveness.
By skip, I mean you just try to achieve best results with minimal efforts just so your product does look broken, even if it's not optimal.
That's what I did when I built Edith et Nous.
In the case users will use and discover the product on mobile, you should take the time to make sure the value proposition of your product is great on those devices.
Generally, I tend to look for polished experience in the marketing website (responsiveness here) and try to go straight to the point on the MVP (best effort).
Thanks for sharing your way of doing it @axelvaindal, I am thinking on exact same lines.