SmashingConf NYC 2015 will challenge you to rethink how you design and build websites today — and how to touch someone's heart with design. 1 track, 2 conference days, 5 workshops, 16 excellent speakers and just 400 available tickets. With the main focus on practical takeaways from real-life projects, you might never be the same again. To the tickets.
You’ve been around for quite some time, haven’t you? You know your way around front-end, or UX methodologies, or mobile patterns, or even the obscure dark matter of responsive web design. But you might not feel just right with your workflow, with the techniques and strategies you use, or perhaps with the amount of time required to get things done. Your techniques are pretty good, great even, but they just aren’t good enough.
Last week, Microsoft made its biggest announcement for the web since it first introduced Internet Explorer in 1995: a new browser, codenamed “Project Spartan.” So, what does this mean for us as designers and developers? What rendering engine will Spartan be using, and how will it affect our work? We spoke with Jacob Rossi, the senior engineer at Microsoft's web platform team, about the new browser, the rendering engine behind it, and whether it's going to replace Internet Explorer in the long run. This article, written by Jacob, is the result of our conversations, with a few insights that you may find quite useful. – Ed.
Spartan is a project that has been in the making for some time now and over the next few months we’ll continue to learn more about the new browser, what it has to offer users, and what its platform will look like. It will be a matter of few months until users and developers alike will be able to try Spartan for themselves, but we can share some of the interesting bits already today. This article will cover the inside story of the rendering engine powering Spartan, how it came to be, and how 20 years of the Internet Explorer platform (Trident) has helped inform how our team designed it.
It’s no secret that the digital industry is booming. From exciting startups to global brands, companies are reaching out to digital agencies, responding to the new possibilities available. However, the industry is fast becoming overcrowded, heaving with agencies offering similar services — on the surface, at least.
Producing creative, fresh projects is the key to standing out. Unique side projects are the best place to innovate, but balancing commercially and creatively lucrative work is tricky. So, this article looks at how to make side projects work and why they’re worthwhile, drawing on lessons learned from our development of the UX Companion app.
AngularJS presents a remarkable number of interesting design choices in its code base. Two particularly interesting cases are the way in which scopes work and how directives behave.
The first thing anyone is taught when approaching AngularJS for the first time is that directives are meant to interact with the DOM, or whatever manipulates the DOM for you, such as jQuery (get over jQuery already!). What immediately becomes (and remains) confusing for most, though, is the interaction between scopes, directives and controllers.
As members of design teams, we want as many people as possible to use what we create. This is true whether we are designing a specialized medical device for a specific type of surgery or something more mainstream, like a smartphone or video game console.
We often focus on the importance of ensuring our product is usable. Less often, we discuss other factors related to people accepting and using our products. Users don’t automatically or simultaneously accept even the best ideas and most useful technologies. Acceptance and adoption happens in stages, and in order to stick, it has to happen the right way. Therefore, our design teams need to account for both usability and how the use of a product spreads across users in order for our work to have maximum impact.
We’re all resigned to it: launching a browser reloads every tab you previously had open, blasting a cacophonous mix of sound and video. While browsers have made it easier to control this experience with tab icons and extensions like MuteTab, for most people this behavior presents a confusing and disorienting experience. As developers and designers it’s our job to make the web welcoming, not overwhelming.
Doesn’t it make sense that sites should only be active when they are the primary focused tab? Why are we burning up batteries and processor cycles with animation that can’t be seen?
Digital experiences are emulating real life more and more every day. This may seem counterintuitive, considering the hate that rains down on skeuomorphic visual design, but there's a lot more to emulating real life than aesthetics.
Interface designers can emulate real-life physics and movement on a digital screen. This type of motion is becoming more common, which is why it's becoming easier for people to understand computers. We're not getting better, the interfaces are!
It’s been three years since I launched my productized service. And, boy, did I do a lot of things wrong! But I’m glad I did. If it weren’t for the many mistakes I’ve learned from and lessons I’ve applied, my business never would have grown to replace my income as a freelancer.
As it turns out, I wasn’t alone in my mission to move away from client work and into a products business. Every day when I read the replies I get from freelancers who read my newsletter, most tell me they want to do the same but that making the transition seems almost impossible.