Developing Perspective

Prompted by some thinking I did around building the App Preview for Pedometer++, I start to wonder about honesty in advertising. How honesty should I be? What level of candor is appropriate, helpful, reasonable? Building an App Preview

I’m not a huge fan of the term polymath. It sounds kinda pretentious but sometimes the best word for something is that way. Today I was struck by the wild variety of tasks and skills that it takes to run a business principally on your own. So I wanted to walk through some of disparate aspects of the ‘job’. Hopefully giving someone who is considering going out on their own some good food for thought. My intention isn’t to scare anyone off, but just to help you understand the inherent complexity of this line of work, and an appreciation for the things other people handle for you in a J-O-B, job. General Development Software engineering Bug tracking Product Design Release planning Customer support Version Control iTunes Connect submission lifecycle iOS Development Objective C, Xcode, Interface Builder Device and iOS version management Photoshop, PaintCode Testing / QA Server Development Ruby on Rails Postgres Memcached, nginx, redis Queueing, sidekiq Linux system administration, Backups, Security updates Operations iTunes Connect, contracts, payments, Accounting, Taxes and banking. Budgeting Compliance, Local, State, Federal, Business Licenses Benefits / Welness General hosting, email, domains, etc Marketing Websites ‘Brand’, personal and otherwise Photoshop Marketing concepts and ideas Microeconomics

Today I walk through my history thinking about Swift. From WWDC to now I’ve done a lot of thinking about Swift as whether I should be using it. The result makes me feel a bit conflicted, but the brutally pragmatic part of me is winning out. Swift on Apple.com My WatchKit series

I take a break out of my normal 15 minute format for a return of my occational interview series. This week I’m delighted to talk to Sam Soffes about balancing your own product work with doing consulting, different ways of thinking about success and deciding what it is you want to do with your time. Sam has been developing for iOS since 2008 and has worked on a wide variety of successful products. He is currently working on Whiskey, a Markdown editor for Mac and iOS.

Rather than wading into the hullabaloo regarding Apple’s software quality directly I instead decided to take a step backwards and consider the forces that have driven us to this situation in the first place. My goal is to consider the forces that make keeping software stable over time difficult. The result can apply to small projects as well as to a company as large as Apple. Marketing Complexity: The pressure to keep adding features in order to keep software relevant in a marketplace. Intrinsic Complexity: The unfortunate reality that any added feature doesn’t just linearly increase complexity, instead it increases radically. Personnel/Personal Complexity: The tension and struggle around keeping sharp, talented engineers focused on stability when the promise of working on something else, newer and more exciting looms. These are the concerns we need to stay conscious of in order to manage our software over time. Handshake Problem

Today I think out loud about the implications of an App Store that is functionally full. Where applications cannot realistically thrive simply because of novelty or freshness. Whatever you do now you are facing up against a hyper-competitive marketplace. I think this changes significantly how we need to pursue things from a business perspective as well as helps us be realistic about what to expect. As an experiment I also recorded this episode as a video. I’m not really sure how valuable this is but I’ll never know unless I try. I’m thoroughly enjoying trying out video recently as a medium for sharing within our community. As a result of how my recording was setup the audio for this episode as a bit more echo than I would have liked, I’ll get that buttoned down if I try this again. YouTube version of this Episode

Thinking out loud about why I recently starting my series called As I Learn WatchKit. I’ve learned a lot about the creative process by giving myself permission to put unpolished things into the world. My first attempt at Youtube Then, I dive into the economics of building WatchKit apps. In general I think that the economic realities of building apps for it are consistent with any other app endeavor. If it was a good idea before it is likely doubly so to add a Watch extension. If it is a new idea you have a great opportunity to be an early adopter.

My first reactions to WatchKit. I’m really glad Apple has given is some genuinely powerful capabilities with this first generation of APIs. Getting Started with WatchKit My Initial Impressions Apple’s Main WatchKit page Developer Forums

For a while now I’ve had an episode idea discussing some of the ‘interesting math’ about working on a project by yourself. I discuss how working on something by yourself is so very different than in working on any other sized team.

I’ve had a few folks ask me about my plans and ideas for Apple Watch. While I don’t try to be too coy about what I’m working on I’ve definitely kept some of my ideas close to the vest. I’m well aware that ideas, in general, are useless on their own. But that doesn’t mean that being promiscuous with your ideas is still always a good choice. Derek Sivers on ideas. Trying to formularize this I came up with the following structure for ideas and where sharing them is likely a good and poor choice. Like all good concepts it can be best demonstrated with a two-axis graph with four quadrants: On the one axis is the ease of implementing/realizing the idea. On the other is the expected return on a successful implementation of that idea. Easy, High Reward: If you actually have one of these (you likely don’t) keep it quiet and run with it as fast as you can. Likely hyper competitive. Simultaneous invention everywhere. Easy, Low Reward: Confections that are likely flash in the pan (if they flash at all). Hard, Low Reward: Time sinks, labors of love. Most ‘I have a great idea for an app’ pitches. XKCD on easy vs hard problems. Hard, High Reward: Real businesses are built here.

With the impending arrival of the AppleWatch next year and the WatchKit SDK next month I’m starting to shift my focus towards ‘wearables’. They present a few challenges to me as a developer, not the least of which is that I have almost no experience with that type of device. I used to wear a watch years ago but haven’t consistently for a long time. I saw the Pebble when it first came out and it looked kinda janky. But now it is clear this is an area that the larger companies that I piggyback my business on are heading so I’m trying hard to make sure I don’t fall off. To help me get up to speed I’ve been purchasing a variety of devices to start getting my feet at least slightly damp, if not actually wet. I started with the Jawbone UP and just got the Microsft Band. These are my initial reactions and thoughts. Jawbone UP 24 Microsoft Band

I recently hit a few milestones that got me thinking about the attributes of sustained projects. My 7th iOS (iPhone) Developer Program My first app approved 6 years ago 200 Episodes I tried to boil them down into four keys: Purpose Diversity Flexibility / Ruthlessness Patience / Tenacity

Thinking through the Retina iMac in a world where pixels stop mattering. Also, what’s going on with the iPad? Marco Arments’s thoughts on Retina iMac vs Mac Pro AnandTech’s Hands-on

While a single button might seem somewhat boring or mundane to discuss I unpack the process of thinking through a single button in Emoji++. Specifically how to handle editing of favorites. Ultimately I went with an Edit button rather than a gesture based approach. While somewhat benign superficially decisions like this can make or break your user experience. Also, why I didn’t make the icons wiggle. The Boring Designer Creating Passionate Users Creating Passionate Users - Feature Curve

Thursday, July 12, 2012 - The importance of having Side Projects and Internationalization. iOS and Mac Podcasts Plain Wallpapers Cheddar API Question from Paul Dunahoo.