opinion

Wibbly-Wobbly Apple

There has been a lot of news lately about Apple reversing course with various apps using  extensions and widgets in iOS 8. At WWDC a few months ago Apple (or more precisely the engineering branch of Apple) announced a lot of new toys they'd thrown in iOS 8 to make it easier for developers to extend the experience of their apps to notification center, other applications, and cloud based storage. To me, and a lot of other people, it felt like exactly what iOS needed. 

Then a group of smart developers started building things with these new tools We got Today View widgets that could open apps, calculate a tip, and otherwise increase the functionality of our iThingies. More developers dug in on the cloud accessibility with, perhaps one of the best new apps being Panic's Transmit which gave us the ability to move files between different cloud services at will.

Apple approved these apps, put them up for sale, and, in some cases, even featured them. We paid money for the apps and now a bunch of them are being required to remove the innovative features we bought them for at risk of being pulled from the App Store.

So how did Apple get so bi-polar on extensibility in iOS? I'd argue they've always had warring factions over this issue but the battles have always been behind closed doors in Cupertino. Now it's public. Now we actually see some really great functionality only to have the carpet yanked from under us. If Microsoft or Google were changing its mind publicly like this, all of us Apple geeks would be giggling about it.

There is no doubt in my mind who should win. I think the extensions mentioned above only make iOS better. They are all in applications that users must download and extensions that users must enable. I can't see how the "this will confuse users" argument holds any weight since these all require action by the user to enable. If I found myself sitting at Tim Cook's desk, I'd say let them through. I'm sure developers are taking the iOS 8 tools to places the iOS development team didn't anticipate. However, I think this is something to celebrate, not restrict.

There is a separate, equally troubling question arising from all of this. How is this all happening in public? Regardless of whether or not Apple agrees with me about what developers can and can't do, somebody needs to decide, predictable standards should be identified, and we should move on. Let's hope the days of wibbly-wobbly changes like this are nearly over.

Multiple Variables

One of the great things about last year’s iPad release was the device parity Apple brought to both devices. They both had retina screens. They both and the same camera. They both had the same processor. They both had the same memory. All of this resulted in much easier consumer decisions when choosing between them. Do you want the big screen or the little one?

If the rumor sites are to be believed, this won’t be the case with the two different sized iPhones we are expected to see next week. Not only will screen size be different but we may also have differences in camera quality. I would speculate that differences in display quality, battery life, and storage could also easily be in play. Assuming that the bigger phone does get some of the better components, what do the people who want a smaller screen with the better components do? They have to make tough choices. I suspect much digital ink will be sacrificed in relation to this question in the coming weeks.

Broadwell and ARM Macs

wrote last month about Broadwell’s delays and the expected impact on the release of new Macs. It appears that is coming true. The recently updated MacBook Pros just received slightly bumped Haswell chips and, as Macworld reports, the speed improvements are small.

Moreover, I’m more convinced than ever that the rumored 12" MacBook Air with retina screen, assuming it exists, will get pushed back until next year when Apple can get the Broadwell chips it needs to put a retina screen in a small MacBook. If Apple were to release a Haswell-based MacBook Air with retina screen, I’d recommend waiting.

There is also more buzz about the idea of an ARM-based Mac. The ARM chips that currently power iOS devices are Apple designed and Apple controlled. If Apple could put those in Macs, they wouldn’t be dependent on Intel for future Mac releases and wouldn’t get saddled with the problems they have with the current Broadwell delays.

The problem is that ARM chips aren’t nearly as powerful as these Intel chips and it would incur a substantial performance hit. Another downside of ARM Macs would be that they don’t run Windows nearly as easily as Intel based Macs do. (However, I have to wonder how important that is as we increasingly move to web-based services and Windows becomes less relevant.)

On the plus side, ARM based Macs would have ridiculously great battery life. When you think about it, a thin, light Mac that sucks at Final Cut but runs Safari and Mail for 24 hours on a single charge may have a pretty large audience. If Apple were to go this route, I suspect that initially they would keep producing high-end Intel Macs for people that need the power.

