Where the design community meets.
UI Designer at BaseKit Joined about 6 years ago Dale-Anthony has invited David Darnes
Very nice. Does anyone know how to create a similar looking text effect to the one they're using on the updates?
I've had one of these on my phone for a year now, it's awesome... you don't even notice it's there.
Not as grippy as the silicone cases, but not slippery either.
The one gripe I have is that after a few months of use the area around the volume button seems to warp, but the customer service is great and they offered a replacement case both times.
For those of you in the UK it might be worth checking out Vesper cases if you want to save on shipping costs, these look almost identical (although I haven't used one myself): http://vespercase.co.uk/
Caved and bought does.design just so I could have dale.does.design >.<
I couldn't resist.
I always find infographics like this interesting. A shame about the bottom right though.
Right now Chrome, but I may give Safari a good chance when Yosemite is released.
Chrome is a great browser but they're forcing Google Now a bit too much for my liking. I seem to have to find a way to disable it again with every new update.
Maybe I should have titled the post Ditching Bootstrap, rather than Ditch Bootstrap. This is an approach I've found useful and wanted to share with people as a suggestion, I'm not claiming this is the only way things should work. Just because you don't agree with my points I don't think it means the post is 'link-bait'.
In my experience developers often mindlessly setup bootstrap as a quick way for them to get started on a project, and then having committed to using it it becomes a big obstacle later down the line.
So many times I've heard things along the lines of "Sorry, I can't implement X/Y in this way because bootstrap JS expects it to work like this...". If I designed something to work a certain way, I did it for a reason. I know that I'm not limited to using what's been bundled with Bootstrap, but most of the time I don't get much say.
The approach I've suggested is one that was thought through with designers and developers from the beginning and has resulted in better communication, understanding and seems much more flexible and manageable for both teams.
I do agree, I'm not saying that this is a process that everyone should use, simply that there are better options (in most cases).
I'd say that for large products where a fairly good design and development team exists it makes more sense to use an approach which doesn't involve a heavy framework like Bootstrap, it's easier to build one tailored to the product, something that can evolve and grow over time.
I guess that with some smaller websites where budget and time are restricted Bootstrap can be a sensible option :)
Yeah, a discussion for each subject I think is acceptable, and maybe also a general one for the event. It's fairly quiet right now but when the event kicks off I imagine a lot of the same links and discussions are going to be added.
I think a 'post group' / category would be a good post type addition to DN, or maybe even something like a live discussion (that's within DN and doesn't require Slack, IRC, etc) for events like this.
For now I've moved to Raindrop.io, absolutely love the way it works (the onboarding process was awesome).
I'm keeping an eye on http://useoctobox.com too, looks like it could be a good contender!
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.