I Can’t Design in the Browser (2012)
sazzy.co.uk
I Can’t Design in the Browser (2012)
1–10 of 29 posts
Re: I Can’t Design in the Browser (2012)
#2I can see there being some users here (including me) who would think that's actually a good thing... unless your goal is to make an extremely artistic site.
Re: I Can’t Design in the Browser (2012)
#3Wireframes are good; just give me a thick marker and some pencil (or a dry erase board) and i'm set. Sometimes you need to bring photoshop in, but rarely for concept work, more to produce parts.
Also, where / when you stop designing is up to you. If you're not satisfied with the way things look, how you got there is not to blame, not enough iterations is. Start with a solid foundation and add nuances from there, instead of trying to build a full scale house out of paper.
Re: I Can’t Design in the Browser (2012)
#4If I don’t have my design to follow, the whole process breaks down for me. I’ve tried, goodness knows I’ve tried, but my designs end up suffering, looking boxy, bland and uninspiring. I can see there being some users here (including me) who would think that's actually a good thing... unless your goal is to make an extremely artistic site.
Re: I Can’t Design in the Browser (2012)
#5Re: I Can’t Design in the Browser (2012)
#6The advantage with Photoshop is most things take a similar amount of time , so you're not subconsciously changing the design based on what's easy / hard , but just what end result is best.
Ultimately if there are multiple break points then I think each should be 'designed' , not just left up to the whim of how its turns out in css.
Re: I Can’t Design in the Browser (2012)
#7Problem with designing in code is that it starts to influence the design too much if there's friction in implementing a certain look. The advantage with Photoshop is most things take a similar amount of time , so you're not subconsciously changing the design based on what's easy / hard , but just what end result is best. Ultimately if there are multiple break points then I think each should be 'designed' , not just l…
Depending on the goals of the project, that isn't necessarily a problem per se. One of the things we've been working on at my current employer is finding that nice balance between "amazing, interesting designs" and "not impossible to implement". What's fun is that if you get the balance right, design and development flow into one another so perfectly. Avocode with Sketch helps a lot with that, mind you.
Re: I Can’t Design in the Browser (2012)
#8If you don't know code then use Photoshop, get it approved by the client and get a project manager to get a developer to come up with whatever it is you have designed. Easy.
Re: I Can’t Design in the Browser (2012)
#9In a way it's like using Photoshop in that the nuances of the language don't really impact the plans at the time, though losing the prototyping can be annoying. But this metaphor does break down because I think the problem she illustrates is far worse.
Re: I Can’t Design in the Browser (2012)
#10If I don’t have my design to follow, the whole process breaks down for me. I’ve tried, goodness knows I’ve tried, but my designs end up suffering, looking boxy, bland and uninspiring. I can see there being some users here (including me) who would think that's actually a good thing... unless your goal is to make an extremely artistic site.
Even unartistic sites should aim higher than "bland and uninspiring".