Point #1: I always assume it needs to look perfect on both. The last website I made for "desktop only" was right after I made one for "mobile only" and that was right after the Palm Treo" came out... in the 90's I think... do others make a choice in this regard and make a website that doesn't work well on the one not chosen?
Not sure why anyone would want a website that only works on one and not the other, besides of course an intranet web app for a company that knew exactly who was going to use it with what browser and what screen etc... Am I missing a use case scenario?
Yes people design UI and CMS for desktop only.
They do? I love learning about why others do things. Learning about their uses cases and how they approach them is helpful for me to be prepared when i'm confronted with something similar.
So why do they come up with desktop only as a solution? Is it because it's faster and cheaper?
We'll some programs are too bulky or the tasks they perform are too detailed for mobile devices. Another use case would be a large department store site. The site would be built for desktop first since they would most likely offer an app as a smooth alternative to a site with a lot of functionality that would overload your data and make navigation frustrating.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.