Timestamps & topics

• 0:00 Well here we are
• 0:26 Why Jake is great
• 1:14 Where the books came from?
• 4:11 On starting to write (& NaNoWriMo)
• 6:00 Business & reputation
• 7:58 Self-doubt, de-risking, and blogging as book v1
• 9:49 Education vs. entertainment
• 12:02 Structure, organization, & clarity
• 14:44 The one-week prototype & ToC
• 15:40 Learning from experts & friends
• 18:13 Audience & marketing
• 19:51 Word of mouth and what publishers can’t do
• 23:35 Why not selfpub?
• 24:46 Perils of cover design
• 27:48 On writing something that works
• 30:23 Devin being handsome & Jake laughing

This interview was originally published on Useful Books

Jake Knapp on designing nonfiction worth reading was originally published in Useful Books on Medium, where people are continuing the conversation by highlighting and responding to this story.

This isn’t the sort of thing I usually write about. I like to write about design and code, but what this law allows is so egregious I felt compelled to put together this quick guide. So here are three simple steps you can take to protect yourself online.

1. Make your voice heard
2. Protect your communications with a VPN
3. Use Tor

Step 1: Make your voice heard

If you object to this law and reside in the UK you need to write to your MP and express your honest thoughts about this bill. That’s it. Only takes 5 minutes.

Step 2: Protect your communications with a VPN

A virtual private network (VPN) is a service which encrypts traffic between your devices and the VPN’s servers. When you normally surf the web, all your communication goes through your internet service provider (ISP) unencrypted. The ISP can log this activity and store it for later. This is one type of data that the Snoopers’ Charter forces ISPs to collect.

With a VPN, all traffic from your computer to the VPN’s own servers is encrypted. Even if your ISP has tapped directly into your online communications they will only see an unintelligible mess.

Does a VPN give you complete privacy online? No, but it severely limits the data that eavesdropping can collect. There are a few things to keep in mind with VPNs:

1. Your communications are only as secure as the VPN you use
2. There are other methods available for tracking you online (cookies, ad & plugin fingerprinting to name a few)
3. The VPN server you connect to (sometimes called “exit point”) must be outside of the UK to evade bulk data collection by your ISP. Most services have many to choose from.

So, which VPN should you use? There are many great providers with excellent security records. The two that I highly recommend are NordVPN and ExpressVPN.

Extra credit: Use Tor

For most people, a good VPN will provide a sufficient level of security. If you want to take your communication anonymity to the extreme, then using Tor is next step. Tor is a anonymity network which bounces your communications between a series of relays, encrypting it each bounce. No node knows the start or end point of the traffic, just where it needs to go next. This makes tracing any communication near impossible.

Setting up Tor is much more complicated than a VPN. If you’re interested in trying it, I suggest downloading Tor Browser. Tor Browser is a modified version of the popular Firefox internet browser that has Tor enabled by default. Anything you do inside that browser is encrypted and anonymised.

In exchange for this extra level of security you will sacrifice speed. Because Tor bounces your traffic through other networks and computers, it can be anywhere for 10 to 20 times slower than your normal connection. That’s the tradeoff.

Start now

Whatever side of the internet privacy debate your fall on, you owe it to yourself to understand how your private communications are being attacked and how to defend against these intrusions. If you are as concerned about freedom of information as I am please consider supporting groups that are fighting for our rights, like the EFF, Liberty, and the ACLU.

Originally published at www.hailpixel.com.

1. Be pronounceable
2. Be able to register a domain which contains the word(s)
3. Be something I’m comfortable using
4. Be something my customers are comfortable using

Beyond that, just choose some words and visuals and run with it. All brands start out with no recognition, no meaning, and often very goofy names. Brand power is derived from what has been accomplished under the name, not from how slick the name is. Google? A silly name. Now it is used with reverence in boardrooms across the world. It’s also a verb.

How about Songkick? Again, if you are not familiar with the live music company, it’s an awkward name. Ian Hogarth, the founder of Songkick, broke down the criteria he and his cofounders used when they originally chose the name back in 2007. It had to be:

1. Short (no more than 2 syllables)
2. Memorable
3. Available
4. Have unambiguous spelling (i.e. no homonyms)
5. Reference music in some fashion

And for the actual process of choosing the name?

“We generated a spreadsheet of a couple thousand word pairings”, Ian recalls, “and used Instant Domain Search to find the available ones and then just went with one.”

Stephen Rapoport, founder of Pact Coffee, followed a surprisingly similar path. In fact, Pact Coffee started life as YourGrind:

