Some Of The Worst Start-up Advice I’ve Ever Read

The irony is this comes on the heels of my talk Monday at Mobile Portland (video and slides coming soon) where I spent 40 minutes outlining options and advocating over and over again to stop, think, and do what is best for your business. But here it is from First Round Review, which usually has incredibly good articles, The Five Mistakes Startups Make When Building for Mobile. In short, here are his five myths and realities:

  1. Myth: Building apps natively per platform is a waste of time and money.
    Reality: If you want a five-star app, build natively. Period.
  2. Myth: My backend infrastructure is ready to support mobile apps.
    Reality: You will need to change, upgrade, or completely rebuild your backend to create the best mobile experience.
  3. Myth: You can build your mobile app internally as fast as an outside firm.
    Reality: Building your app yourself will take 4x the time.
  4. Myth: If I outsource to a mobile development firm, I won’t have to do any work.
    Reality: For the best outcomes, clients need to be heavily involved with the firms they’ve contracted.
  5. Myth: Once I start working with a development firm, I’ll be stuck with them forever.
    Reality: Working with an external firm at first can make it even easier to build internally in the future.

First thing is first: this guy is biased. He works for an outsourcing firm so I’m not surprised he is advocating outsourcing everything.

Second things second, I don’t have a problem with most of it. #2 is probably correct. Adding any new platform, interface or screen dimension may very well require backend changes. #4 is definitely true and #5 is true, too, although sometimes it is hard to pick-up other people’s code.

#1 and 3, though…

However you slice it #1 is bad advice. No, a five-star app does not have to be native. I’ve seen plenty of excellent applications that use HTML5 or use a combination of HTML5 and native code. All of our apps use native and HTML5 to a certain extent. Equals note interface, for instance, is all HTML5 — it was by far the best way to do it at the time we started working on it. Equals also uses a lot of native code. Equals also uses a ton of ANSII C. Anything written in HTML5 and ANSII C can be ported to other platforms so it is our goal to minimize the native Objective-C, Ruby and Java that we use, and we are willing to do that for anything that would feel natural even when it isn’t native.

#3 is also odd. How important is the code to your business? Do you have more money than time? Do you have an outsource contractor who you can have a long term relationship with? Do you have development skills? Is this a skill set you need to be successful? How sure of your product are you? Do you need to be making rapid changes and tweaks, releasing code on a weekly, daily or multiple times per day basis? How much time can the contractor give you? Will they act as apart of your team or is this a throw it over the wall to get it done situation? How active will the contractors be over the long run?

Anyone who has been around the block will instantly know that the author’s advice needs to be considered. Anyone who hasn’t, though, may believe it hook, line and sinker. And that’s what bothers me.

In all cases the answer is, it depends. And the only way to determine which way to go is to know who you are, what you are trying to accomplish, where you are today and where you want to be tomorrow.

Pet Peeves

I’m anal retentive. I like things to be neat and orderly. I like a clean house, which is why I try to go in my kids’ rooms as little as possible. When I was young I was really bad. Other people’s non-anal attitudes would drive me a little crazy, which in turn would drive me even more crazy for being driven crazy by it to begin with.

I’m actually better than I used to be, though, and I’m not so bad that I can’t handle a little disorder. My wife is decidedly not anal retentive, for instance. I try my best to not inflict my internal torture on her. So it is rare that I find other people’s habits driving me nuts these days.

Lately, though, there has been one habit that drives me nuts. It’s the tendency to use phrases like, “my friend” or “friend of the show.” I absolutely hate this and makes me want to throw my iPad or iPhone out a window every time I encounter it.

It has become common place among too many authors to refer to people they know as “my friend” before telling you about him. On a recent podcast, for instance, the speaker was talking about Fred Wilson, a well-known venture capitalist in New York. The speaker went out of his way to mention that he knew Fred, even though it had absolutely nothing to do with his point. Who cares, I screamed at my iPhone? Are you really so insecure that you need to tell the world you know this man?

In some cases, like when you are specifically promoting something of theirs, it is important to mention it. I usually do this in a footnote. From my perspective, this is full disclosure. But when you are quoting a person or relaying something that that person said or otherwise referencing that person for a thousand other reasons, it really should be omitted. It just comes across as egotistical.

Good Reads V

I read a lot and often store up posts that I don’t have much to comment on personally but are excellent articles worth a read. I have more right now stored than I care to mention. This selection is business and technically-oriented. Here’s a few for the weekend:

  • Fear of Flying by Dave McClure. I’ve never been much afraid to fail but it’s still good to be reminded every once in a while, to look in the mirror and ask oneself whether that’s still true.
  • Unprofessionalism by Allen Pike. When we released powerOne version 4 we received a lot of negative feedback from staunch customers over the design. (We got a lot of positive feedback, too.) Some people were very respectful, saying they didn’t like it and even explaining why, which helped a ton as we developed version 4.1 (now in review). Some were very visceral, even calling for us to be fired. It’s easy to forget that there are people on the other end of that email, people doing the best they can, people who sometimes do the right thing and sometimes make mistakes. (via Daring Fireball)
  • Christmas Gifts and the Meaning of Design by Ben Thompson. Ben looks at his favorite gift of all time, what it means from a design perspective, and how we can utilize that in our own products and services.
  • On Delegation by John Cook. I came to the conclusion years ago that, when building a company, we should first hire for the things we are not good at or don’t want to do but need to be done. I also came to the conclusion that we know to fire someone when they are making extra work for me. John has a wonderful run-down on some decision points.
  • Software Development in 2014 by Tim Bray. Exceptional, tight list of the state of software development in 2014.
  • Understanding the Underbelly of Online Marketing by Mark Suster. One of the great business thinkers of our time, Mark dives into the seedy world of online marketing. Important to understand, even if you choose to say no.
  • Wearability Is Not Enough by Michael Mace. Michael, a great thinker on technology topics, focuses on wearable computing and why he is a skeptic. I haven’t worn a watch since high school. Can’t imagine doing it now.
  • Why Bitcoin Matters by Marc Andreessen. I’ve been trying to understand bitcoin for a while. Thanks to Marc, I do now. Very important read.

“We’re Just Flipping Through Index Cards”

Marco Arment took the time to transcribe an incredible interchange between John Roderick and Myke Hurley. John Roderick, a musician and incredible thinker on the music industry, talks about how the music world has changed in the past ten years and what this means for distribution.

As I read it, all I could think of was how replacing “ten” years with “five” and replacing “music” with “software”, had no discernible impact on the truth of the statements. Marco then makes this point at the end.

Go read it.

Mobile Portland Presentation

I am proud to announce that I’m the featured speaker at Mobile Portland this month. I gave this presentation once already at CocoaSlopes in Ogden, Utah. It was very well received.

The topic from the Mobile Portland site:

The software world has been turned on its head and all the rules that were once taken for granted are now obsolete. Elia has developed new rules for modern mobile apps, learning from his 17 years of running an indie company and transitioning from the old to the new.

Elia Freedman is the founder and CEO of Infinity Softworks. During his 17 years running an indie mobile software company, Elia has navigated the transition from Newtons to PalmPilots to Windows Mobile, BlackBerry, iOS and Android. The rules of making money in mobile has changed drastically in the past five years, let alone the past 17.

Elia’s business is changing, too. In this presentation, “Build Businesses, Not Apps,” Elia will share the thinking that has led to his own business transition, leaving you with plenty to think about in the New Year.

If you would like to attend, it will be held at Urban Airship’s offices, Monday January 27th at 6pm. Hope to see you there!