Gesamtlänge aller Episoden: 2 days 7 hours 39 minutes
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...
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...
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...
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...
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
Talking through the process that ultimately lead to the creation of Emoji++, my recently launched custom keyboard for iOS 8. ????