Balloons, or how tech companies need to stop and take stock

Balloons is, concurrently, a ‘fine WordPress theme’ and a ‘whimsical’ one. It is also a theme that caught my attention when I was browsing for WordPress themes recently. Let me be clear – I was not browsing for themes for my own site. I was browsing for themes for our nikhco.in domain, which looks to be in need of a refresh.

But Balloons caught my eye. Why? I’m not sure. Maybe it was the large number of balloons that are front and center at the head of the theme. Maybe it was the oddly small typography, which could look great if it were a few font sizes bigger. But as soon as I saw it, it caught my attention. I started thinking about how I would modify it to suit my needs and change some things I’d definitely get irritated at. I hate when theme authors fixate on certain social network links but not others or add an unneeded sidebar to the theme. But then, I stopped and took a step back.

This planning and plotting I was up to, was it needed? Was it a useful change to my site? Was this theme better than my current theme? I have put many hours into editing my current theme, “Independent Publisher”, to make it look the way I wanted it to look. So should I be putting those same hours again, so soon, into a completely new theme with completely new issues I’d have to fix? I like the challenge, but is the effort valuable? Have I received negative feedback on my theme? Has someone told me that it’s not good the way it looks or maybe it fundamentally conflicts with the content? I write on a variety of subjects – code, fiction, politics, observations about the world, and movie reviews, among others. So it’s been hard to find a theme that fits all that content. Thus, over the years, I’ve experimented with many themes, many plugins and formats to elicit some kind of a reaction from my otherwise passive readership.

I was talking to my brother recently and we were talking about how LinkedIn has the habit of trying new things with their site. I understand the impulse. It’s all about constantly evolving. You have a product, you want to make it better. There’s also the business case for it. For startups and fledgling companies alike, there’s a market to capture and industries to disrupt. Thus, the need for experimentation drives them to keep trying to do new things. If a company working on a professional social network can also act as a Rolodex and be the go-to resource for industry news, that’s better for their business.

But my brother’s point was valid too – you’ve got a product. You’ve released it to the general public. You’re working on minor improvements all the time. Let. it. sit.

There’s oftentimes no need to add that new feature to your current site. If you want to experiment, make a separate platform or a new app to try things. Put it under your label, call it “LinkedIn Connect” or “Facebook Paper”. But don’t try to shove new ideas down the throats of your current users. Let them get used to the current system. Let them complain and argue the merits and demerits of it. Let them give you real feedback and then act on it. At the end of the cycle, if the new idea is that popular, roll it into your current system. Integrate your changes. But don’t start out with the assumption that people will be OK with a constantly changing platform. Most of the time, there’s no need for that.

We talked about all the other companies out there too, including giants such as Google, Cisco and HP. Those who sit on their laurels get surprised by a leaner, smarter company coming along to steal their market share. But those who continually reinvent just to keep the rust off, lose their focus and their customers. If you’ve got a radical improvement to your product, go for it. But make sure you’ve got a second set of eyes telling you that the new is actually better than the old, not just newer than the old.

So, as I looked at Balloons, I silently sighed. There was no need for it. No one is telling me that my tech posts look bad in the new theme. My most popular post ever “Installing Fever on AppFog” still gets visited a few times a week even though it’s years old now. People still read through it on a theme that’s better suited to fiction than tech tutorials and no one seems to mind. Older posts about code are still visited and no one cares if the font is larger than needed.

I bookmarked the theme and closed the tab. One day perhaps, I’ll dust it off and show it to someone and ask if it would make for a better theme for my blog. Until then, my site looks good and I’ve decided what to do with it – Let. It. Sit.


Authors Note – I wrote and edited this post on Hemingwayapp. It’s an amazing editor. It points out sentences that are hard to read, phrases that can be simpler, and the use of adverbs and passive voice. It helped me get rid of all the instances of passive voice in this text. The makers, the Long brothers, have come up with a new Beta version that you should check out. The New Yorker has taken notice of the app too, among other news media. You can read about their coverage here. This article got a grade of 6 on the app, which is not at all bad!

What Facebook needs to do next

Update: Facebook has done it! It has finally created a messenger standalone for the web. You can go here to check it out (here if that doesn’t let you login) or here to read about it (but why would you?). Cheers!

