We had the honor of being interviewed on the awesome podcast, Iterate, recently. We spoke with Rene Ritchie, Marc Edwards, Seth Clifford, and Andrew Martonik about Press, Android design, the Google Reader retirement, and lots more. It was our first podcast appearance, and we’re pretty happy with how it turned out. You can listen to the episode on iMore or Android Central.
We were among the unlucky developers that didn’t snag tickets for Google I/O in San Francisco next week. However, we’ll be at Google I/O Extended in Chicago at 1871 on Wed, May 15 and Thurs, May 16. If you’d like to meet up or just say ‘hi’, let us know through Twitter, email or Google+. We’d love to have some of the rare face-time with people in the community at 1871, or just get a coffee downtown. Let us know if you’ll be around!
We’ve been intentionally quiet the past two months, but continued to work hard in preparation for the post-Google Reader world. There has been a ton of movement in the RSS space during that time, and we’re really excited about this next chapter. We’ve been exploring a lot of different options over the past several weeks and feel we’re in a place where we can announce the first round of services that Press will support. Each of these services offer unique features that enhance the traditional Google Reader experience. Drumroll please…
Just to be clear, there will be more services announced soon. These are three that we have been spending time with and feel comfortable going forward. We think that they fit well with Press, but they also offer a wide variety of features to choose from. Some of these syncing services are also iterating quickly, so the features you see now will also be improving at a rapid pace.
Our goal going forward is to roll out these services as soon as we have them implemented to match Press’ current feature set. Keep in mind, some services may take longer than others to get them ready to ship. We also want to incorporate service-specific features where possible. Please let us know if there’s anything specific from these services that should be integrated into Press.
Thank you to everyone for the emails and tweets letting us know what services you are interested in. It’s been incredibly helpful as we made these decisions. If you have any other thoughts or features requests, be sure to let us know on our new UserVoice page at http://twentyfivesquares.uservoice.com. We’ll be providing updates on the availability on these services in Press, so watch for those in the near future.
Most importantly, THANK YOU to all of our amazing customers for supporting us during this transition!
We started this blog to document our processes, failures, successes, and beliefs as a company to help share our story. But, we also want to share more personal experiences as well. We’ve had a journey and we want to share it with those who may find it interesting. This is a post about the latter.
A few years ago I held a belief that I now know to be incorrect. I had just started a new job with a startup company that offered software and services for the healthcare industry. But that wasn’t the thing that attracted me to the position. It was the people. So many talented people worked there, several of which were my close friends. On top of that, it was going to be challenging work with a good salary. It was my first career job where I truly liked and respected the people I worked with. I believed that working with great people would keep me happy.
I stretched myself as a developer and gained many new skills. I learned new ways to deal with performance issues and work around framework constraints. I learned the value and importance of code reviews and having continuous integration testing. Most importantly, though, I learned how to work with really smart people to develop a large product. All of this new learning was very exciting.
But with time, that excitement faded. I would wake up each morning wondering how I was going to muster up the energy to work on a product I ultimately didn’t care much about. I would wonder if someone would find out that I wasn’t working hard enough. That lead to guilt. Lots of guilt. I felt guilty that I didn’t care about my work as much as I should, and felt guilty because I wasn’t investing enough of myself into the company. Additionally, I was being paid well and complaining about my job, while some of my friends were just trying to scrape by. I wasn’t even willing to be honest with myself about why I was feeling this way. I thought there was something wrong with me. Why couldn’t I be happy with a great job making a good salary? Can’t I just suck it up, play it safe, and live comfortably? I was miserable, and probably pretty miserable to be around.
But as Jordan and I worked many long nights and weekends on what would eventually become Press, I began to understand exactly what I was missing in my day job. Passion. It seems obvious now, but I’d never had the opportunity before to create something that I truly cared about. I didn’t realize that passion was the missing piece that would give me energy and spark the creativity that I’d been hoping for.
Working with great people satisfied my hunger to work hard on a good product for a couple years. But eventually that faded, and my personal desire for something more had been suppressed too long. I still believe working with great and talented people is a key component of doing something successful. Without passion, though, it took me down a dead-end road. In fact, I allowed the presence of guilt and complete absence of passion in my 9-to-5 to affect other areas of my life in negative ways. And I’m still trying to pick up some of those pieces.
I have a massive amount of respect for Jordan, I trust his opinion, and we work extremely well together. But, it’s our love for creating great products that people will enjoy that elevates our focus and energy to a much higher level. We’re not afraid to challenge each other and strive for something better, and we have fun doing it.
Now, waking up in the morning with a clear conscience and the excitement to tackle the day is an amazing feeling. I feel really lucky to be doing something that I love, especially knowing that a lot of people never get the chance. This past year I’ve learned a lot. I have a better idea of who I am and what I want to be doing. I’m sure I will reach more difficult crossroads in time, and when I do, I want to acknowledge them and be more honest with myself. I want to learn and grow. And I bet I’ll end up a better person for it. That sounds pretty great to me.
Android is an interesting beast. There are lots of myths, stereotypes, and assumptions surrounding Android and it’s community, but that’s not what this post is about. This is about design, quality, expectations, and looking forward.
I’ll just come right out and say it: Google really failed at it’s early attempts to build a thriving ecosystem of high quality apps. There are several reasons, but I think the lack of focus on design and experience had a large impact. Prior to version 4.0, Android wasn’t very thoughtfully designed, and it wasn’t an inspiring canvas to design creative and beautiful interfaces. In addition, Google never created sufficient design guidelines for its developers. The combination of these factors gave developers implicit permission to design apps without much thought or care. But that’s the past, and things have been changing quickly.
There’s an obvious turning point in Android’s timeline, and in our opinion, one of it’s most important. It was the hire of Matius Duarte in May 2010, who previously led the design efforts of Palm WebOS. It took some time for his influence to fully spread throughout the veins of Android, but the rate of improvements in the last 12 months has been nothing short of impressive. There are still visible consistency issues, but from the lock screen, to the home screen, to Google’s own apps, there’s an obvious trend going on in Mountain View, and Android is, in many ways, a playground and inspiration for new areas of design.
As we worked on Press this past year, we knew our focus would be newer devices, but it wasn’t until September, 2012 that we made the difficult decision to only target 4.0+ devices. At first it seemed like a risky move, leaving behind a huge market. But, once the choice was made, it freed us to cut ties with the past and look forward to what we truly wanted to create. And we don’t have a single regret about that. Sure, we probably missed out on some potential revenue, but we’re a small team and focusing our efforts on the newest technologies and design initiatives by Google allowed us to concentrate on the things that were most important to us.
We’ve been pleasantly surprised at the amount of positive feedback we’ve heard for some of our design decisions. We still have a lot of work left to fully create what we’ve envisioned, but it’s time that’s our limiting factor, not the platform. And here’s the cool thing that we found: what was obvious to us, when putting lots of care into the small details, is also what many Android users have been craving for a long time. Design is important, and people are willing to pay for it.
Maybe it’s not apparent to everyone yet, especially those on the outside, but there’s something exciting that’s stirring in the Android community. Google’s top-down design initiative is starting to take root, and new apps are starting to turn heads every week. So why did we choose Android? Because there’s a huge opportunity that’s still untapped, and we wanted to be a part of it. We think 2013 is going to be an exciting year for Android as new, creative designs push away the old cruft. And we’ll be working hard towards that goal. We’re excited about the developers who are doing amazing work and taking Google’s design guidelines seriously. Thanks for inspiring us!