gbarry 2,657 Posted May 31, 2012 Share Posted May 31, 2012 We've had a lot of discussions here about the issues surrounding feature parity between clients--and more specifically between families of clients, namely desktop, mobile and the browsers (aka clippers). Many of the issues aired by users are 100% legitimate, and any amount of searching the forums shows it's something we're focused on improving with each iteration of the various clients, and that there's still work to be done.Quite often employees wade into these discussions, making various points. One of our repeated statements is to highlight the team-based nature of our developers at Evernote. Not only are they divided by products, but they're also divided by OS. I thought a recent ReadWriteWeb article about the differences between Hello for Android and Hello for IOS did a great job revealing this part of our culture, and the goals that we're trying to achieve through this team arrangement. Money quote:So why didn't these features come out in the iPhone version at the same time? It's deliberate. Evernote has two different teams building each version of the app, playing to the strengths of the two platforms, and learning from each other's performance."It's two independent teams that are really trying to talk to each other while learning from [each other's] best designs," Libin says. "It's a cooperative and friendly kind of competition. This way, [our teams] aren't doing lowest-common-denominator stuff. They're actually building full, native apps that learn from each other."The rest of the article's worth a good look. In short, we're walking the line between parity and progress, with parity being only one side of the same coin. Link to comment
This topic is now archived and is closed to further replies.