Every third website order is about functions and layout on the smartphone. “What does that look like?” “Does it work?” “Does it cost extra?” We have been dealing with this uncertainty for a long time, even though “responsive web design” should actually be standard.
So why are clients unsure at the beginning of such projects whether the new website will be displayed correctly on all devices?
2 causes in particular come into question here:
Separate position in the offer
Many clients had the experience with previous agencies that “Responsive web design” was listed as a separate item in the offer. If this item is not implemented, the question arises: How does the website look on mobile devices? Is the adaptation so complex that it will be charged extra? Is this item prioritized appropriately in relation to the others or considered from the outset in the implementation? At a time when 70% of web traffic is mobile, this should be standard.
Responsive often already standard
Design not adapted to the client
Almost every reputable web agency uses either a well-known page builder or a framework for more individual implementations. These have inherent stylings that sometimes make it impossible for the website to look any different on mobile devices than the desktop version, simply because of the use of such builders and frameworks. And this is the second problem: "Responsive web design" has long been standard, but we need to communicate this transparently to our clients AND not stop at this point in the programming. Because that seems to happen in some projects and that can lead to poor results.
Every client has different content and corporate designs that cannot be seamlessly integrated into every framework or page builder. As a result, the website often looks unflattering on smartphones.
Transparent communication
What can we do?
Even if the final steps in “responsive web design” seem tedious, they are part of modern front-end work. This way, clients know in advance that the new website will look optimal on every device and it's certainly not bad for your own references either.