Making technology look good

Avatar

My Palm Pre impressions, day 1

In response to being asked how the Pre compares to the iPhone:

In all fairness…I’ve been a Palm fan for years, but I’m not too brainwashed to say that there’s a place in the market for both. Pre and the iPhone each have pros and cons, and the Pre meets my needs the best. For me, having a physical keyboard, carrier availability, and choice of development platform are high priorities. YMMV.

Now with that said, WebOS and Synergy are amazing new technologies that are full of possibilities, but I fairly and lovingly admit that certain aspects of the Pre reinforce the fact that it’s a v1.02 device. Things you’ll love: everything about the hardware, how easily it integrates with online services, beautiful multitasking, gps navigation, and push email. Things you might not like: unoptimized calendar experience, short battery life, and limited application selection. The people currently best suited for the Pre are early adopters, users without advanced requirements, and linux hackers (I’m trying to find a way to SSH into my phone as I write this). Since there are so many people excited about this device, I hope to see Palm engaging the community to incorporate our feedback into future updates (which I expect within a month or two).

…that got a bit too involved, didn’t it? The Pre’s a great phone. Buy it, bitches.

About the author: Lisa Brewster is a project manager and startup advisor in San Diego, CA. Subscribe to this blog by RSS or email, or follow me on Twitter for more updates.

The future of preDevCamp

On Friday, Dan Rumney made some important announcements on the preDevCamp blog that I’d like to expand upon.

Meet your new organizing team
To fill in for whurley’s and Giovanni’s unfortunate departures, Greg Stevenson and myself will be stepping in to help co-ordinate the various preDevCamp events around the globe.  Greg has already been hosting some webOS training sessions (pre-preDevCamps, if you will), and will be invaluable bringing this knowledge to the community.  And while I’ve helped plan a barcamp or two, I’m positively giddy for the chance to help build a stronger community and facilitate knowledge transfer on such a massive scale.  Combined with Dan’s experience bringing preDevCamp where it is today, I think we’re going to make a wonderful team.

New target date:  August 8th
The second major announcement is regarding preDevCamp’s target date.  Several cities have expressed concern about organizing events on such short notice and without guarantee that the SDK will be available.  Palm hears our cries about the SDK loud and clear, but there’s a lot more involved than just making sure everyone has a copy of the software.  We still don’t have a confirmed SDK release date, but I’m very optimistic that pushing the date back to August 8th will give Palm time to finalize these issues.  And while August is later than the expectation that was originally set, it’s still only 9 weeks after the launch of the phone (recall that the iPhone SDK was released 9 MONTHS later).  Also, 9 weeks is the same amount of time it takes to make kittens.  Coincidence?  I think not.

More content coming soon
Momentum since the phone’s announcement has ebbed due to a lack of developer-related news, but now that the cone of silence is being lifted we can start featuring content created by Palm and other preDevCamp members.  The goal here is to provide maximum visibility to emerging community leaders and create a repository of reusable presentations, therefore lowering the barrier to entry for someone interested in talking about webOS but might not be sure where to begin.  Plus, I plan on releasing a series of articles on how to recruit developers in your community, how to sell the event to sponsors, and share other experience I’ve gathered on how to host a successful conference.  Now that we have a target to shoot for, expect to see a lot more activity on the preDevCamp blog!

What you can do
Some cities are still moving forward with June 13th events, and my personal opinion on this is kudos to you for getting a head start.  There’s a lot of learning to be done in the next few months, so I encourage you to use this time to help create our public knowledge base.  Write a blog post on something you’ve learned.  Record a presentation and upload it to the preDevCamp slideshare groupGet to know other developers and provide feedback for each other.  And don’t forget to keep your city’s preDevCamp blog updated!

Learning as publicly as possible will show the world that the preDevCamp community is leading the way to webOS enlightenment.  Are you ready?  Let’s begin.

Individualizing Social Media with a Personal Information Layer

We’ve leveraged social to the point where there’s a big melting pot of content out there, but how do you make all that data more useful? The next step of social media is to take a step back towards a more personal information layer.

I’ve been thinking a lot lately about the direction of social media and what it means to me, and I’ve found myself uninterested at best. So we share stuff. Big damn deal. There’s so much content being shared to me that I ignore almost all of it now, at least compared to what I was consuming a year ago. No offense to any of my contacts, but I’ve reached the point where enough is enough, and while all that firehose of content is still in my input stream, I’ve altered my patterns to only consume what’s relevant to my interests at that moment.

For example, tweets are skimmed while walking up the stairs (Confession #1: Or when I’m in the restroom. Hey, just being honest), but hundreds of messages may be ignored if I decide to do something more interesting for a weekend. Neglected RSS feeds pile up to the dreaded 1000+ mark. I used to have a level of background stress because I was “behind,” but after learning that I’m no worse off without this information, I now have no regrets using the “mark all as read” button with reckless abandon.

The content’s there, now make it relevant.

While too much content isn’t a bad thing (until you reach the point where you’re so unable to manage it that it becomes easier to ignore), I didn’t bring up the previous rant and confession to focus on content filtering. I think that’s a problem to be solved with some sort of relevancy engine, something that reads in your context, available resources, and attention profile, and feeds you the data that’s most useful to you at that moment. But even that intelligently consumed content can be made much more useful if I have a highly customized layer to help me organize my own meaning for that data.

But there’s bookmarking tools, you might say. And tags. With these tools, you can organize content however you want. To be honest, I could never get started using bookmarking services until just a few months ago when I started using Mento.info, because it has a nice balance between the metadata robustness of a bookmarking service and the relevant content highlighting of a tumblelog. (Confession #2:  the first service was actually ma.gnolia, but only for a few heavily-frequented topics. And all those links are gone now, bless ma.gnolia’s heart.)

Bookmarking services are flexible, but that also means they’re very generic. Their biggest flaw is that even when given the option of clipping content, you’re recording a copy of what someone else said or likes or thinks is useful. What if I like the author’s advice, but find that it doesn’t work for me 100%? Feedback can be shared publicly in comments, but they’re merely a footnote to the original content.

The first step of social media was to make everything public; the next step is to make it more applicable to your individual situation.

I’ve come up with an idea I call a personal information layer. This data layer is a different concept than annotation as found in services like Diigo, where users’ adjustments float like post it notes. The personal information layer should look and interact just like the original content, but customized to the preferences for an individual user. Recipes are a good example. I may like much more sage than the original author called for, or perhaps my oven requires an additional 10 minutes cooking time. The content is way more valuable to me when I can alter it according to my taste and needs.

Remixing is hard enough now. What happens to copyright in an Internet like this?

This question felt a lot easier to deal with when I was trying to keep the data in the personal information layer truly personal (read: private), but it just won’t work that way (Confession #3:  also, I loathe the idea of building another social graph). Even individual adjustments to public content is useful data, so there’s value in sharing it. But this will be harder to defend than deep linking and reblogging…this is making potentially minor changes to someone else’s otherwise verbatim content and collecting it all under your own name. Simultaneously collecting and customizing data is another step towards the ideal Internet, but at what point does Emeril’s pie recipe become Brittany’s pie recipe? What’s the significance if it was Kathy’s version before Brittany saw it?

I can’t predict how the Internet community will respond to any of these challenges; I don’t think anyone can until a demo is released in the wild to see how people react. And of course, I wouldn’t go through the trouble of documenting all these questions and ideas if I didn’t have a hell of a use case I hope Dave and I have time to experiment with over the summer.

Next,

RECENT READERS

RECENT PHOTOS


AFFILIATIONS