Yesterday, Jean-Louis Gassée (who knows more about this stuff in his pinky finger than I do in my entire body) wrote that he believes an ARM based Mac may very well lie in the not so distant future. One of the points he made that hadn’t occurred to me is that since Apple is designing the chips, they could create a separate ARM design for the Mac that is a bit more powerful and uses a bit more power. Pound-for-pound though, I suspect Apple would have a hard time matching Intel on the power end, especially now that the Broadwell chip is on a 14nm dye.

Could something like this be already in the works at Apple? To answer that question I’d state that just a few months ago Apple announced an entirely new programming language for the Mac and iOS that they’d been internally developing for years and nobody on the outside had a clue of its existence.

In Defense of Tim

Dan Frommer has a nice piece up about Tim Cook.

"In many ways, Cook is running Apple better than Jobs ever did."

I think anyone following Steve Jobs has the deck stacked against him. Nevertheless, looking at all the news from WWDC, I also think Tim Cook is the right guy to follow Steve Jobs. If you think Tim is under heat now, just wait until Apple actually releases a watch or fitness band. That market is much smaller than the iPhone market. Even a product pitched by Steve Jobs with his reality distortion field turned up to full power is not going to touch iPhone numbers. When this inevitably happens, all the long knives will come out for Tim in the tech press.

Efficiency vs. Delight

I've been thinking a lot lately about the role of delight in application design and how it relates to (and sometimes trumps) efficiency. I wrote a small piece about this and Macworld published it today.

The Next Thing and Low Hanging Fruit

I read this Wall Street Journal article where Tim Cook explained that Apple is approaching releasing a product in a new category. There is one line in the story that explains “Cook knows that’s the biggest question hanging over the company: whether it can repeat the innovative success with a new product category – as it did with the iPhone in 2007 and iPad in 2010.” Somehow it’s become a thing that if Apple can’t release something equivalent to the iPhone and iPad, it’s doomed. Oddly (or perhaps sanely), nobody says that about any other company.

I’m sure Apple does have some new product categories up its sleeve but I also seriously doubt any of them will be as successful as the iPhone. Everybody needs a phone. Not everyone needs a watch, fitness tracker, or iJockstrap. The iPhone represents an expensive and frequently replaced bit of technology that we all need to get around. There isn’t anything else like that. Nevertheless, Apple will start expanding into these lesser categories and people will look at the numbers and say, “See … Apple is doomed without Steve.”

It seems to me that with phones and tablets, Apple has already taken the low hanging fruit. I don’t think there is another category of personal electronics at this stage of the game that everyone will want or need. I’m sure Apple’s new products will be great and will enhance the overall experience but I’d be shocked if they were iPhone/iPad levels of success. I don’t think it matters whether Tim Cook or Steve Jobs were in charge, I just don’t think such a product category exists right now.

The Problems You Don't Know

I’ve been running pretty hard the last few months between the day job and finishing up the Email Field Guide. In the process, I’ve fallen off the wagon a few times with my OmniFocus task management discipline. Everybody probably knows that feeling of seeing the red badge of “Overdue” show up on the icon and know that it has been several days since you opened up the application and sorted through things. You know there is ticking bomb under your kitchen table and part of you would rather pretend it’s not there and keep eating Cheeze-Its.

I’m here to tell you to put down the box of delicious cheese-flavored crackers and instead cut the red wire. If you are using some of the tricks I showed in my OmniFocus Screencasts, it will not take that long to quickly get through your task list. Even if that means pushing 95% of your tasks off until next Monday, that 5% left is manageable and just think how much more time and money it will cost to rebuild your kitchen if you let that bomb go off.

Here is how I did it under fire the last few weeks.

Screenshot 2013-11-21 14.02.13.png

1. Enable A Clear Perspective

I have a special perspective to help me sweep the decks. It removes all project distinctions and instead just gives me a long list of all active tasks. This makes it really easy to grab big fat chunks of them using the shift or command keys while selecting.

Screenshot 2013-11-21 14.02.28.png