“YourGrind was always a disposable brand, which I intended to change if the model worked. I picked it in about an hour, and based the brand on which .com and Twitter handles were available. I found a list through Lean Domain Search.”

So, in summary, don’t worry about it. Choose some words that feel inline with what your company is trying to accomplish and just run with it. In time those simple words will take on a life of their own.

Originally published at www.hailpixel.com.

This is the story about the mistakes, breaks, successes, and all the gory detail involved in launching an app. So, here’s the basic timeline, from inception to launch.

January 2nd — Inception

An early version of Colordot has been live as a web app for almost three years. Go check it out if you haven’t seen it before, it’s crucial to this story. It has entered a few people’s workflows and has around 18k active users a month.

Many users asked if there would be a mobile app. In an attempt to be entrepreneur-y about it, I stuck a quick mailchimp form in the help section asking users to sign up to be alerted when the mobile app is ready. That list hit 2.5k subscribers in late 2015. I never had a specific threshold in mind, but 2.5k felt right.

It was time to make Colordot for iOS. I had a pretty good idea of what I wanted to create. Over the years I had hacked together a few prototypes, trying out different interaction designs. I sketched out three wireframes (this took about 5 minutes), opened up Xcode and started coding.

February 8th — It’s alpha time

Hit v0.1. It’s taken two weeks longer than I expected to get to this point. Colordot now has it’s three core features: choosing colors with touch, picking colors with the camera, and support for multiple color palettes. It also doesn’t crash that often. Time to get it into the hands of other people.

It takes half a day to successfully build and upload an app for testing on iTunes Connect, Apple’s app management platform. I honestly don’t know how I would get anything done on iTunes Connect without Google & Stack Overflow 🙏. They’re like a safety net.

I send my partner an invite and check that the Test Flight build works. The app breaks almost immediately. Quick fixes, new build uploaded. I ask a few close friends to join the testing list. More obvious bugs and interaction problems surface. Work continues.

Two weeks later I’m feeling confident so I tweet out a call for testers. Through that tweet 10 more people offer their help. Colordot now has a total of 12 testers.

The more testers, the better Colordot gets. People naturally tire of trying my broken, busted-ass app. So when I change something dramatically — a new UI layout, for example — I message each tester personally and ask them to try the new build.

March 8th — The Beta

After a month of testing (I expected this to take a week), the app feels usable. With more confidence behind the concept, I begin to turn almost any conversation into an user test. Especially at industry events. You know the deal:

Me: “Hi, I’m Devin”

Them: “Hi, I’m XXXXX. What do you do?”

Me: “Well, I’m actually working on an a little app…”

I hand over my phone with a fresh install of Colordot open

Them: “… What the fuck is this.”

After a series of somewhat awkward conversations, I realize two things:

1. At first, no one has any idea what they are looking at, let alone what they should do.
2. After I demonstrate how the color picker works, people instantly get it. They often end up designing an entire color palette.

Colordot needs a tutorial.

March 21st — Colordot’s tutorial

My view on in-app tutorials is that it’s a crutch for bad interface design. I have high standards for usability and figure that if someone can’t pick something up and figure out how to use it from the get-go, the design is a failure. And, of course, I now find myself needing a tutorial.

An interactive tutorial is just another app inside your app. I knew this, but I really didn’t appreciate it. The whole design process had to begin anew. I had to go back to the whiteboard and wireframe out all the steps of the tutorial, design a whole tutorial system, code it, test it, refine it, etc. The whole works. All in all, it took another two un-budgeted weeks to get right.

Since I’d been watching people use the app for the past month, I knew the key interactions which needed explanation before people got it: how to add a new color and the gestures used to edit the color. The best feature of the app — the camera picker — doesn’t even appear in the tutorial. Once people get the swipe gestures, they naturally tap the camera button. Once in the camera picker, the experience is self-explanatory. So with this in mind the tutorial went from this:

to this:

A new user is now using the full app after just a few screens and very little text.

March 22nd — Marketing materials

With Colordot nearing v1.0, it was time to shift my focus to it’s launch page and marketing materials. A majority of my time went into capturing and animating the explainer video which now sits at the top of the Colordot’s launch page. It takes about three days to get all the material together.

March 23rd — Losing the debate and winning

After a long, coffee fueled debate with Chris I concede that my perfect UI — specifically the button layout for the color picker — can be improved. Adding a “cancel” button to the picker UI allows users to close the picker and remove any changes made to a color. It takes an hour to implement. I push the new UI to the testers.

March 24th — Surprise work

The new picker UI is received very well. But this UI improvement means I have to redo the entire demo video from scratch. Another day is spent in After Effects.

