studiofellow

11 ms·

61.
by studiofellow 14y ago
That's a great point that I hadn't considered. However, backend code does affect user experience, and having an understanding of design goals will help vet features and decisions.
62.
Not designers. Not coders. Just builders.(blog.studiofellow.com)
11 points by studiofellow 14y ago|7 comments
63.
by studiofellow 14y ago
(Disclaimer: I'm the author of one of the books linked at the end of the post.) Design is not just important for usability, but also for marketing. If you have an awesome framework, you have to get the word out so people know about it and w
64.
by studiofellow 15y ago
I'm the author. Sorry I'm late in seeing this! If you happen to check back, feel free to email me any questions at hello@bootstrappingdesign.com. I can also point you to reviews and feedback from customers.
65.
by studiofellow 15y ago
Sure, it's an imperfect comparison, but it's the closest we're ever going to get through coincidence. Same launch day, same format, similar topic. The length is different and the authors have different-sized audiences, but we should be abl
66.
by studiofellow 15y ago
You're assuming a higher price causes lower sales, but I don't think the data supports that. If you were hypothetically faced with such a tradeoff, I understand sacrificing some profits to gain more customers. But if you could have both pro
67.
by studiofellow 15y ago
I completely disagree. Everyone is creative. Design is not about learning to be creative, but about learning how to use your creativity. Here's an excerpt from the book that speaks to this: ...we assign mystical reverence to the work of pr
68.
by studiofellow 15y ago
People launching businesses face much more substantial design costs. At the high end, paying a designer $100/hr. At the low end, buying: templates, fonts, logos, icons, photos, etc. The premise of the book is how to achieve design yourself
69.
by studiofellow 15y ago
There's a sample pdf linked on the website that includes the table of contents. Here's the direct link: http://bootstrappingdesign.com/pdf/sample.pdf
70.
by studiofellow 15y ago
Thanks for posting this. I'm the author. Happy to answer any questions.
71.
by studiofellow 15y ago
The idea is to design directly in html & css. Sketch, then build prototypes. Skip photoshop/wireframe mockups altogether.
72.
by studiofellow 15y ago
Thanks so much for sharing this. Fantastic. I had no idea Hicks is colorblind.
73.
by studiofellow 15y ago
I only see the issue in Chrome and IE < 9. (Fresh install of Windows 7 via boot camp. No ClearType tweaks.) Typekit does provide samples of how the fonts render in various browser/OS combinations: https://typekit.com/fonts/calluna (Cl
74.
by studiofellow 15y ago
Great suggestion. Learning design software, at least basics, can be productive. Some designers will disagree on this point—many are moving away from Photoshop altogether. However it's more difficult to try color variations for a gradient by
75.
by studiofellow 15y ago
That's fair. I think it's about prioritizing. At some point, coding new features becomes less important than improving aspects of the design. So the tradeoff will vary with each situation.
76.
by studiofellow 15y ago
False dichotomy. People are capable of doing more than one thing. I'm a designer who writes code. Developers can learn design basics, and doing so will serve them well! You're right though about practice. That topic is on my outline.
77.
by studiofellow 15y ago
For choosing colors, I'd suggest starting with a palette from elsewhere. Just like Kuler as louhong mentioned. Starting with proven colors will be better than choosing from scratch. And that applies to everyone, not just you. I think in you
78.
by studiofellow 15y ago
Sure, and hopefully a nice compliment to it.
79.
by studiofellow 15y ago
Thanks for helping. You obviously have more experience with this.
80.
by studiofellow 15y ago
This is an issue with how Windows renders fonts. I believe Windows 7 has a ClearType tuner that could help you. (@font-face via Typekit can exacerbate this too compared with locally installed fonts.) I'll look into a fallback font for that
81.
by studiofellow 15y ago
You make a fair point, but don't we often see threads that designers should learn to code, if only to be better designers? How is the inverse not true? I'd never say someone new to design could get results equal to those from a professional
82.
by studiofellow 15y ago
Thanks so much for the list. I'll make sure it's covered.
83.
by studiofellow 15y ago
Completely understand your situation and have heard similar stories too many times. That's why I decided to start the eBook. If you would like some design feedback, shoot me an email. That offer stands for anyone else too, time allowing!
84.
by studiofellow 15y ago
Working from what you like and what inspires you is really the best place to start. I'm planning to include a checklist in the book that's more detailed than the simple preview/cheatsheet on the site right now. Thanks for the suggestion and
85.
by studiofellow 15y ago
Thanks! Cool that you noticed. It's a ligature built into the font. (Calluna: http://www.exljbris.com/calluna.html )
86.
by studiofellow 15y ago
Thanks for spreading the word! And seriously, feel free to email requests and feedback.
87.
by studiofellow 15y ago
Thanks for submitting this. I'm the author. I'm still in the process of writing and would love to make this a collaborative project. If you have topics or ideas you'd like to see covered, please leave a comment or shoot me an email. hello@B
88.
by studiofellow 15y ago
Related: http://news.ycombinator.com/item?id=3024147 http://news.ycombinator.com/item?id=3036347
89.
The follow-up to: The Knack, a web app, story.(blog.studiofellow.com)
4 points by studiofellow 15y ago|1 comments
90.
by studiofellow 15y ago
You're right. I didn't understand the market. However I'd substitute that I blame myself for not understanding my customers, rather than blaming my customers. Also, I posted a follow up here: http://blog.studiofellow.com/2011/09/26/the-fol

More ›