2. Use the Inspector to Process Multiple Tasks

On the Mac version of OmniFocus, open up the inspector and move the start date to some safe date in the future for large swathes of your selected task backlog. Set a record for how many you move with one selection.

3. Defuse the Bombs

There will be a few important things left. Deal with those and get back to the big project that put you behind in the first place. Remember, this too shall pass.

The thing is there are the problems you know and the problems you don’t know. It is the ones you don’t know that will get you every damn time.

Trucks and Cars

In 2010, Steve Jobs made the analogy between PCs and mobile devices with the original trucks and cars. He explained that when we were an agrarian nation and automobiles were new, everybody wanted a truck. Automobiles were expensive things and you only bought one if you needed it to do heavy work. That, however, was temporary. Eventually, people began buying cars and before you knew it most people bought cars.

As the analogy goes, the desktop PCs are the trucks and the emerging classes of tablets and pocket computing devices, such as iPhones, are the cars. When he made the analogy, it made a lot of sense to me but I felt like it was still something pretty distant into the future. I don’t think that’s the case anymore. Looking at my new iPhone, it has a 64 bit processor and is more powerful than anything I could’ve imagined just a few years ago. Moreover, software developers are getting smarter about ways to implement these touch devices in a way that’s quick, efficient, and just better than a traditional PC. (Don’t believe me? Check out Editorial.) I don’t think the desktop Mac is going away but I do feel the swing as more people decide their phones and tablets are “enough”.

This was brought home for me today with some reporting by Horac Dediu. Including iOS and Android devices with traditional computers, in Q3 2008, there were 92 million units shipped, 90% of which were running Windows. Jumping to Q3 2013, using the same devices, there were 269 million units shipped of which Windows was 32%. There were more traditional computer shipped in 2008 than in 2013. You don’t even need fancy statistics to verify this. Just look around you, and you’ll find several people that get by just fine with a mobile device alone.

I’m not saying that laptops and desktop computers are going to go away entirely. There’s a big group of people that are always going to want that kind of power, including me. However, the shift from trucks to cars is in full swing and as the mobile devices get even better hardware and smarter software, this is going to become even more obvious.

Scummy App Copycats

I cannot understate how repulsive I find the actions reported in this Ars Technica article. An App Developer made a successful photo app called "A Beautiful Mess". The app was successful and then a group of copycats began submitting confusingly similar apps with names like "A Beautiful Mess Free" and "A Beautiful Mess +". In some instances, the copycats used identical icons and screenshots. The article opines how some developers will even grab the code from the original app and reverse engineer it. How does Apple not see what is going on here? If I submitted an app called "Logic Pro X Free" do you think it would get approved?  When someone so blatantly rips off another developer, Apple shouldn't only reject the app, they should also ban the developer. There simply is no excuse.

The tragedy is that with the approval process Apple has the ability to stop this practice in its tracks. Indeed, Apple is the only app store that can do this since it is the only one requiring approval.  As a community we need to put as much light on this as possible so, in addition to looking for malicious code, Apple also starts looking for (and banning) scummy developers. 

 

Apple's Enemies

I'm 100% on board with Brent Simmons' post at Macworld yesterday.

"Instead, Apple’s enemy is Apple itself. It must attract and retain talent. It needs to get strong where it’s weak—particularly with syncing and online services.

It needs to retain that awesome balance between cautious incremental updates and the occasional, mind-blowing new.

It’s not easy. But nobody does it better than Apple."

I tried to make a similar point in my Macworld article about the culture of fear in the Apple community. We are not going back to a world where one platform gets 96% of the market share. We no longer need to be worried about our beloved fruit company shuttering its doors. It is now up to Apple to continue to deliver.

The RSS Apocalypse

Aldo Coresi explains:

"The truth is this: Google destroyed the RSS feed reader ecosystem with a subsidized product, stifling its competitors and killing innovation. It then neglected Google Reader itself for years, after it had effectively become the only player. Today it does further damage by buggering up the already beleaguered links between publishers and readers. It would have been better for the Internet if Reader had never been at all."

