{"id":702,"date":"2012-10-23T08:51:01","date_gmt":"2012-10-23T08:51:01","guid":{"rendered":"https:\/\/sparktoro.com\/blog\/?p=702"},"modified":"2012-10-23T08:51:01","modified_gmt":"2012-10-23T08:51:01","slug":"we-can-do-better-than-bitly","status":"publish","type":"post","link":"https:\/\/sparktoro.com\/blog\/we-can-do-better-than-bitly\/","title":{"rendered":"We Can Do Better Than Bit.ly"},"content":{"rendered":"

Of all the tools I use each day on the web, perhaps none frustrates me more than bit.ly. I like being able to track all the sharing I do across networks with a single URL shortener, but the site’s frustrating from numerous levels. Historic data and habit are most of what keeps me from moving to other services (along with a lack of knowledge of better platforms, though awe.sm<\/a> seems worth a shot).<\/p>\n

\"\"<\/p>\n

We can do better than being forced to take multiple, non-intuitive actions to shorten a URL and getting mediocre analytics data in return. A couple weeks back, I complained on Twitter about this<\/a>, and received many replies asking what features I’d want to see. So, tonight, I spent a little bit of time noodling on the subject and mocking up a hyper-simplistic wireframe of something that might work better, at least for me.<\/p>\n

The result of that wireframing process is below, but beware, this is far, far too simplistic and not-thought-through to be a true product. It’s more of a brainstorm with a visual:<\/p>\n

\"\"<\/a><\/p>\n

click for bigger version<\/a><\/p>\n

As you can see, I didn’t even have time to fill out all the datapoints next to the rows, which might make it hard to entirely grasp on a first look. Basically, the big features I want to see are:<\/p>\n