March 31st — App review

Colordot hits v1.0. I push it out to the 30 testers on the beta list and ask them to try and break the app. They do. It takes another 4 builds to get everything smoothed out. Each build-test-review iteration takes about a day.

On April 4th I submit the app to Apple for review.

April 9th — : (

Rejection! I submitted the app to Apple and after 4 days of waiting Colordot is rejected. Looks like I introduced a bug on one of my hot fixes and didn’t run all my checks. Typical. It takes just 10 minutes to fix the bug and resubmit Colordot to Apple.

April 14th — : )

Eureka! Colordot passes review. Now that publishing my first app ever on the App Store has become very real, I begin to realize I have absolutely no idea how I charge money for it and, if it sells at all, get the money from Apple. I start to read the developer & distribution agreements and discover that they’re all incorrect. None of the documents are in my company name or even at the correct address.

Thankfully, Apple Developer Support is fantastic. After a 10 minute phone call and a few verification emails the contracts are in the correct name and I can digitally sign them. Then I get to the tax paperwork.

Hailpixel — the company that I do business through — is a UK limited company. Apple, as I’m sure you are aware, is a US company. That means the IRS has a great deal of interest in what Apple does, especially with foreign companies. I need to get an EIN (Employer Identification Number) from the IRS so that Apple can prove it is sending proceeds to a foreign company and does not need to withhold tax on Hailpixel’s behalf. This is thanks to a UK-US tax treaty. After some frantic searching, I come across a series of posts with step-by-step instructions on how to call the IRS and get an EIN in an hour. After a two hour call with a very, very somber IRS agent Hailpixel has an EIN. I submit the tax forms to Apple.

My EIN doesn’t pass verification.

I call Apple Developer Support and their advice is simple: “Try it again tomorrow!”

April 15th — Tax trouble

I submit the tax forms again. They still fail. And the same the following day. I talk to the IRS, but everything seems fine. Apparently it’s just one of those delays, and might take up to three weeks.

After a bit of research, I learn that I don’t need to have the tax forms verified before launch. The tax forms are to negate the required IRS withholding and — from my understanding — as long as they are verified before you take the first payment form Apple, you should have no trouble.

April 21st — Go live

Holy shit it’s happening. I’m sure there is something I’m missing but who cares. It’s go time. I push the Colordot v1.0 to the app store. And… nothing happens. I try to buy my app and get this message: “This app is only available in the US app store”.

Wait, what. Did I miss something? I frantically look through all the settings in iTunes connect. Do I need to localize for each region? Oh shit, do I need to get translations for all regions?! DO I NEED TO REDO THE ITUNES INFORMATION??

And then all of a sudden, everything works. Turns out it takes about an hour for an app to propagate to all the app stores. Now you know.

After I confirm the app does install on a few friends’ phones, I head over to Product Hunt and post Colordot for iOS. Thus ends a 4 month journey of converting a weekend project to an iPhone app.

The final statistics

Here’s the summary of my expectations vs. reality.

Core development

Expected 2 weeks, was 2 months with including the tutorials.

Testing

Expected about a month in parallel with development and marketing. In reality, the alpha and beta tests lasted 3 months and spanned 30 testers.

Marketing

A week to put together demo video, site, and marketing hit list. Almost hit this one on the nose, took 1.5 weeks thanks to having to recreate the demo video from scratch.

Legals

Didn’t even think about this. I expected Apple’s App Store to basically take care of this. Took a full 3 days to put all the paperwork in place.

Active promotion

I expected one day; launch day. It mostly played out that way. I am glad I took the entire day off to focus on the launch. It allowed me to be responsive to all manner of questions and comments.

In Summary

Expected: A month. In reality: 4 months.

And the lessons I took away from this sole-developer experience?

1. Remember the adage “estimate how much time you need for a project, then double it”? You should honestly triple it.
2. Show off your work — constantly. If a person shows interest, ask them to be a tester.
3. “Business” things — like contracts, tax compliancy, etc — happen at a snails pace compared to development. Start that work as soon as possible.

This project took about four times longer than expected, but I am very proud of the results. Working on something from start to finish is a rare experience in modern work. If you use colors in your work, please do checkout Colordot for iOS and let me know your thoughts on Twitter, I’m @hailpixel.

PS — Thanks

I’d like to thank a few people for all their help and support. Without it, I honestly wouldn’t have finished this project. Thank you Jenny, Utku, James, Rob, Rob, Chris, Nat, Anthony, and to all the testers, suggesters, and friends. You know who you are.

Originally published at www.hailpixel.com.

What it takes to launch an app was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.