I spent most of today in meetings. As a result, I didn't have time to fiddle in Twitter or check in on the web. It was the kind of day where I knew I could catch up on the day's news the way I do most busy days, through RSS. So you can imagine my suprise as I drove home today chatting with Katie Floyd on the phone and she tells me Google is uplugging Reader.

I remember back when RSS was amazing and something you paid for. I also remember when Google Reader showed up and very quickly started taking over. It was free. It was Google (back before we were all scared of Google) and it wrecked the market for all of the paid RSS services. We all wondered how Google monetized its Reader expense but we wonder that about most Google services so we all cancelled our paid services and leapt.

Now Google is yanking the cord. Since Reader is the Google service I use the most, that made me a bit sad but I didn't see it as the end of the world. I'm sure some enterprising folks have already filled the whiteboard and are spitballing ideas for the next great RSS reader service. Within a month competitors will be on the market and I'll switch. It will probably cost a few bucks but they won't be collecting data on me or selling to advertisers. (At least not the RSS service I evenutally choose won't.) In other words, with Google exiting, the free market will take over. So my initial reaction was, "meh" and even a bit of enthusiasm that with paid RSS, people may start innovating again.

Then I got home and my wife was really upset about it. My wife is a bit of a nerd too but she travels in circles of electronically connected paper-crafters and they are absolutely up in arms about this. To them, Google Reader is RSS. They don't know of alternative services and as far as they know, new services will never again exist. They think RSS is going to die on July 1 and that's that. Now some of them will figure out they can go elsewhere but some won't. Those people will stop reading blogs via RSS and those blogs will lose readers.

That got me thinking. I've spent years building up MacSparky.com. There are thousands of RSS subscribers. How many will bother to sort out a new RSS system and subscribe again? The closing of Google Reader is going to result in the great RSS purge of 2013. Then Brett Terpstra tweeted this article by Aldo Cortesi which sums it all up in the above cited paragraph better than I ever could. This whole mess is just another example of why free is so often bad.

$329

I've been thinking about all the hullabaloo over the price of the new iPad mini. Everybody feels that Apple blew it by not getting the price down to something competitive with Google and Amazon. Upon reflection, this really doesn't surprise me. Both Google and Amazon have stated that they are selling their small plastic-based tablet products essentially at cost in order to get market share. They have a problem. Apple is beating their pants off in the tablet market and they need a toehold. Apple enthusiasts are eager for Apple to stifle the competition by making a superior iPad mini at roughly the same price. As they see it, Apple has its boot on Google and Amazon's neck and needs only to push to own all aspects of the tablet market for the foreseeable future.

Apple however does not play that game. Apple likes to make money. I can't really fault it for that. The iPad mini starts at $329. the Google Nexus device starts at $199. That Google device only has 8 GB of storage whereas the iPad mini has 16 GB. To get a Google Nexus tablet at 16 GB, you need to spend $250, $79 less than the iPad mini.

So a fair comparison is the $250 Google Nexus device versus the $329 iPad. What does that extra $79 get you? For starters, the iPad mini is better designed and built. I'll take aluminum over plastic any day of the week. Additionally, the iPad mini is an iPad in all senses of the word. It runs, natively, all of the excellent iPad software. The Android tablet software is not there yet. (That thing I wrote about Android apps nearly a year ago still stands.)

When I was on the Mac Roundtable this week, I made the comment that this device isn't necessarily aimed at us nerds. We all love our large-screen iPads with retina displays and a lot of us don't see a good reason to go to the smaller device. That's okay. Apple already has our money. I suspect that the market for the iPad mini is probably less nerd-inclined than that of the larger iPad. The iPad mini is aimed at people who want a quality smaller tablet device. Apple thinks there are a lot of people willing to shell out an extra few bucks for such a device and I suspect they are correct. All of this said, I agree that if they were able to hit $299 instead of $329, a lot more people would have gotten past the price barrier but Apple is a very successful company and I'm sure people much smarter than I already did that math and the iPad mini will do just fine at $329.

The real interesting part of all of this discussion is the collective concern of Apple enthusiasts over Apple blowing it. All of us remember the times when Apple was nearly on the chopping block and there's this sort of cultural fear that somehow our beloved company is to stop making our beloved products. As a result, we all wring our hands and rend our garments in fear every time Apple makes a big move. Moreover, when we see any other company being remotely successful in the same space as Apple, a small part of our brains think it is Microsoft Windows all over again. The good news, my brothers and sisters, is that those days are over. There is not going to be a single winner like there was for the Mac vs. Windows days this time. (Not even Apple.) Apple gets that and is more than happy to let others fight over the low margin end of the market and gobble up the high-end of the market where Apple can actually make a profit and, therefore, keep the lights on.

Jason Snell said it best in this week's Macworld podcast, "Is there a cheap tablet market or is there a small tablet market?" I think the latter and so does Apple. I'll also go out on a limb and say that, with the iPad mini's sales starting tonight at midnight, they'll be sold out before I wake tomorrow.

About this Apple Publishing Lawsuit ▻

Senator Charles Schumer (D-NY)wrote an editorial for the Wall Street Journal about the US Department of Justice's lawsuit against Apple over book-selling practices. I'm sure there must be some explanation for this lawsuit but it eludes me.

As I understand things:

  1. Amazon had a chokehold on digital distribution and was gleefully ramming it down the publishers' throats.

  2. Apple, and others, entered the market and gave publishers more control over how they sold their books.

If anything, it seems that Amazon is the one being anti-competitive. It looks like Senator Schumer agrees with me.

Degrees of "Free"

In this week’s episode of Build & Analyze, Marco Arment explains the challenges of competing with free. At some point over the last few years I’ve migrated away from free services for anything I consider essential. I’d like to say this was calculated but this shift took place at a subconsious level. This shift has two reasons:

  1. No Monetization = Temporary
    I don’t want to waste my time in something temporary. I’ve been burned too many times over the years investing my time and effort learning a free service or app that disappears with little or no warning. If something is good, I want it to stick around and I understand that requires money.

  2. Free is Not Free
    While some apps are free downloads, they are rarely “free”. I end up paying with intrusive ads or information about myself. I’d much rather pay a few dollars to begin with. In my book, that is much cheaper.

Applying this to Instapaper, not only did I pay for the app on my iPhone and iPad, I also am a subscriber and pay $1 per month for this ridiculously useful service that I use every day.

Sandboxing and the Mac App Store

As I met with developer friends at Macworld this year, a common discussion point was Apple’s forthcoming implementation of sandboxing on the Mac. As part of the continuing effort to keep the Mac secure, Apple is preparing to require that all apps sold through the Mac App Store comply with Apple’s sandboxing rules. Sandboxing in Mac OS X is the process of requiring apps to obtain permission for access to different parts of your Mac’s memory and file system. For instance, if you are create a text editor app, you shouldn’t need access to the Mac’s Address Book database. Indeed, making an app that seems harmless but then grabs and uploads personal information and data is exactly the kind of behavior Apple seeks to prevent. In essence, sandboxing partitions the different areas of your Mac only giving software developers access to those particular assets their apps reasonably require. A photo editing app, for instance, will not get access to your admin files. A calculator will not get access to your documents folder. I’m simplifying, but you get the point.

As such, Apple is adding sandboxing to Mac OS X. Sandboxing makes a lot of sense. It worked out really well for iOS and now Apple wants the same level of security on the Mac. However, there still are a lot of questions. For instance, what about apps that necessarily need to work across your Mac? Macro applications and text expansion tools work within several apps and, by their very nature, need access throughout your system in order to serve you. Likewise, some of our favorite productivity apps use small menu bar apps to provide an ever-present gateway into their functionality. Another example are FTP clients that allow you to upload files from anywhere in your computer. All of these applications are incredibly useful. Unfortunately, it also appears that all of these applications would violate of Apple’s looming sandboxing rules.

Nothing is in stone yet. The policy hasn’t been made final or implemented. However, the writing is on the wall and longtime Mac app developers are concerned. Is Apple’s efforts to implement sandboxing going to kill their apps? Nobody knows: everyone is worried.

At some point, Apple is going to throw the switch and start vetting all apps submitted for sale in the Mac App Store. Apps that don’t meet the sandboxing standards, it appears, will not be sold through the Mac App Store. This is a serious problem for app developers as users become more and more accustomed to buying their applications exclusively through the Mac App Store. (I buy nearly all of my apps there.) Moreover, it is not beyond the realm of possibility that one day the only way you can buy an app will be through the Mac App Store.

Sandboxing was originally set to begin in November, 2011. As both Apple and developers struggled to understand exactly what this meant, the deadline was pushed back further. Frankly, having talked to several developers, it seems like there is still a lot of confusion over sandboxing and, in my opinion, this should get pushed back to the next major Mac OS X release, 10.8.

While I have no objection to the idea of sandboxing on the Mac, I hope that Apple doesn’t throw out the baby with the bathwater. From the outside, it appears that the Apple steamroller is gassing up and a lot of our favorite apps are sitting in its path. I believe there is a middle path here. Sandboxing can work if Apple is willing to consider being reasonable with apps that necessarily require broad access to your Mac, particularly from established developers. Maybe the reason this keeps getting delayed is because Apple is internally figuring out how to make that happen. Regardless, I can report that many developers are agitated about the possibility of sandboxing rolling them over in the future. I can only hope Apple will use enough foresight to keep that from happening. It would be a shame if we lost some of our favorite apps in this effort to make the platform more secure.

So as users what does all of this mean for us right now? It is hard to say. We could be looking at a serious threat to some of our favorite software or we could be tilting at windmills. Hopefully it is the latter not the former. In the meantime, as a software purchaser, this causes me to pause with respect to purchasing applications in the Mac App Store. While generally I’m a big fan of the Mac App Store, when it comes to apps that could potentially tread on the sandboxing rules, I’m hesitant. My concern is that they will eventually be banned from the Mac App Store, and any licenses I purchased there will no longer be available to me. As a result, if it’s an app that may run afoul of these new rules, buy it from the developer directly for now. Maybe in six months this will work out and not be a problem, but why take the risk?

The Android App Store Problem

Eric Schmidt predicts that in six months, iOS developers will be flocking to Android, even if they don’t like it. Ummm, think again.

Android’s marketshare continues to climb and that is presumably a good thing for Android but mere numbers does not create a vibrant app market. There need to be two pieces for a successful platform app store: 1. a trustworthy store, and 2. customers. Android has neither of these.

The Theoretical Android App Store

While there are no shortage of issues with Apple’s own App Store, there are a few things it really nails. Apple provides a safe and easy environment to deliver apps and seperate customers from their money. This is where Android misses the boat. If Google wants to attract developers, they shouldn’t worry so much about marketshare and instead focus on getting a reliable payment system and an app purchase environment where customers aren’t constantly getting stiffed. Amazon seems to be making the best efforts to fix this but there are some truly legendary stories about what a spectacular job they are doing screwing it up. With so many different form factors, screen sizes, and system specs, it is going to be a lot harder for Google (or somebody) to deliver the iOS App Store experience on Android.

“Free is Better! Hooray!”

Android owners don’t buy apps. With very few exceptions, every Android owner I’ve talked to is only interested in free apps. To hell with the user interface. Put ads everywhere. Just don’t charge any money. (Perhaps all of the on-screen ads explains the arms race of larger screen sizes.) I don’t mean this as some sort of character attack against Android owners, many of whom are very nice people. I just think that, for whatever reason, Android users are not interested in paying for mobile apps. I’ve been talking to Android and iOS owners about this for years and the theme is consistent. iOS owners buy lots of apps: Android owners don’t.

I don’t know if it is a lack of trust in the payment system or simply a culture of “free” but ask your Android toting friends how many apps they’ve purchased and the answer will be few, if any. The short of it is that Android devices could multiply like locusts but if people don’t buy apps for them, developers will stay away.

Multi-Platform is a Feature

Maybe this is obvious but as iCloud rolls out, users are going to add a new criteria to their app buying calculus. “Is it multi-platform?”

Just like the way even us ‘power users’ are getting hooked on Lion’s versioning and auto-saves, even the most die-hard Dropbox supporters are going to find themselves expecting data to migrate between their Macs, iPads, iPhones, and even Windows PCs.

With iCloud, there is no secret incantation, retina scan, or hacking involved. Your data just is. No longer will you have to consider whether the right folder is synced to the right app. Work on one device. Turn it off. Work on another device and pick up where you left off.

There is a price to brain dead syncing. From everything I’ve seen, in order to work, you’ve got to be working on the same app on every platform.

For the first time since the iOS arrived in our lives, using the same app on multiple platforms comes with an added benefit, data bliss. When users look at apps for their Mac or iOS devices, they are going to actively seek those with support on other platforms. Automatic data-syncing is a huge benefit and multi-platform is going to be a big deal for enlightened Mac and iOS developers.

Already there are some text editors supporting both iOS and Mac OS X. I think this will spill over into most productivity apps: PDF apps, outliners, mind mappers, graphics apps, and any app with a user generated data file. Expect to see a lot of familiar apps on unfamiliar platforms soon.

Juggling

In episode 23 of Back to Work, my friend Dan Benjamin argued it is not possible to do two things really well at the same time. Specifically, Dan explained that there simply aren’t enough hours in the day to seriously pursue two different big things. He used the example of starting an iOS app business while holding a day job. Dan made a good case that the attempt to do two things well results in you sucking at both.

Ouch.

I’m doing a lot of things at once. Am I torpedoing myself? Dan’s argument led to some soul searching about what I’ve been up to lately. I simultaneously agreed and disagreed with Dan throughout the show. At one point Merlin Mann used me as an example. I practice law by day and write technology by night. Dan explained that I didn’t count because I’m not a, “normal human.” That’s the one part that Dan got wrong. I’m very human and this stuff is really hard.

A Very Regular Human Indeed

I laugh when someone refers to me as a productivity guru. I am a mess. My mother chose well when she named me David. I spend my weekdays in the trenches with my clients against a seemingly endless stream of Goliaths. I spend my free time (the weeknights and weekends Dan was talking about) writing for MacSparky and podcasting with the Mac Power Users. Add to this my family, friends, and other social commitments and I quickly find I don’t have just two things. I have six or seven. That is my normal juggling routine. Now add to this the spinning chainsaw that is a 25 chapter book, due in just a little over a month, and you can see how I am well and truly screwed. Or at least it would seem. The thing is, right now I am having more fun than ever.

Saying No

Saying “no” is something I’ve only recently figured out but, like a religious convert, I’m exercising this particular muscle plenty. If you want to juggle, you have to learn to say no. Even jugglers have their limits. There are degrees of difficulty in saying no. Television and video games are the easy ones. The day I decided to stop responding to every MacSparky e-mail was a tough “no”. (I still read everything you send me.) It gets even harder when you turn down opportunities. In the past six months I’ve turned down some great opportunities including writing for some really smart people, sitting on an American Bar Association planning board, and expanding my career. I don’t have any regrets with any of those, but they weren’t easy. The real corker, however, is saying no to your family and friends. That is a fourth degree no. This stuff is hard.

The key to it all for me is balance. I try my very best to give the things and people I love attention and accept that it is not possible for me to be all things to all people at any one time. I’m also not too hard on myself. I do my best and try each day to get a little better.

Where Dan’s words ring true for me is this very month as I push to complete a book. It is this extra commitment with the obscene amounts of extra time it requires that I get Dan. Now things are nuts. The next month is going to requires me to say no to some things I’d rather not. It is a temporary thing and will pass soon enough. If every month was like this one, though, I’d fall apart, just as Dan predicts.

Big and Small Touches

Wouldn’t it be great though if I could constantly juggle all of this? If I could run a law practice, blog, podcast, speak, and write books and not go insane? That would make me awesome with my very own superpower. That, however, would also be bullshit.

Writing the book is my edge case. Normally I seem to get by just fine with the law practice and MacSparky. I think, for me at least, this juggling act isn’t a super power but instead a selfish thing. I really like everything I do right now and I’m addicted to the big and small touches.

Just looking at my law/MacSparky juggle, I see these two things scratching very different itches.

I became a lawyer because I enjoy helping people. Stop laughing. You’d be surprised how many lawyers find themselves in this profession for exactly the same reason. People come to me with some really big problems. My clients need help and I can make the difference between pulling out of a nose dive and making a big smoking hole in the ground. My work as a lawyer has a major impact on their lives. Those are my big touches

MacSparky, on the other hand, leads to many small touches. I get e-mails from people all over the world explaining how some little thing I posted or said made their lives better. I love those small touches. When the Mac at Work book shipped, I received an e-mail from a single mom who explained how she used a bunch of my workflows from the book to shorten her work day, saving her about 10 hours a week (500 hours a year) for more time with her daughter. When I wonder why I’m working so hard on this next book and saying “no” so often, that e-mail is why. Both the big and small touches that mean a lot for me.

Dan is Right

Despite all of the above yammering, Dan is right. You really can’t give two things everything. The trick in all of this is finding that tipping point when outside interests go from being simply a hobby or dabbling into the pedal-to-the-metal Next Big Thing. Recognizing that moment and having the guts to jump on it is key. That is what I think Dan was talking about and he is absolutely right. My only qualification is that this idea of just one thing shouldn’t prevent you from dabbling and hobbies. You never know where those things might lead. (I think Dan would agree with me on this.)

Since I’ve accepted Dan’s argument, I’m agreeing that if I did just law, or just wrote about technology, or just podcasted, I’d no doubt be able to commit more energy and be better at the one thing. However, I’m still not interested in picking just one. Maybe I’m too gutless to jump but I don’t think that is the case.

Emerging from this rabbit hole, I realize that at this point in my life, I couldn’t imagine myself giving up the big touches or the little touches. I’m not willing to jump on just one thing because I’m enjoying several things way too much. My life is more enriching now because of all the things I do. In other words, I intend to continue juggling.

The Lodsys Lawsuit and Apple's Opportunity

So Lodsys made good on its threat. This really isn’t surprising. They sent the demand letter and now they’ve filed suit.

Lawsuits are filed every day. Crooks sue homeowners for tripping over the sprinkler when breaking in. Crazy stuff happens. All you need to file a lawsuit is a few pieces of paper and the filing fee. The trick, as Lodsys will discover, is proving your case.

I view these lawsuits as a crossroads for Apple. They could parachute in and protect their developers or they could abandon them as they enter the meat grinder that is patent litigation.

It seems to me that there really is only one choice for Apple, to step in and defend. There are a lot of reasons for this starting with the most important, it is in Apple’s own best interest. If Apple lets developers get sued for using Apple’s API’s, developers are going to to go elsewhere. Gold rush or not, nobody wants to get sued. While I’m sure the developer agreement has some draconian terms that say Apple has no responsibility, I don’t think Apple is going to leave these developers hanging out this way.

While the cost of patent litigation is truly daunting, Apple has the money and is already well lawyered-up. None of these defendants are in a position to defend themselves as well as Apple could.

Finally, stepping in is a huge win for Apple on the public relations front. Developers will see that and the iOS will benefit. If Apple were to take the other route and and leave the developers on their own to deal with this litigation, the exact opposite would happen.

As I’ve said before, I don’t possess a lick of knowledge about how to run a patent case but I have seen first hand the way litigation kills small companies. I suspect that in the next 30 days, the lid will come off and we will find out how far Apple is willing to go for its developers. For everyone’s sake (including Apple) I hope it is a long way.

MacSparky.com is sponsored by Bee Docs Timeline 3D. Make a timeline presentation with your Mac.