1,624 karma · joined December 8, 2010
http://twitter.com/thesash
gmail: sashcatanzarite
The most exciting feature of the whole redesign is one that I totally missed until I read about it in the mashable article, and that's the recommendations on the homepage. It surfaces some really interesting content, and plays on foursquare's strengths which are social data and time-sensitive check ins. Unfortunately, this feature is pretty buried at the moment, and is limited to showing generalized recommendations for the current time. There doesn't seem to be any way to dive deeper into the recommendations by time/date, or to filter by category. There's a lot of potential there however, so I'm excited to see where that goes.
It is also really surprising to me that foursquare does't have a map on their search page if they're pushing local discovery.
What about adding a feature to dump the data into a google doc instead of sending an email?
For artists and designers, the stylus will be used for many years to come, but for casual, everyday use, it simply isn't user friendly. While it may be natural to draw or write on a screen with a stylus, jabbing at buttons on a screen with a stylus is no more intuitive or natural than jabbing at a screen with a finger, and in many use cases (scrolling, zooming, panning) is much less natural. The case for the stylus becomes even weaker in the face of technology like Siri, which elegantly solves the problem of text input.
The Bret Victor "Rant" mentioned in the article makes the case for exploring more dynamic, tactile, interactive experiences, decidedly not limited to one mode of input like the stylus. I, for one, hope for a future that is much more ambitious than the stylus, with new forms of interaction that combine hands, voice, and beyond. Things like this http://www.chrisharrison.net/index.php/Research/PneumaticDis... and this http://www.youtube.com/watch?feature=player_embedded&v=x... that truly push the boundaries of human computer interaction.
The irony is that concepts that intentionally ignore reality create the impression among those same people who "don't get it" that these concepts not only are grounded in reality, but are as trivial to create as the concept video makes it look.
It reminds me of this clip from Ali G: http://www.youtube.com/watch?v=nkuOuxRD1Bc&feature=youtu...
www.trello.com/ www.talkto.com/ http://prismskylabs.com/ and http://www.farmigo.com/
all of which have obvious value propositions and disruptive potential. This explains it.
A true MVP must strike the balance between feature bloat and watered down junk, driven by a vision of what users need as opposed to what they think they need. Such vision requires a lot of insight and a lot of courage. Imagine being the PM that decided the iPhone was ready to ship without support for copy and paste. Is copy and paste an important feature for a mobile phone? Obviously. Was it necessary for the product to be viable in the marketplace? Clearly, it wasn't, and that is why determining a feature set for and MVP is such a challenge.
You don't need to have a degree from art school to be a designer, just like you dont need a CS degree to write code. You can learn the basic tenants of typography, grid systems, and usability on your own. Whether or not you hire a "designer," design thinking should be part of the process of product development from day one.
Addons like IE tab for firefox/chrome that simulate other browsers work decently well, but have some shortcomings. https://addons.mozilla.org/en-us/firefox/addon/ie-tab-2-ff-3...
Compatibility testing often comes down to a compromise of picking the fewest combinations that cover the highest percentage of your audience. We tend to focus most of our time testing chrome for webkit (covers 99% of safari and opera issues), firefox, and IE on mac and pc. This covers the vast majority of our users, but we have to accept the fact that certain issues will slip through on less widely adopted browsers. Also, dropping support for IE6 cut our compatibility testing/fixing time dramatically.
General PM software gripes (jira, project, pivotal tracker):
1. lack of keyboard shortcuts: have to use mouse way too much. org-mode is so much more intuitive and efficient for task management once learned but lacks collaborations and no one wants to put in the time to learn it.
2. Difficult to get a clear picture of the overall status of projects. Project managers have to spend a lot of time gathering status updates and creating reports because we use so many different tools, and the built-in reporting generally sucks.
3. Lack of intuitive structure within data. An ideal PM platform would structure information in an intuitive way that to make it discoverable by people working on peripherally related projects.
Specific gripes w/Basecamp:
1. Don't get notifications when clients upload files, only when they post messages (they often don't understand the difference)
2. Checkboxes to send out email notifications are not checked by default for new messages. Clients always forget to do this, even when we remind them, and then wonder why we don't respond right away.
3. Refusal to use gantt charts. I get that 37signals has a philosophical objection to dependancies and detailed timelines in PM, but sometimes a gantt chart is the best way to visually display a project timeline, especially if certain milestones are missed and impact the rest of the project.