12 Jan 2016
Our team recently sat down and started talking about some trends we think might pick up steam for 2016. The conversation ventured down another road, trends we wish would go away. While I would necessarily call these trends, this article points out a lot of nuisances that sites still make us go through, and we still deal with on a day-to-day basis. WHY!?! Make it stop!
11 Jan 2016
A developer's walkthrough for creating a custom action inside Spree Commerces internals.
4 Jan 2016
As a core value, we define proactive as actively seeking opportunities to improve our client’s products, our processes, and our abilities. What does that mean? And why is this important to us?
22 Dec 2015
A lot has happened this year, for all of us in this world. This year, we decided instead of just focusing on us, we would take this time to reflect on our year by also highlighting charities that we support. We invite you to read about our reflections on 2015, our hopes for 2016, and the charities we care about.
17 Dec 2015
The folks over at PSD to WordPress reached out to ask about thoughts on CSS frameworks. Brian had a few words to share to their roundup.
8 Dec 2015
As a designer, asking that simple question, ‘why?’, is very critical to my job, and one I need to ask before I start anything. Why?
3 Nov 2015
A handful of weeks ago, a handful of us had the awesome opportunity to attend Portland’s Responsive Field Day; a one day conference on responsive design mirrored after Responsive Day Out— a conference put on by Jeremy Keith and Clearleft in the UK. Here's what we had to say.
14 Oct 2015
A few weeks back I saw this article from Jared Spool in my twitter feed - and the timing was eerily perfect. We were in the midst of re-examining what it was we were doing for our client and why. The roadmap we had originally created had shifted and morphed and when all was said and done, there we were with a "map" but the idea of where we were going, our focus, got hazy. To most, it just looked like a bunch of feature changes.
Building a roadmap is challenging. You know the least amount you will know at the beginning, and that is when your team (and your client) want to know what it is you plan to do and how much will it take. Historically, we've tried different approaches to make this more efficient and realistic for us and our clients. But at the end of the day, roadmaps tend to just look like a big list of features, a bunch of "stuff" that we are going to do. In the background, it's all intentional and tied to the needs we've so far determined, but it doesn't make the picture clearer. The idea of identifying the themes to focus our discussion and solutions is one I'm willing to try. It may not be the only answer for roadmaps and project scope, but if anything - it's the place to start.
5 Oct 2015
Last week, we unveiled the new Planet Argon logo to the team. We’re delighted to now share it with you.
13 Aug 2015
Yehuda Katz has announced the new major release of Ember.JS. Unlike typical major releases, they are using this major release as an opportunity to remove features (see Release Notes) that have been deprecated as of Ember 1.13. We appreciate the Ember team's mindful philosophy toward releases (and providing long-term support in a sensible manner). It definitely helps teams like us out.
Have a project that needs help?
