What is the difference between dynamically serving different web designs based on the user agent versus hiring a web developer, an iOS developer, and an Android developer? A few thousand, at minimum.
You're giving me business ideas.
If you doubted the importance of responsive/adaptive mobile friendly websites...
- Thread starter Fatbat
- Start date
What is the difference between dynamically serving different web designs based on the user agent versus hiring a web developer, an iOS developer, and an Android developer? A few thousand, at minimum.
You're giving me business ideas.
As I said earlier, you can make RWD do just about anything you want it to. You can make a "one unified design" solution work on desktop, tablet and mobile, all with just plain old HTML and CSS, using media queries, and show/hide, push/pull, and resizing techniques. The user experience can be dramatically different from device to device, it just requires some creative thinking. For example, you could lead a desktop user down a 3 step form and a mobile user down a 1 step form, simply by showing them different submit buttons using just HTML/CSS, without having to do anything fancy with Javascript.
You I guess that could work since you can setup a separate split testing experiment for mobiles on the same page.
So a really good RWD designer can take a PSD of a desktop design and make it look nice even on a mobile screen?
Ideally, you're not hiring a static designer and you're hiring a front end developer who is walking with you through the design process using wireframes and then rapidly prototyping while the two of you talk through feedback on the fly.
If you hire a designer to build photoshop mockups, and then take it to a developer to make it responsive, it's still possible to get a good end product. But you're definitely adding to the challenges, and probably adding to your own costs.
Yeah, and people don't want to have to deal with that shit. That's why web design and frontend web dev are are often now combined into the same skillset. Streamlinin'
@media screen (max-comprehension: lulz_for_WFers_who_dont_think_mobile_converts){
profit:none;
}
profit:none;
}
I rarely even use PSDs these days unless the project is especially complex (for example, a real time sports betting application I am working on with a complex UI), and in those cases I don't just do one PSD mockup, but three. One each for what it will look like on desktop, tablet, and phone.
Most of the time I just get stuck in using Bootstrap and work up a functional mockup. I really hate using Photoshop to mock up web pages. I actually find it faster, especially when making tweaks to layout, colours, fonts, etc. just to use CSS to do it. There's nothing worse than having to resize and realign every element in Photoshop mockup each time you make a small change to something on the page
I'm such a novice... but how difficult is it to turn a basic HTML/CSS website into a responsive one? Should I hire someone to do it, or buy a brand new responsive template?
That's too broad of a question to answer, the obvious variable being the complexity of the design. If you have an existing design and you need it to be responsively retrofitted, your best bet is to let your developer start from a scratch point that works best for them so that they're able to move quickly versus being bogged down by pre-existing code.
For me, I won't approach projects that I don't get to start from the ground up due to the amount of friction that they can potentially cause in my workflow.