Facebook has changed a lot over the past few years. There have been acquisitions, newsfeed, design changes and rollbacks and a whole mess of things. Facebook obviously understands that the future is mobile (hence WhatsApp and Instagram) and that people are moving in all kinds of directions, towards private spaces (hence the separate Messages app) and public posts (hence hashtags and the searchability of your FB post that goes with those).

So what’s next? Well, today, I wanted to send a link to my brother. Since I’m on Windows right now and not on my Mac (I usually just iMessage links to him), I fired up Facebook and sent it to him in a message. Why? Because it’s convenient, because Facebook detects the OpenGraph information about the page and processes it to make a neat link+image combo and because we have many conversations on there anyways.

Why didn’t I send it to him as a directed Facebook post? I could have, but I didn’t care enough to make it public. Our Facebook activity is not our true selves but a reflection of what we want to portray to others, and this link didn’t necessarily fit into any paradigm of my public self. (In other words, it wasn’t epic. Publicly shared links must be epic.)

Why didn’t I send it to him in an email? Hush, don’t ask silly questions.

But then, I wanted to send him another link and another. So what did I do? I clicked on that miserably little link that takes me to Facebook’s dedicated messages page so that I could share links and have conversations in a larger space than that goofy little box that occupies the bottom right corner of my screen.

That’s when it hit me. Facebook has a beautiful Messages app on the iPhone. I’ve sung praises of it before. But there’s a curious lack of a well designed web interface for messages. The old and clunky interface that sits there now has been sitting untouched since a long time.

Now, you’d argue that another private space that I could have used was the Facebook Groups feature. It looks nice, it’s often updated and has the same look-and-feel as the rest of Facebook. But why would I create a group for just myself and my brother? There’s no need for that since /messages exists. The only thing needed is to build a nice looking private messages space that people would use.

I was really tempted, as I started writing this post, to build this webapp myself. Facebook’s API is open and easy to work with. I’m sure I could have found many plugins and libraries to make the task easier for me. But any such project can never be feature complete. I can build it and you can come, but you’ll never stay because of lack of features, because a single guy sitting with a laptop with a limited amount of time can only do so much.

So Facebook, here’s the next thing you need to do – make messenger.com what it really should be – a full-fledged webapp that’s as classy as any other public facing feature of Facebook. I hope to see it soon!

License, don’t acquire

Silicon Valley has a bad habit – that of buying outright any company that might prove useful to them and the tech community. When Google bought Waze, Facebook bought Spool and Pinterest bought Icebergs, they all did it to bring to their platforms, users and companies, ideas, technologies and features that they believed would be a good fit with their own setup.

But they did it wrong. Waze is a great app and when it finally disappears (as do all Google acquisitions), it will be a great loss for it’s users. Waze has a unique UI, a dedicated user following and features that are not at all present in Google Maps. While the integration went well, Google Maps is an overloaded app with too many features. Eventually, they’ll simplify and drop a few features, getting rid of many core things that Waze is known for. In no circumstance will Waze ever recover from this setback.

Continue reading

Well, what about the jailbreak?

iOS8 is here today and as I always do before an iOS update, it’s time to audit my jailbreak. Of late, I’ve grown distant from the jailbreak idea as such. I still have a jailbroken iPhone 4S and iPad Mini 1, but there’s barely much happening there.

RAM? What’s that?

The first problem with my jailbreak is that it’s on a device that’s now, well, old. The iPhone 4S has 512 MB of RAM and as much as Apple fanboys will tell you that you don’t need RAM because Apple has a) tight integration with their hardware or b) amazing tricks up their sleeves that put apps to ‘sleep’ as soon as you minimize them, the truth is that if you jailbreak, you need RAM. Continue reading

A response to Marco Arment about ADN Freemium

Today, App.net (ADN), the social network that made me drop all others made an important announcement – that it is going to allow free accounts that are invited by currently paying members. I did not intend on writing a blog post about it because this is news that has already spread through wildfire in the tech community. Some have lauded and some criticized it. But the post that made me write is this commentary by Marco Arment.

Marco argues that while such news is welcome, ADN needs to do more to promote user growth instead of focusing on developing the API. He goes on to state that the main reason people are signing up is the twitter like functionality sans the spam and advertisements and instead of building file storage APIs, the team should develop spam protection and open the gates completely to free members. Continue reading