Developing Perspective http://developingperspective.com Developing Perspective is a podcast discussing the news of note in iOS Development, Apple and the like. Hosted by David Smith, an independent iOS developer. Never longer than 15 minutes. en hourly 1 Copyright © Developing Perspective 2013 david@crossforward.com (David Smith) david@crossforward.com (David Smith) technology 1440 http://developingperspective.s3.amazonaws.com/logo_small.png Developing Perspective http://developingperspective.com 144 144 A near daily discussion of the news of note in iOS, Apple and the like. Developing Perspective is a podcast discussing the news of note in iOS Development, Apple and the like. Hosted by David Smith, an independent iOS developer. Never longer than 15 minutes. iOS, apple, mac, geek, development, iPhone, cocoa, iPad David Smith David Smith david@crossforward.com no no #190: Everything but a Business Model http://developingperspective.com/2014/07/03/0/ Thu, 03 Jul 2014 11:30:00 -0400 David http://developingperspective.com/?p=5552816735040

I will be on vacation for the next two weeks, so unless something monumental happens in between now and late July there won’t be any episodes of Developing Perspective.

Back at WWDC, basking in the glow of the river of great new announcements I had quipped “Wow, they gave us everything but a business model.” That comment is clearly absurd but it does drive towards a more honest and worthwhile point. In many ways the situation iOS developers find themselves in heading into the Autumn of 2014 isn’t about technology or tools, it is about business. As the market has matured the natural consequence is that older inefficiencies that may have propped up unsustainable models have fallen away.

The App Store and related ecosystems are now extremely efficient. If there is an opportunity to be exploited we can expect it to be found and exploited. If you come up with a great new idea it will be analyzed, dissected and the interesting parts copied with often head-turning pace. As I have navigated this transition myself I have started to see many issues with the approach I had been taking to my business. Some of which I have been able to address but many of which I’m still working through.

For the purpose of today’s episode I thought it might be constructive to take a quick tour of the various models and their various strengths and weaknesses. I’m going to be working in rough order of which I think they are desirable in the current ecosystem.

Subscriptions

tl;dr - People pay you on an ongoing basis for providing software and software related services.

Pros - So long as your subscription base is enough for your expenses and your renewal/signup rate exceeds your cancellations you are golden.

Cons - Often tricker to get someone to make a long term commitment. Managing credit cards, expirations, etc. Typically smaller user base needed (yay!), each requiring and feeling owed more (not so yay).

Advertising

tl;dr - People use your software and are presented a message from someone else you pays you.

Pros - Strong possibility for ongoing revenue. Can make your software free.

Cons - You need to show other people’s messages in your apps. Requires large customerbases for reasonable revenue.

Consumable In-App Purchases

tl;dr - People make (typically) small, repeated payments to continue to gain access to aspects of your software. Gratuity based models also fall into this category.

Pros - Strong possibility for ongoing revenue. Lets you segment your customer base by how much they are willing to spend.

Cons - Can quickly get very dodgy.

One Time In-App Purchases

tl;dr - People make payments to gain access to specific parts of the application or content therein.

Pros - Gives users a clear trial of the experience before needing to make a commitment.

Cons - Often very tricky to work out what part of the application can be segmented off. If you are too generous nobody will buy, too stingy and nobody will buy.

Up Front One Time Purchase

tl;dr - People pay money to be able to use your software.

Pros - Simple and straightforward.

Cons - Trickier to make sustainable since your effectively cap your income per user. Single Price. Long term support gets hard to justify.

Free

tl;dr - You create software, everyone uses it without charge.

Pros - Wide adoption potential.

Cons - Often hard to sustain long term. Most often seen in either altruistic or venture based software.

What is best?

It is going to vary for each business. What I have found over the last 6 years is that models that have more of a focus on ongoing revenue are more sustainable than things that are more one-time oriented. Mixing as many as you can often is important too.

It is also absolutely imperative that you have a good working definition of what success looks like for yourself before you can make a thoughtful choice.

]]>

I will be on vacation for the next two weeks, so unless something monumental happens in between now and late July there won’t be any episodes of Developing Perspective.

Back at WWDC, basking in the glow of the river of great new announcements I had quipped “Wow, they gave us everything but a business model.” That comment is clearly absurd but it does drive towards a more honest and worthwhile point. In many ways the situation iOS developers find themselves in heading into the Autumn of 2014 isn’t about technology or tools, it is about business. As the market has matured the natural consequence is that older inefficiencies that may have propped up unsustainable models have fallen away.

The App Store and related ecosystems are now extremely efficient. If there is an opportunity to be exploited we can expect it to be found and exploited. If you come up with a great new idea it will be analyzed, dissected and the interesting parts copied with often head-turning pace. As I have navigated this transition myself I have started to see many issues with the approach I had been taking to my business. Some of which I have been able to address but many of which I’m still working through.

For the purpose of today’s episode I thought it might be constructive to take a quick tour of the various models and their various strengths and weaknesses. I’m going to be working in rough order of which I think they are desirable in the current ecosystem.

Subscriptions

tl;dr - People pay you on an ongoing basis for providing software and software related services.

Pros - So long as your subscription base is enough for your expenses and your renewal/signup rate exceeds your cancellations you are golden.

Cons - Often tricker to get someone to make a long term commitment. Managing credit cards, expirations, etc. Typically smaller user base needed (yay!), each requiring and feeling owed more (not so yay).

Advertising

tl;dr - People use your software and are presented a message from someone else you pays you.

Pros - Strong possibility for ongoing revenue. Can make your software free.

Cons - You need to show other people’s messages in your apps. Requires large customerbases for reasonable revenue.

Consumable In-App Purchases

tl;dr - People make (typically) small, repeated payments to continue to gain access to aspects of your software. Gratuity based models also fall into this category.

Pros - Strong possibility for ongoing revenue. Lets you segment your customer base by how much they are willing to spend.

Cons - Can quickly get very dodgy.

One Time In-App Purchases

tl;dr - People make payments to gain access to specific parts of the application or content therein.

Pros - Gives users a clear trial of the experience before needing to make a commitment.

Cons - Often very tricky to work out what part of the application can be segmented off. If you are too generous nobody will buy, too stingy and nobody will buy.

Up Front One Time Purchase

tl;dr - People pay money to be able to use your software.

Pros - Simple and straightforward.

Cons - Trickier to make sustainable since your effectively cap your income per user. Single Price. Long term support gets hard to justify.

Free

tl;dr - You create software, everyone uses it without charge.

Pros - Wide adoption potential.

Cons - Often hard to sustain long term. Most often seen in either altruistic or venture based software.

What is best?

It is going to vary for each business. What I have found over the last 6 years is that models that have more of a focus on ongoing revenue are more sustainable than things that are more one-time oriented. Mixing as many as you can often is important too.

It is also absolutely imperative that you have a good working definition of what success looks like for yourself before you can make a thoughtful choice.

]]>
0 900 I will be on vacation for the next two weeks, so unless something monumental happens in between now and late July there won’t be any episodes of Developing Perspective. Back at WWDC, basking in the glow of the river of great new announcements I had quipped “Wow, they gave us everything but a business model.” That comment is clearly absurd but it does drive towards a more honest and worthwhile point. In many ways the situation iOS developers find themselves in heading into the Autumn of 2014 isn’t about technology or tools, it is about business. As the market has matured the natural consequence is that older inefficiencies that may have propped up unsustainable models have fallen away. The App Store and related ecosystems are now extremely efficient. If there is an opportunity to be exploited we can expect it to be found and exploited. If you come up with a great new idea it will be analyzed, dissected and the interesting parts copied with often head-turning pace. As I have navigated this transition myself I have started to see many issues with the approach I had been taking to my business. Some of which I have been able to address but many of which I’m still working through. For the purpose of today’s episode I thought it might be constructive to take a quick tour of the various models and their various strengths and weaknesses. I’m going to be working in rough order of which I think they are desirable in the current ecosystem. Subscriptions tl;dr - People pay you on an ongoing basis for providing software and software related services. Pros - So long as your subscription base is enough for your expenses and your renewal/signup rate exceeds your cancellations you are golden. Cons - Often tricker to get someone to make a long term commitment. Managing credit cards, expirations, etc. Typically smaller user base needed (yay!), each requiring and feeling owed more (not so yay). Advertising tl;dr - People use your software and are presented a message from someone else you pays you. Pros - Strong possibility for ongoing revenue. Can make your software free. Cons - You need to show other people’s messages in your apps. Requires large customerbases for reasonable revenue. Consumable In-App Purchases tl;dr - People make (typically) small, repeated payments to continue to gain access to aspects of your software. Gratuity based models also fall into this category. Pros - Strong possibility for ongoing revenue. Lets you segment your customer base by how much they are willing to spend. Cons - Can quickly get very dodgy. One Time In-App Purchases tl;dr - People make payments to gain access to specific parts of the application or content therein. Pros - Gives users a clear trial of the experience before needing to make a commitment. Cons - Often very tricky to work out what part of the application can be segmented off. If you are too generous nobody will buy, too stingy and nobody will buy. Up Front One Time Purchase tl;dr - People pay money to be able to use your software. Pros - Simple and straightforward. Cons - Trickier to make sustainable since your effectively cap your income per user. Single Price. Long term support gets hard to justify. Free tl;dr - You create software, everyone uses it without charge. Pros - Wide adoption potential. Cons - Often hard to sustain long term. Most often seen in either altruistic or venture based software. What is best? It is going to vary for each business. What I have found over the last 6 years is that models that have more of a focus on ongoing revenue are more sustainable than things that are more one-time oriented. Mixing as many as you can often is important too. It is also absolutely imperative that you have a good working definition of what success looks like for yourself before you can make a thoughtful choice. I will be on vacation for the next two weeks, so unless something monumental happens in between now and late July there won’t be any episodes of Developing Perspective. Back at WWDC, basking in the glow of the river of great new announcements I had quipped “Wow, they gave us everything but a business model.” That comment is clearly absurd but it does drive towards a more honest and worthwhile point. In many ways the situation iOS developers find themselves in heading into the Autumn of 2014 isn’t about technology or tools, it is about business. As the market has matured the natural consequence is that older inefficiencies that may have propped up unsustainable models have fallen away. The App Store and related ecosystems are now extremely efficient. If there is an opportunity to be exploited we can expect it to be found and exploited. If you come up with a great new idea it will be analyzed, dissected and the interesting parts copied with often head-turning pace. As I have navigated this transition myself I have started to see many issues with the approach I had been taking to my business. Some of which I have been able to address but many of which I’m still working through. For the purpose of today’s episode I thought it might be constructive to take a quick tour of the various models and their various strengths and weaknesses. I’m going to be working in rough order of which I think they are desirable in the current ecosystem. Subscriptions tl;dr - People pay you on an ongoing basis for providing software and software related services. Pros - So long as your subscription base is enough for your expenses and your renewal/signup rate exceeds your cancellations you are golden. Cons - Often tricker to get someone to make a long term commitment. Managing credit cards, expirations, etc. Typically smaller user base needed (yay!), each requiring and feeling owed more (not so yay). Advertising tl;dr - People use your software and are presented a message from someone else you pays you. Pros - Strong possibility for ongoing revenue. Can make your software free. Cons - You need to show other people’s messages in your apps. Requires large customerbases for reasonable revenue. Consumable In-App Purchases tl;dr - People make (typically) small, repeated payments to continue to gain access to aspects of your software. Gratuity based models also fall into this category. Pros - Strong possibility for ongoing revenue. Lets you segment your customer base by how much they are willing to spend. Cons - Can quickly get very dodgy. One Time In-App Purchases tl;dr - People make payments to gain access to specific parts of the application or content therein. Pros - Gives users a clear trial of the experience before needing to make a commitment. Cons - Often very tricky to work out what part of the application can be segmented off. If you are too generous nobody will buy, too stingy and nobody will buy. Up Front One Time Purchase tl;dr - People pay money to be able to use your software. Pros - Simple and straightforward. Cons - Trickier to make sustainable since your effectively cap your income per user. Single Price. Long term support gets hard to justify. Free tl;dr - You create software, everyone uses it without charge. Pros - Wide adoption potential. Cons - Often hard to sustain long term. Most often seen in either altruistic or venture based software. What is best? It is going to vary for each business. What I have found over the last 6 years is that models that have more of a focus on ongoing revenue are more sustainable than things that are more one-time oriented. Mixing as many as you can often is important too. It is also absolutely imperative that you have a good working definition of what success looks like for yourself before you can make a thoughtful choice. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
#189: In the Loop http://developingperspective.com/2014/06/26/0/ Thu, 26 Jun 2014 09:53:00 -0400 David http://developingperspective.com/?p=5553355557170 This past week we had a bit of drama about the role of podcast networks. I don’t intend to wade into that discussion but as a result of it I was asked about the role that linking and recommendations play in expanding my own audience for this show. Which is considerable and measurable. I wanted to return the favor this week by talking about how I stay informed about the goings-on in Apple development.

This isn’t an exhaustive list but these are the places I always make sure I’m up to date with.

I actually use Twitter a lot less than I used to. The signal-to-noise (even with aggressive muting) is just too low.

Podcasts

Programming and Design
Business-y Stuff
General News

Blogs

Misc

]]>
This past week we had a bit of drama about the role of podcast networks. I don’t intend to wade into that discussion but as a result of it I was asked about the role that linking and recommendations play in expanding my own audience for this show. Which is considerable and measurable. I wanted to return the favor this week by talking about how I stay informed about the goings-on in Apple development.

This isn’t an exhaustive list but these are the places I always make sure I’m up to date with.

I actually use Twitter a lot less than I used to. The signal-to-noise (even with aggressive muting) is just too low.

Podcasts

Programming and Design
Business-y Stuff
General News

Blogs

Misc

]]>
0 898 This past week we had a bit of drama about the role of podcast networks. I don’t intend to wade into that discussion but as a result of it I was asked about the role that linking and recommendations play in expanding my own audience for this show. Which is considerable and measurable. I wanted to return the favor this week by talking about how I stay informed about the goings-on in Apple development. This isn’t an exhaustive list but these are the places I always make sure I’m up to date with. I actually use Twitter a lot less than I used to. The signal-to-noise (even with aggressive muting) is just too low. Podcasts Programming and Design Debug Iterate Mobile Couch Business-y Stuff Release Notes Core Intuition General News The Prompt Accidental Tech Podcast Blogs Inessential Jared Sinclair Ole Begemann MacStories Misc Hello Internet Pragmatic This past week we had a bit of drama about the role of podcast networks. I don’t intend to wade into that discussion but as a result of it I was asked about the role that linking and recommendations play in expanding my own audience for this show. Which is considerable and measurable. I wanted to return the favor this week by talking about how I stay informed about the goings-on in Apple development. This isn’t an exhaustive list but these are the places I always make sure I’m up to date with. I actually use Twitter a lot less than I used to. The signal-to-noise (even with aggressive muting) is just too low. Podcasts Programming and Design Debug Iterate Mobile Couch Business-y Stuff Release Notes Core Intuition General News The Prompt Accidental Tech Podcast Blogs Inessential Jared Sinclair Ole Begemann MacStories Misc Hello Internet Pragmatic iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
#188: Thoughtful Accessibility http://developingperspective.com/2014/06/20/0/ Fri, 20 Jun 2014 09:36:00 -0400 David http://developingperspective.com/?p=5556937056780
  • ASCIIwwdc
  • Accessibility is an important aspect of software development. Apple’s platforms provide a wide array of tools for easily adding it into your apps. The return for this effort is often somewhat ephemeral but nevertheless rewarding.

    • Basic Accessibility overview
    • Triple-tap home shortcut
    • Thoughtful ordering of controls
    • Thoughtful ordering of words
    • Design the experience, not narration.

    • Pedometer++ (the app discussed).

    ]]>
  • ASCIIwwdc
  • Accessibility is an important aspect of software development. Apple’s platforms provide a wide array of tools for easily adding it into your apps. The return for this effort is often somewhat ephemeral but nevertheless rewarding.

    • Basic Accessibility overview
    • Triple-tap home shortcut
    • Thoughtful ordering of controls
    • Thoughtful ordering of words
    • Design the experience, not narration.

    • Pedometer++ (the app discussed).

    ]]>
    0 899 ASCIIwwdc Accessibility is an important aspect of software development. Apple’s platforms provide a wide array of tools for easily adding it into your apps. The return for this effort is often somewhat ephemeral but nevertheless rewarding. Basic Accessibility overview Triple-tap home shortcut Thoughtful ordering of controls Thoughtful ordering of words Design the experience, not narration. Pedometer++ (the app discussed). ASCIIwwdc Accessibility is an important aspect of software development. Apple’s platforms provide a wide array of tools for easily adding it into your apps. The return for this effort is often somewhat ephemeral but nevertheless rewarding. Basic Accessibility overview Triple-tap home shortcut Thoughtful ordering of controls Thoughtful ordering of words Design the experience, not narration. Pedometer++ (the app discussed). iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #187: Explorers http://developingperspective.com/2014/06/13/0/ Fri, 13 Jun 2014 15:42:00 -0400 David http://developingperspective.com/?p=5555524834780 We are exploring a new territory within the Apple developer landscape. Here is how I plan my expedition.

    Get a solid grasp of what’s new

    Start with Apple’s own overviews:

    Keep in mind questions like these:

    • What does this enable that isn’t currently possible?
    • How would Apple promote this feature?
    • Is this a evolutionary or ‘revolutionary’?
    • Does this seem to be a dead-end or a beachhead?

    Short list your paths

    Start to think about how you are going to spend your summer.

    • How much time do you have?
    • What are your ‘minimum’ required things? Not what could you do, what must you do?
    • What would you enjoy trying most?
    • Do you have any specific skills, connections or experience that give you an advantage?

    Avoid the pitfalls

    Keep a few things in mind.

    • New developer focused features are often really buggy to start with and your customers won’t care.
    • It likely need to be ready by September 1. So be careful how much you bite off. (It was Sept 10 for iOS 7).
    • Try to focus on what is going to cool in iOS 8, tackling lots of problems that aren’t specific to it might not make much sense.

    And most of all, have fun!

    ]]>
    We are exploring a new territory within the Apple developer landscape. Here is how I plan my expedition.

    Get a solid grasp of what’s new

    Start with Apple’s own overviews:

    Keep in mind questions like these:

    • What does this enable that isn’t currently possible?
    • How would Apple promote this feature?
    • Is this a evolutionary or ‘revolutionary’?
    • Does this seem to be a dead-end or a beachhead?

    Short list your paths

    Start to think about how you are going to spend your summer.

    • How much time do you have?
    • What are your ‘minimum’ required things? Not what could you do, what must you do?
    • What would you enjoy trying most?
    • Do you have any specific skills, connections or experience that give you an advantage?

    Avoid the pitfalls

    Keep a few things in mind.

    • New developer focused features are often really buggy to start with and your customers won’t care.
    • It likely need to be ready by September 1. So be careful how much you bite off. (It was Sept 10 for iOS 7).
    • Try to focus on what is going to cool in iOS 8, tackling lots of problems that aren’t specific to it might not make much sense.

    And most of all, have fun!

    ]]>
    0 0 We are exploring a new territory within the Apple developer landscape. Here is how I plan my expedition. Get a solid grasp of what’s new Start with Apple’s own overviews: iOS 8 for Developers What’s new in iOS API Diffs Keep in mind questions like these: What does this enable that isn’t currently possible? How would Apple promote this feature? Is this a evolutionary or ‘revolutionary’? Does this seem to be a dead-end or a beachhead? Short list your paths Start to think about how you are going to spend your summer. How much time do you have? What are your ‘minimum’ required things? Not what could you do, what must you do? What would you enjoy trying most? Do you have any specific skills, connections or experience that give you an advantage? Avoid the pitfalls Keep a few things in mind. New developer focused features are often really buggy to start with and your customers won’t care. It likely need to be ready by September 1. So be careful how much you bite off. (It was Sept 10 for iOS 7). Try to focus on what is going to cool in iOS 8, tackling lots of problems that aren’t specific to it might not make much sense. And most of all, have fun! We are exploring a new territory within the Apple developer landscape. Here is how I plan my expedition. Get a solid grasp of what’s new Start with Apple’s own overviews: iOS 8 for Developers What’s new in iOS API Diffs Keep in mind questions like these: What does this enable that isn’t currently possible? How would Apple promote this feature? Is this a evolutionary or ‘revolutionary’? Does this seem to be a dead-end or a beachhead? Short list your paths Start to think about how you are going to spend your summer. How much time do you have? What are your ‘minimum’ required things? Not what could you do, what must you do? What would you enjoy trying most? Do you have any specific skills, connections or experience that give you an advantage? Avoid the pitfalls Keep a few things in mind. New developer focused features are often really buggy to start with and your customers won’t care. It likely need to be ready by September 1. So be careful how much you bite off. (It was Sept 10 for iOS 7). Try to focus on what is going to cool in iOS 8, tackling lots of problems that aren’t specific to it might not make much sense. And most of all, have fun! iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #186: Dropping Bombs http://developingperspective.com/2014/06/02/0/ Mon, 02 Jun 2014 13:10:00 -0400 David http://developingperspective.com/?p=5551937299090 My initial impressions on the 2014 WWDC Keynote. Wow, it was a big one.

    ]]>
    My initial impressions on the 2014 WWDC Keynote. Wow, it was a big one.

    ]]>
    0 875 My initial impressions on the 2014 WWDC Keynote. Wow, it was a big one. My initial impressions on the 2014 WWDC Keynote. Wow, it was a big one. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #185: Pick up your Kite. http://developingperspective.com/2014/05/27/185/ Tue, 27 May 2014 13:41:00 -0400 David http://developingperspective.com/?p=555551848209185 This year I’m going to skip my usual soapbox speech about WWDC tips and etiquette. Given the way the ticket distribution played out it seems neither kind nor productive. If you are going to WWDC I commend these two

    Today I’m going to talk through a bit of my thoughts heading into WWDC. If the last episode bummed you out a bit this will hopefully put a more positive spin onto things.

    I also talk a bit about what I’m expecting/hoping to see announced next week.

    I will be in San Francisco next week and hope you meet many of you there.

    ]]>
    This year I’m going to skip my usual soapbox speech about WWDC tips and etiquette. Given the way the ticket distribution played out it seems neither kind nor productive. If you are going to WWDC I commend these two

    Today I’m going to talk through a bit of my thoughts heading into WWDC. If the last episode bummed you out a bit this will hopefully put a more positive spin onto things.

    I also talk a bit about what I’m expecting/hoping to see announced next week.

    I will be in San Francisco next week and hope you meet many of you there.

    ]]>
    0 897 This year I’m going to skip my usual soapbox speech about WWDC tips and etiquette. Given the way the ticket distribution played out it seems neither kind nor productive. If you are going to WWDC I commend these two #128: WWDC Tips and Etiquette. #53: Please, be polite at WWDC. Today I’m going to talk through a bit of my thoughts heading into WWDC. If the last episode bummed you out a bit this will hopefully put a more positive spin onto things. I also talk a bit about what I’m expecting/hoping to see announced next week. I will be in San Francisco next week and hope you meet many of you there. This year I’m going to skip my usual soapbox speech about WWDC tips and etiquette. Given the way the ticket distribution played out it seems neither kind nor productive. If you are going to WWDC I commend these two #128: WWDC Tips and Etiquette. #53: Please, be polite at WWDC. Today I’m going to talk through a bit of my thoughts heading into WWDC. If the last episode bummed you out a bit this will hopefully put a more positive spin onto things. I also talk a bit about what I’m expecting/hoping to see announced next week. I will be in San Francisco next week and hope you meet many of you there. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #184: The Middle Path? http://developingperspective.com/2014/05/16/0/ Fri, 16 May 2014 16:31:00 -0400 David http://developingperspective.com/?p=5555551141810 I wax philosophical about the future. Trying to wrestle with the uncertainty that surrounds our industry. Some products succeed, some products fail. Where will mine fall?

    ]]>
    I wax philosophical about the future. Trying to wrestle with the uncertainty that surrounds our industry. Some products succeed, some products fail. Where will mine fall?

    ]]>
    0 891 I wax philosophical about the future. Trying to wrestle with the uncertainty that surrounds our industry. Some products succeed, some products fail. Where will mine fall? I wax philosophical about the future. Trying to wrestle with the uncertainty that surrounds our industry. Some products succeed, some products fail. Where will mine fall? iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #183: Anxiety and Inertia http://developingperspective.com/2014/05/02/0/ Fri, 02 May 2014 13:46:00 -0400 David http://developingperspective.com/?p=5556352999670 My thanks to everyone who purchased a t-shirt in the last two weeks. They should be at the printer and then on their way to your door within the next week or so.

    Anxiety and Inertia

    I’ll be taking a quick break from the Unconventional Wisdom series today. I want to ruminate a bit on something more topical for my personally.

    Feed Wrangler hit its one year anniversary this past week. That accomplishment in and of itself is rather significant for me. If you have been listening to this podcast over the last year you know the trials and triumphs getting to here has involved. I wrote up my thoughts about that here if you are interested.

    The actual topic I want to discuss though isn’t directly related to Feed Wrangler. It has to do with the anxiety of sustaining a business. I’ve been making my primary living from the App Store for just shy of five years now. In that time I’ve seen it morph and change dramatically. The manner in which I have been able to make a living has necessarily required several adjustments along the way. One thing that has remained constant is the lurking sense of anxiety that tomorrow everything will fall apart and my business will fail. I’ve had that lingering fear now for five years running. From talking to other iOS developers I know I’m not alone in it.

    As a brief aside the funny thing about being independent is that this anxiety feels much more real than it does working for a larger company but I doubt if it is actually as dramatically more likely as it feels. Because there is a direct connection between your work and your success everything gets magnified. But I suspect you are roughly as likely to get laid off as you are for your business to fail.

    I’ve had to learn to deal with this fear in order to stay sane and to take the risks necessary to grow my business. It hasn’t gone away but it has become manageable, if not useful, for me.

    The key I found was to rely on what I will now pompously refer to as “Underscore’s First Law of Business Dynamics”

    On any given timeframe, the rate your business will decay roughly matches the rate it grew.

    Put another way fast up, fast down — slow up, slow down.

    I’ve seen this in my own apps time and time again. I’ll have big spikes followed by big falls, but over the long term things decay much more slowly. I’ve rarely been hit by sudden dramatic fall offs in sales unless they were preceded by big spikes. They haven’t always been at the level I’d like but even when an app falls down to just a few sales a day…it tends to stay consistent there.

    This gives me some comfort. When I look at my business today I can roughly predict how it will do by looking at the past few months. The trends over the long term might not always work out but the need for day to day worry is likely unfounded.

    ]]>
    My thanks to everyone who purchased a t-shirt in the last two weeks. They should be at the printer and then on their way to your door within the next week or so.

    Anxiety and Inertia

    I’ll be taking a quick break from the Unconventional Wisdom series today. I want to ruminate a bit on something more topical for my personally.

    Feed Wrangler hit its one year anniversary this past week. That accomplishment in and of itself is rather significant for me. If you have been listening to this podcast over the last year you know the trials and triumphs getting to here has involved. I wrote up my thoughts about that here if you are interested.

    The actual topic I want to discuss though isn’t directly related to Feed Wrangler. It has to do with the anxiety of sustaining a business. I’ve been making my primary living from the App Store for just shy of five years now. In that time I’ve seen it morph and change dramatically. The manner in which I have been able to make a living has necessarily required several adjustments along the way. One thing that has remained constant is the lurking sense of anxiety that tomorrow everything will fall apart and my business will fail. I’ve had that lingering fear now for five years running. From talking to other iOS developers I know I’m not alone in it.

    As a brief aside the funny thing about being independent is that this anxiety feels much more real than it does working for a larger company but I doubt if it is actually as dramatically more likely as it feels. Because there is a direct connection between your work and your success everything gets magnified. But I suspect you are roughly as likely to get laid off as you are for your business to fail.

    I’ve had to learn to deal with this fear in order to stay sane and to take the risks necessary to grow my business. It hasn’t gone away but it has become manageable, if not useful, for me.

    The key I found was to rely on what I will now pompously refer to as “Underscore’s First Law of Business Dynamics”

    On any given timeframe, the rate your business will decay roughly matches the rate it grew.

    Put another way fast up, fast down — slow up, slow down.

    I’ve seen this in my own apps time and time again. I’ll have big spikes followed by big falls, but over the long term things decay much more slowly. I’ve rarely been hit by sudden dramatic fall offs in sales unless they were preceded by big spikes. They haven’t always been at the level I’d like but even when an app falls down to just a few sales a day…it tends to stay consistent there.

    This gives me some comfort. When I look at my business today I can roughly predict how it will do by looking at the past few months. The trends over the long term might not always work out but the need for day to day worry is likely unfounded.

    ]]>
    0 0 My thanks to everyone who purchased a t-shirt in the last two weeks. They should be at the printer and then on their way to your door within the next week or so. Anxiety and Inertia I’ll be taking a quick break from the Unconventional Wisdom series today. I want to ruminate a bit on something more topical for my personally. Feed Wrangler hit its one year anniversary this past week. That accomplishment in and of itself is rather significant for me. If you have been listening to this podcast over the last year you know the trials and triumphs getting to here has involved. I wrote up my thoughts about that here if you are interested. The actual topic I want to discuss though isn’t directly related to Feed Wrangler. It has to do with the anxiety of sustaining a business. I’ve been making my primary living from the App Store for just shy of five years now. In that time I’ve seen it morph and change dramatically. The manner in which I have been able to make a living has necessarily required several adjustments along the way. One thing that has remained constant is the lurking sense of anxiety that tomorrow everything will fall apart and my business will fail. I’ve had that lingering fear now for five years running. From talking to other iOS developers I know I’m not alone in it. As a brief aside the funny thing about being independent is that this anxiety feels much more real than it does working for a larger company but I doubt if it is actually as dramatically more likely as it feels. Because there is a direct connection between your work and your success everything gets magnified. But I suspect you are roughly as likely to get laid off as you are for your business to fail. I’ve had to learn to deal with this fear in order to stay sane and to take the risks necessary to grow my business. It hasn’t gone away but it has become manageable, if not useful, for me. The key I found was to rely on what I will now pompously refer to as “Underscore’s First Law of Business Dynamics” On any given timeframe, the rate your business will decay roughly matches the rate it grew. Put another way fast up, fast down — slow up, slow down. I’ve seen this in my own apps time and time again. I’ll have big spikes followed by big falls, but over the long term things decay much more slowly. I’ve rarely been hit by sudden dramatic fall offs in sales unless they were preceded by big spikes. They haven’t always been at the level I’d like but even when an app falls down to just a few sales a day…it tends to stay consistent there. This gives me some comfort. When I look at my business today I can roughly predict how it will do by looking at the past few months. The trends over the long term might not always work out but the need for day to day worry is likely unfounded. My thanks to everyone who purchased a t-shirt in the last two weeks. They should be at the printer and then on their way to your door within the next week or so. Anxiety and Inertia I’ll be taking a quick break from the Unconventional Wisdom series today. I want to ruminate a bit on something more topical for my personally. Feed Wrangler hit its one year anniversary this past week. That accomplishment in and of itself is rather significant for me. If you have been listening to this podcast over the last year you know the trials and triumphs getting to here has involved. I wrote up my thoughts about that here if you are interested. The actual topic I want to discuss though isn’t directly related to Feed Wrangler. It has to do with the anxiety of sustaining a business. I’ve been making my primary living from the App Store for just shy of five years now. In that time I’ve seen it morph and change dramatically. The manner in which I have been able to make a living has necessarily required several adjustments along the way. One thing that has remained constant is the lurking sense of anxiety that tomorrow everything will fall apart and my business will fail. I’ve had that lingering fear now for five years running. From talking to other iOS developers I know I’m not alone in it. As a brief aside the funny thing about being independent is that this anxiety feels much more real than it does working for a larger company but I doubt if it is actually as dramatically more likely as it feels. Because there is a direct connection between your work and your success everything gets magnified. But I suspect you are roughly as likely to get laid off as you are for your business to fail. I’ve had to learn to deal with this fear in order to stay sane and to take the risks necessary to grow my business. It hasn’t gone away but it has become manageable, if not useful, for me. The key I found was to rely on what I will now pompously refer to as “Underscore’s First Law of Business Dynamics” On any given timeframe, the rate your business will decay roughly matches the rate it grew. Put another way fast up, fast down — slow up, slow down. I’ve seen this in my own apps time and time again. I’ll have big spikes followed by big falls, but over the long term things decay much more slowly. I’ve rarely been hit by sudden dramatic fall offs in sales unless they were preceded by big spikes. They haven’t always been at the level I’d like but even when an app falls down to just a few sales a day…it tends to stay consistent there. This gives me some comfort. When I look at my business today I can roughly predict how it will do by looking at the past few months. The trends over the long term might not always work out but the need for day to day worry is likely unfounded. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #182: Unconventional Wisdom, Listen to Spock. http://developingperspective.com/2014/04/25/0/ Fri, 25 Apr 2014 09:03:00 -0400 David http://developingperspective.com/?p=5551462304050 T-shirts

    I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts.

    Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing. My thanks for the dozens of people who have already got one.

    Unconventional Wisdom

    I’m doing a series of episodes trying to take contrarian positions against conventional wisdom in software development. My goal is to challenge the assumptions we make and help us to think more critically about how we conduct our business.

    The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself.

    The second topic is customer support.

    Providing good customer support is important?

    I can’t count the number of times I have heard “the thing we pride ourselves in is our customer support” at conferences. I have so often heard people getting up and talking about how they love interacting with their customers. How this has driven their companies forward. How it is the responsible thing to do as a software engineer. I couldn’t disagree more.

    The needs of the many

    To start off my attack on the important of good customer support I’m going to start off by invoking Spock—which should likely settle the matter. The needs of the many out weigh the needs of the few. That in a nutshell is the core of the problem with providing good customer support. Every business (except perhaps VC based shops) are always operating in an environment of scarcity. You are forced to make hard decisions about how you spend your time and money. Within that context any time and energy that you are putting into customer support is necessarily taking time away from energy that you could be putting into making your product better. Helping customers individually is terribly inefficient. Hopefully your product has a large enough audience that any one person is a vanishingly small percentage of your overall customer base. Would you rather spend a few hours definitely making 99.99999% of your customer’s experience better or making it possibly better for the 0.00001%?

    Relentlessly focusing on making the product better and better also has the effect of reducing the need for one-on-one customer support.

    Horrible, unscalable hourly rate

    If your product is available in the iOS app store the revenue you receive per customer is likely pretty small. You are likely getting somewhere between $0.70 and $2.10 per user (at best). If you spend 15 minutes helping a customer out you are looking at an hourly rate of $2.80 - $8.40/hr. You’d be better off burning coffee and mispronouncing names at Starbucks. Also, how can you scale up your product with that type of cost. If you want to provide customer support for increasingly more and more customers you’ll need to hire someone to help. You are then either paying them minimum wage or taking a loss with each request.

    Worst customers

    Not to pass a judgment on the actual people using your software but the people who require your support are also necessarily your worst customers. The best customers for your business are ones who give you money then cost you the least. These are the customers you want. You want to make life as good for these people as possible. They are going to be the reason your business is able to be sustainable. To apply the 80/20 rule you want to optimize and focus on the experience of the productive 80%, not the counter productive 20%.

    You don’t need it

    I’m often struck by how most of the wildly successful apps in the App Store provide no customer support whatsoever. I’m thinking of games. You hardly ever see a game with a ‘Contact Us’ button in it. They just build a solid app, deploy it to the market and then reap the benefits of their labors. “But productivity software is different,” you say. Is it, or are we just lazily relying on customer support to fill in the holes we allow to grow in our products? In many ways the need to provide customer support is a symptom of a problem in our products. The need to provide extensive support or help to our customers necessarily means we have missed something in our development process. Maybe we should just put more effort in getting it right the first time.

    ]]>
    T-shirts

    I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts.

    Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing. My thanks for the dozens of people who have already got one.

    Unconventional Wisdom

    I’m doing a series of episodes trying to take contrarian positions against conventional wisdom in software development. My goal is to challenge the assumptions we make and help us to think more critically about how we conduct our business.

    The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself.

    The second topic is customer support.

    Providing good customer support is important?

    I can’t count the number of times I have heard “the thing we pride ourselves in is our customer support” at conferences. I have so often heard people getting up and talking about how they love interacting with their customers. How this has driven their companies forward. How it is the responsible thing to do as a software engineer. I couldn’t disagree more.

    The needs of the many

    To start off my attack on the important of good customer support I’m going to start off by invoking Spock—which should likely settle the matter. The needs of the many out weigh the needs of the few. That in a nutshell is the core of the problem with providing good customer support. Every business (except perhaps VC based shops) are always operating in an environment of scarcity. You are forced to make hard decisions about how you spend your time and money. Within that context any time and energy that you are putting into customer support is necessarily taking time away from energy that you could be putting into making your product better. Helping customers individually is terribly inefficient. Hopefully your product has a large enough audience that any one person is a vanishingly small percentage of your overall customer base. Would you rather spend a few hours definitely making 99.99999% of your customer’s experience better or making it possibly better for the 0.00001%?

    Relentlessly focusing on making the product better and better also has the effect of reducing the need for one-on-one customer support.

    Horrible, unscalable hourly rate

    If your product is available in the iOS app store the revenue you receive per customer is likely pretty small. You are likely getting somewhere between $0.70 and $2.10 per user (at best). If you spend 15 minutes helping a customer out you are looking at an hourly rate of $2.80 - $8.40/hr. You’d be better off burning coffee and mispronouncing names at Starbucks. Also, how can you scale up your product with that type of cost. If you want to provide customer support for increasingly more and more customers you’ll need to hire someone to help. You are then either paying them minimum wage or taking a loss with each request.

    Worst customers

    Not to pass a judgment on the actual people using your software but the people who require your support are also necessarily your worst customers. The best customers for your business are ones who give you money then cost you the least. These are the customers you want. You want to make life as good for these people as possible. They are going to be the reason your business is able to be sustainable. To apply the 80/20 rule you want to optimize and focus on the experience of the productive 80%, not the counter productive 20%.

    You don’t need it

    I’m often struck by how most of the wildly successful apps in the App Store provide no customer support whatsoever. I’m thinking of games. You hardly ever see a game with a ‘Contact Us’ button in it. They just build a solid app, deploy it to the market and then reap the benefits of their labors. “But productivity software is different,” you say. Is it, or are we just lazily relying on customer support to fill in the holes we allow to grow in our products? In many ways the need to provide customer support is a symptom of a problem in our products. The need to provide extensive support or help to our customers necessarily means we have missed something in our development process. Maybe we should just put more effort in getting it right the first time.

    ]]>
    0 715 T-shirts I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts. Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing. My thanks for the dozens of people who have already got one. Unconventional Wisdom I’m doing a series of episodes trying to take contrarian positions against conventional wisdom in software development. My goal is to challenge the assumptions we make and help us to think more critically about how we conduct our business. The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself. The second topic is customer support. Providing good customer support is important? I can’t count the number of times I have heard “the thing we pride ourselves in is our customer support” at conferences. I have so often heard people getting up and talking about how they love interacting with their customers. How this has driven their companies forward. How it is the responsible thing to do as a software engineer. I couldn’t disagree more. The needs of the many To start off my attack on the important of good customer support I’m going to start off by invoking Spock—which should likely settle the matter. The needs of the many out weigh the needs of the few. That in a nutshell is the core of the problem with providing good customer support. Every business (except perhaps VC based shops) are always operating in an environment of scarcity. You are forced to make hard decisions about how you spend your time and money. Within that context any time and energy that you are putting into customer support is necessarily taking time away from energy that you could be putting into making your product better. Helping customers individually is terribly inefficient. Hopefully your product has a large enough audience that any one person is a vanishingly small percentage of your overall customer base. Would you rather spend a few hours definitely making 99.99999% of your customer’s experience better or making it possibly better for the 0.00001%? Relentlessly focusing on making the product better and better also has the effect of reducing the need for one-on-one customer support. Horrible, unscalable hourly rate If your product is available in the iOS app store the revenue you receive per customer is likely pretty small. You are likely getting somewhere between $0.70 and $2.10 per user (at best). If you spend 15 minutes helping a customer out you are looking at an hourly rate of $2.80 - $8.40/hr. You’d be better off burning coffee and mispronouncing names at Starbucks. Also, how can you scale up your product with that type of cost. If you want to provide customer support for increasingly more and more customers you’ll need to hire someone to help. You are then either paying them minimum wage or taking a loss with each request. Worst customers Not to pass a judgment on the actual people using your software but the people who require your support are also necessarily your worst customers. The best customers for your business are ones who give you money then cost you the least. These are the customers you want. You want to make life as good for these people as possible. They are going to be the reason your business is able to be sustainable. To apply the 80/20 rule you want to optimize and focus on the experience of the productive 80%, not the counter productive 20%. You don’t need it I’m often struck by how most of the wildly successful apps in the App Store provide no customer support whatsoever. I’m thinking of games. You hardly ever see a game with a ‘Contact Us’ button in it. They just build a solid app, deploy it to the market and then reap the benefits of their labors. “But productivity software is different,” you say. Is it, or are we just lazily relying on customer support to fill in the holes we allow to grow in our products? In many ways the need to provide customer support is a symptom of a problem in our products. The need to provide extensive support or help to our customers necessarily means we have missed something in our development process. Maybe we should just put more effort in getting it right the first time. T-shirts I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts. Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing. My thanks for the dozens of people who have already got one. Unconventional Wisdom I’m doing a series of episodes trying to take contrarian positions against conventional wisdom in software development. My goal is to challenge the assumptions we make and help us to think more critically about how we conduct our business. The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself. The second topic is customer support. Providing good customer support is important? I can’t count the number of times I have heard “the thing we pride ourselves in is our customer support” at conferences. I have so often heard people getting up and talking about how they love interacting with their customers. How this has driven their companies forward. How it is the responsible thing to do as a software engineer. I couldn’t disagree more. The needs of the many To start off my attack on the important of good customer support I’m going to start off by invoking Spock—which should likely settle the matter. The needs of the many out weigh the needs of the few. That in a nutshell is the core of the problem with providing good customer support. Every business (except perhaps VC based shops) are always operating in an environment of scarcity. You are forced to make hard decisions about how you spend your time and money. Within that context any time and energy that you are putting into customer support is necessarily taking time away from energy that you could be putting into making your product better. Helping customers individually is terribly inefficient. Hopefully your product has a large enough audience that any one person is a vanishingly small percentage of your overall customer base. Would you rather spend a few hours definitely making 99.99999% of your customer’s experience better or making it possibly better for the 0.00001%? Relentlessly focusing on making the product better and better also has the effect of reducing the need for one-on-one customer support. Horrible, unscalable hourly rate If your product is available in the iOS app store the revenue you receive per customer is likely pretty small. You are likely getting somewhere between $0.70 and $2.10 per user (at best). If you spend 15 minutes helping a customer out you are looking at an hourly rate of $2.80 - $8.40/hr. You’d be better off burning coffee and mispronouncing names at Starbucks. Also, how can you scale up your product with that type of cost. If you want to provide customer support for increasingly more and more customers you’ll need to hire someone to help. You are then either paying them minimum wage or taking a loss with each request. Worst customers Not to pass a judgment on the actual people using your software but the people who require your support are also necessarily your worst customers. The best customers for your business are ones who give you money then cost you the least. These are the customers you want. You want to make life as good for these people as possible. They are going to be the reason your business is able to be sustainable. To apply the 80/20 rule you want to optimize and focus on the experience of the productive 80%, not the counter productive 20%. You don’t need it I’m often struck by how most of the wildly successful apps in the App Store provide no customer support whatsoever. I’m thinking of games. You hardly ever see a game with a ‘Contact Us’ button in it. They just build a solid app, deploy it to the market and then reap the benefits of their labors. “But productivity software is different,” you say. Is it, or are we just lazily relying on customer support to fill in the holes we allow to grow in our products? In many ways the need to provide customer support is a symptom of a problem in our products. The need to provide extensive support or help to our customers necessarily means we have missed something in our development process. Maybe we should just put more effort in getting it right the first time. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #181: Unconventional wisdom, pricing. http://developingperspective.com/2014/04/18/181/ Fri, 18 Apr 2014 09:41:00 -0400 David http://developingperspective.com/?p=555920655263181 T-shirts

    I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts.

    Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing .

    Wrapping up

    I have published the consolidated, summarized article for my Towards a Better App Store series.

    Unconventional Wisdom

    Today I thought it might be fun to start another series of episodes. I like doing series because then I don’t have to think so much about my topic each week. The concept I’m starting with is modeled a bit after debate exercise where you are given a topic or statement then told to take either the pro or against position. The process of having to defend either side of an argument often helps to think in ways you wouldn’t otherwise. Along those lines I’m going to try and take the intentionally contrarian position against ‘conventional wisdom’ in the software business.

    The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself.

    The first topic I’m going to attack is pricing.

    Paid software is good for customers and developers?

    When I first got into the software business nearly 6 years ago the prevailing ‘best practice’ for software sales was to charge a reasonable up front price for your product. Then provide minor update and bug-fix update patches for free. Then charge (with upgrade pricing) for each major update to the product. This model had worked pretty well for many years and had grown up in the era of boxed software. More importantly this system had been widely accepted by customers as reasonable and appropriate.

    It is, however, an awful way to sell software. For, at least, 3 reason.

    Barrier to entry

    Software typically has an extremely low marginal cost. Unless you are hosting media for your customers you can typically add one more customer to your user-base for a tiny cost. Even with things like customer support you each additional user is essentially free. As such charging a large up front amount for your software doesn’t make sense. This pricing model could only be maintained in an uncompetitive marketplace. Otherwise, you will quickly be undercut by someone else who is willing to lower their prices, to get them closer to their marginal costs.

    You are also scaring away potential customers. Often the hardest part of selling software is getting it known to potential customers. If you finally have a customer considering your product (after whatever long, drawn out marketing effort) and then you put up a barrier to them then actually getting it you are shooting yourself in the foot. That is likely your only chance to convince them to download it, make that process as easy as possible.

    Unsustainable

    The paid software model is fundamentally unsustainable. To most clearly demonstrate this imagine a world where your paid sales are going well, you’ve built up a reasonable customer-base of happy users and then suddenly your sales drop off. The reason for the drop off isn’t particularly important. You now find yourself in an extremely awkward position. You continue to have expenses and have made commitments for minor updates to your customers but have no income to back them up. You either need to start squeezing your existing users progressively harder for additional income or go out of business.

    The fundamental flaw in this model was that each purchase was necessarily short-lived. You had no plan to make a continuous income from your product. Each day you need to find more people to buy your software. A process that will be progressively harder and more expensive to do. You’ve spent all the good-will of your customers all once.

    Imagine instead a business model that is based on subscriptions or advertising. This is far better. Now your viability as a business is directly based on how used your software actually is! Should your application fall out of favor and your customers stop using it, then fine, your income drops but nobody has any commitments that you are then not following through on if you cease development. If it is wildly successful then you have a virtuous cycle of more revenue for more development.

    Horribly Abrupt

    The nature of the paid model is to get large bundles of income along with significant updates. Your sales will often then fall down dramatically thereafter. This means that you are essentially in a feast-and-famine cycle. You need to store up and be frugal enough with the days of plenty to survive through the days of want. I can say from experience this is horrifically stressful. As you chip away at your storehouse your level of comfort will dramatically reduce. While conceptually you could say that it is functionally identical to getting the same overall amount evenly over the same period, human nature says otherwise. There are few things as comforting as a dependable, consistent income. Something paid apps simply don’t provide.

    ]]>
    T-shirts

    I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts.

    Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing .

    Wrapping up

    I have published the consolidated, summarized article for my Towards a Better App Store series.

    Unconventional Wisdom

    Today I thought it might be fun to start another series of episodes. I like doing series because then I don’t have to think so much about my topic each week. The concept I’m starting with is modeled a bit after debate exercise where you are given a topic or statement then told to take either the pro or against position. The process of having to defend either side of an argument often helps to think in ways you wouldn’t otherwise. Along those lines I’m going to try and take the intentionally contrarian position against ‘conventional wisdom’ in the software business.

    The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself.

    The first topic I’m going to attack is pricing.

    Paid software is good for customers and developers?

    When I first got into the software business nearly 6 years ago the prevailing ‘best practice’ for software sales was to charge a reasonable up front price for your product. Then provide minor update and bug-fix update patches for free. Then charge (with upgrade pricing) for each major update to the product. This model had worked pretty well for many years and had grown up in the era of boxed software. More importantly this system had been widely accepted by customers as reasonable and appropriate.

    It is, however, an awful way to sell software. For, at least, 3 reason.

    Barrier to entry

    Software typically has an extremely low marginal cost. Unless you are hosting media for your customers you can typically add one more customer to your user-base for a tiny cost. Even with things like customer support you each additional user is essentially free. As such charging a large up front amount for your software doesn’t make sense. This pricing model could only be maintained in an uncompetitive marketplace. Otherwise, you will quickly be undercut by someone else who is willing to lower their prices, to get them closer to their marginal costs.

    You are also scaring away potential customers. Often the hardest part of selling software is getting it known to potential customers. If you finally have a customer considering your product (after whatever long, drawn out marketing effort) and then you put up a barrier to them then actually getting it you are shooting yourself in the foot. That is likely your only chance to convince them to download it, make that process as easy as possible.

    Unsustainable

    The paid software model is fundamentally unsustainable. To most clearly demonstrate this imagine a world where your paid sales are going well, you’ve built up a reasonable customer-base of happy users and then suddenly your sales drop off. The reason for the drop off isn’t particularly important. You now find yourself in an extremely awkward position. You continue to have expenses and have made commitments for minor updates to your customers but have no income to back them up. You either need to start squeezing your existing users progressively harder for additional income or go out of business.

    The fundamental flaw in this model was that each purchase was necessarily short-lived. You had no plan to make a continuous income from your product. Each day you need to find more people to buy your software. A process that will be progressively harder and more expensive to do. You’ve spent all the good-will of your customers all once.

    Imagine instead a business model that is based on subscriptions or advertising. This is far better. Now your viability as a business is directly based on how used your software actually is! Should your application fall out of favor and your customers stop using it, then fine, your income drops but nobody has any commitments that you are then not following through on if you cease development. If it is wildly successful then you have a virtuous cycle of more revenue for more development.

    Horribly Abrupt

    The nature of the paid model is to get large bundles of income along with significant updates. Your sales will often then fall down dramatically thereafter. This means that you are essentially in a feast-and-famine cycle. You need to store up and be frugal enough with the days of plenty to survive through the days of want. I can say from experience this is horrifically stressful. As you chip away at your storehouse your level of comfort will dramatically reduce. While conceptually you could say that it is functionally identical to getting the same overall amount evenly over the same period, human nature says otherwise. There are few things as comforting as a dependable, consistent income. Something paid apps simply don’t provide.

    ]]>
    0 900 T-shirts I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts. Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing . Wrapping up I have published the consolidated, summarized article for my Towards a Better App Store series. Unconventional Wisdom Today I thought it might be fun to start another series of episodes. I like doing series because then I don’t have to think so much about my topic each week. The concept I’m starting with is modeled a bit after debate exercise where you are given a topic or statement then told to take either the pro or against position. The process of having to defend either side of an argument often helps to think in ways you wouldn’t otherwise. Along those lines I’m going to try and take the intentionally contrarian position against ‘conventional wisdom’ in the software business. The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself. The first topic I’m going to attack is pricing. Paid software is good for customers and developers? When I first got into the software business nearly 6 years ago the prevailing ‘best practice’ for software sales was to charge a reasonable up front price for your product. Then provide minor update and bug-fix update patches for free. Then charge (with upgrade pricing) for each major update to the product. This model had worked pretty well for many years and had grown up in the era of boxed software. More importantly this system had been widely accepted by customers as reasonable and appropriate. It is, however, an awful way to sell software. For, at least, 3 reason. Barrier to entry Software typically has an extremely low marginal cost. Unless you are hosting media for your customers you can typically add one more customer to your user-base for a tiny cost. Even with things like customer support you each additional user is essentially free. As such charging a large up front amount for your software doesn’t make sense. This pricing model could only be maintained in an uncompetitive marketplace. Otherwise, you will quickly be undercut by someone else who is willing to lower their prices, to get them closer to their marginal costs. You are also scaring away potential customers. Often the hardest part of selling software is getting it known to potential customers. If you finally have a customer considering your product (after whatever long, drawn out marketing effort) and then you put up a barrier to them then actually getting it you are shooting yourself in the foot. That is likely your only chance to convince them to download it, make that process as easy as possible. Unsustainable The paid software model is fundamentally unsustainable. To most clearly demonstrate this imagine a world where your paid sales are going well, you’ve built up a reasonable customer-base of happy users and then suddenly your sales drop off. The reason for the drop off isn’t particularly important. You now find yourself in an extremely awkward position. You continue to have expenses and have made commitments for minor updates to your customers but have no income to back them up. You either need to start squeezing your existing users progressively harder for additional income or go out of business. The fundamental flaw in this model was that each purchase was necessarily short-lived. You had no plan to make a continuous income from your product. Each day you need to find more people to buy your software. A process that will be progressively harder and more expensive to do. You’ve spent all the good-will of your customers all once. Imagine instead a business model that is based on subscriptions or advertising. This is far better. Now your viability as a business is directly based on how used your software actually is! Should your application fall out of favor and your customers stop using it, then fine, your income drops but nobody has any commitments that you are then not following through on if you cease development. If it is wildly successful then you have a virtuous cycle of more revenue for more development. Horribly Abrupt The nature of the paid model is to get large bundles of income along with significant updates. Your sales will often then fall down dramatically thereafter. This means that you are essentially in a feast-and-famine cycle. You need to store up and be frugal enough with the days of plenty to survive through the days of want. I can say from experience this is horrifically stressful. As you chip away at your storehouse your level of comfort will dramatically reduce. While conceptually you could say that it is functionally identical to getting the same overall amount evenly over the same period, human nature says otherwise. There are few things as comforting as a dependable, consistent income. Something paid apps simply don’t provide. T-shirts I am doing another run of t-shirts for the show. After I did the campaign for them last fall I heard from a lot of people that they missed out. This year I’m giving the campaign a nice long run (through April 28). The shirt design this year combines three distinctly geeky things—underscores, square brackets and fixed width fonts. Shirts are $14.59 (never longer than 15 minutes). Get one at http://teespring.com/developing . Wrapping up I have published the consolidated, summarized article for my Towards a Better App Store series. Unconventional Wisdom Today I thought it might be fun to start another series of episodes. I like doing series because then I don’t have to think so much about my topic each week. The concept I’m starting with is modeled a bit after debate exercise where you are given a topic or statement then told to take either the pro or against position. The process of having to defend either side of an argument often helps to think in ways you wouldn’t otherwise. Along those lines I’m going to try and take the intentionally contrarian position against ‘conventional wisdom’ in the software business. The result is something that isn’t 100% my actual position on things but should be productive and hopefully thought provoking nevertheless. I’ll be making sweeping, un-nuanced statements for effect. As with everything in life, it is more complicated than I’m going to present it. The interesting part of being in business is navigating that nuance for yourself. The first topic I’m going to attack is pricing. Paid software is good for customers and developers? When I first got into the software business nearly 6 years ago the prevailing ‘best practice’ for software sales was to charge a reasonable up front price for your product. Then provide minor update and bug-fix update patches for free. Then charge (with upgrade pricing) for each major update to the product. This model had worked pretty well for many years and had grown up in the era of boxed software. More importantly this system had been widely accepted by customers as reasonable and appropriate. It is, however, an awful way to sell software. For, at least, 3 reason. Barrier to entry Software typically has an extremely low marginal cost. Unless you are hosting media for your customers you can typically add one more customer to your user-base for a tiny cost. Even with things like customer support you each additional user is essentially free. As such charging a large up front amount for your software doesn’t make sense. This pricing model could only be maintained in an uncompetitive marketplace. Otherwise, you will quickly be undercut by someone else who is willing to lower their prices, to get them closer to their marginal costs. You are also scaring away potential customers. Often the hardest part of selling software is getting it known to potential customers. If you finally have a customer considering your product (after whatever long, drawn out marketing effort) and then you put up a barrier to them then actually getting it you are shooting yourself in the foot. That is likely your only chance to convince them to download it, make that process as easy as possible. Unsustainable The paid software model is fundamentally unsustainable. To most clearly demonstrate this imagine a world where your paid sales are going well, you’ve built up a reasonable customer-base of happy users and then suddenly your sales drop off. The reason for the drop off isn’t particularly important. You now find yourself in an extremely awkward position. You continue to have expenses and have made commitments for minor updates to your customers but have no income to back them up. You either need to start squeezing your existing users progressively harder for additional income or go out of business. The fundamental flaw in this model was that each purchase was necessarily short-lived. You had no plan to make a continuous income from your product. Each day you need to find more people to buy your software. A process that will be progressively harder and more expensive to do. You’ve spent all the good-will of your customers all once. Imagine instead a business model that is based on subscriptions or advertising. This is far better. Now your viability as a business is directly based on how used your software actually is! Should your application fall out of favor and your customers stop using it, then fine, your income drops but nobody has any commitments that you are then not following through on if you cease development. If it is wildly successful then you have a virtuous cycle of more revenue for more development. Horribly Abrupt The nature of the paid model is to get large bundles of income along with significant updates. Your sales will often then fall down dramatically thereafter. This means that you are essentially in a feast-and-famine cycle. You need to store up and be frugal enough with the days of plenty to survive through the days of want. I can say from experience this is horrifically stressful. As you chip away at your storehouse your level of comfort will dramatically reduce. While conceptually you could say that it is functionally identical to getting the same overall amount evenly over the same period, human nature says otherwise. There are few things as comforting as a dependable, consistent income. Something paid apps simply don’t provide. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #180: Enduring Features. http://developingperspective.com/2014/04/11/180/ Fri, 11 Apr 2014 10:57:00 -0400 David http://developingperspective.com/?p=555644351478180 I hope you fared better in the WWDC lottery than I did, though I’m hopeful for a possibility of a second round on Monday (maybe?). The system and process generally went really well and I think this is likely the process we’ll see going forward. It isn’t perfect but is as good as I could imagine.

    Improving the App Store: Part 5

    Ratings

    The star rating of an application is the most important aspects of the sale experience that is outside of the developer’s direct control. It is displayed on every page and instance where your app is shown and gives the customer a general cue about the quality of your app. As such developers tend to take whatever actions they can to increase it. If this were just a question of improving the quality of their apps that would be fine but that isn’t where most developers stop off. Not to reopen the tempest about prompt dialogs, but there are a lot of potentially dubious and tricky things developers can do to try and ‘artificially’ boost their ratings. There are also some really solid, thoughtful ways to accomplish the same goal.

    My general recommendations about ways this could be improved.

    • Define a clear policy about where, how, and when applications may prompt for reviews.

    Much of the discussion around the dialog prompts stemmed from a feeling that ‘everyone was doing it’ so ‘I need to too’. The best way to reward earnest developers who are trying to optimize for their users’ experience is to level the playing field by establishing exactly what is permitted.

    • Make the rating scale a rolling, weighted average rather than just current, at least soon after updates.

    I remember when Apple changed the review score from a global average to only the current version. This was an attempt to make sure that a single buggy version didn’t forever hang around your neck. It also makes the reviews perhaps more reflective of the experience the customer should expect. The challenge though is that immediately after submitting your update your reviews all go to zero which gives the customer a very different perspective about your app. It makes it look unused or low quality. This discourages updates and encourages annoying your users with review prompts immediately after updates. Either show the overall average or a rolling, weighted average, even if only recently after update.

    Editorial

    While the role and scope of editorial (feature) coverage of the store has been steadily improving over the years I think there is still a massive amount of room to be done here. Apart from the top lists, the featured area is probably the most visible place your app can be found. Building an app with the goal of being featured incentivizes quality, thoughtful and relevant app creation. Which is great but means that the value of being featured should be less abrupt.

    • Expand the scope and frequency of editorial coverage in the Store

    It seems very odd that features are only ever updated once a week (typically thursday afternoon). New apps are added to the store constantly, updates are submitted constantly, it seems like features should be updated accordingly. I’d love to see things like ‘daily picks’/promotions or similar. Things that could potentially drive user engagement with the App Store app, checking in on what is new and interesting.

    • Make an app’s featured status visible after their initial feature

    If an app is featured I’d love to see some kind of badge or notation on its App Store page promoting its selection. Apple has already taken the time and effort to identify apps that are worth the user’s attention, why not communicate that to user’s on the actual product page for the app. Similarly I’d love to see the curated lists that Apple puts together show up as search results. For example, if you search for ‘accounting’ the featured list for “Managing your Money” would seem like a great place to present the user with some apps that might be worth initially considering. This has the added benefit of improving the quality of search results.

    Categories

    • Expand the diversity of categories associated with each app.

    Lastly I’d love to see the variety and specificity of categories you could assign to an app be expanded. The current metadata assignment into one of only 24 categories seems paltry when trying to catalog over a million individual apps. I’m sure based on the search data that Apple has at its disposal I’m sure they could subdivide of the existing categories into several useful sub-categories (much like how games are treated). This would also help improve the relevance of the top charts. Being the top app in a more niche sub-category might be genuinely useful for developers and customers alike.

    This concludes this series on the App Store.

    ]]>
    I hope you fared better in the WWDC lottery than I did, though I’m hopeful for a possibility of a second round on Monday (maybe?). The system and process generally went really well and I think this is likely the process we’ll see going forward. It isn’t perfect but is as good as I could imagine.

    Improving the App Store: Part 5

    Ratings

    The star rating of an application is the most important aspects of the sale experience that is outside of the developer’s direct control. It is displayed on every page and instance where your app is shown and gives the customer a general cue about the quality of your app. As such developers tend to take whatever actions they can to increase it. If this were just a question of improving the quality of their apps that would be fine but that isn’t where most developers stop off. Not to reopen the tempest about prompt dialogs, but there are a lot of potentially dubious and tricky things developers can do to try and ‘artificially’ boost their ratings. There are also some really solid, thoughtful ways to accomplish the same goal.

    My general recommendations about ways this could be improved.

    • Define a clear policy about where, how, and when applications may prompt for reviews.

    Much of the discussion around the dialog prompts stemmed from a feeling that ‘everyone was doing it’ so ‘I need to too’. The best way to reward earnest developers who are trying to optimize for their users’ experience is to level the playing field by establishing exactly what is permitted.

    • Make the rating scale a rolling, weighted average rather than just current, at least soon after updates.

    I remember when Apple changed the review score from a global average to only the current version. This was an attempt to make sure that a single buggy version didn’t forever hang around your neck. It also makes the reviews perhaps more reflective of the experience the customer should expect. The challenge though is that immediately after submitting your update your reviews all go to zero which gives the customer a very different perspective about your app. It makes it look unused or low quality. This discourages updates and encourages annoying your users with review prompts immediately after updates. Either show the overall average or a rolling, weighted average, even if only recently after update.

    Editorial

    While the role and scope of editorial (feature) coverage of the store has been steadily improving over the years I think there is still a massive amount of room to be done here. Apart from the top lists, the featured area is probably the most visible place your app can be found. Building an app with the goal of being featured incentivizes quality, thoughtful and relevant app creation. Which is great but means that the value of being featured should be less abrupt.

    • Expand the scope and frequency of editorial coverage in the Store

    It seems very odd that features are only ever updated once a week (typically thursday afternoon). New apps are added to the store constantly, updates are submitted constantly, it seems like features should be updated accordingly. I’d love to see things like ‘daily picks’/promotions or similar. Things that could potentially drive user engagement with the App Store app, checking in on what is new and interesting.

    • Make an app’s featured status visible after their initial feature

    If an app is featured I’d love to see some kind of badge or notation on its App Store page promoting its selection. Apple has already taken the time and effort to identify apps that are worth the user’s attention, why not communicate that to user’s on the actual product page for the app. Similarly I’d love to see the curated lists that Apple puts together show up as search results. For example, if you search for ‘accounting’ the featured list for “Managing your Money” would seem like a great place to present the user with some apps that might be worth initially considering. This has the added benefit of improving the quality of search results.

    Categories

    • Expand the diversity of categories associated with each app.

    Lastly I’d love to see the variety and specificity of categories you could assign to an app be expanded. The current metadata assignment into one of only 24 categories seems paltry when trying to catalog over a million individual apps. I’m sure based on the search data that Apple has at its disposal I’m sure they could subdivide of the existing categories into several useful sub-categories (much like how games are treated). This would also help improve the relevance of the top charts. Being the top app in a more niche sub-category might be genuinely useful for developers and customers alike.

    This concludes this series on the App Store.

    ]]>
    0 900 I hope you fared better in the WWDC lottery than I did, though I’m hopeful for a possibility of a second round on Monday (maybe?). The system and process generally went really well and I think this is likely the process we’ll see going forward. It isn’t perfect but is as good as I could imagine. Improving the App Store: Part 5 Ratings The star rating of an application is the most important aspects of the sale experience that is outside of the developer’s direct control. It is displayed on every page and instance where your app is shown and gives the customer a general cue about the quality of your app. As such developers tend to take whatever actions they can to increase it. If this were just a question of improving the quality of their apps that would be fine but that isn’t where most developers stop off. Not to reopen the tempest about prompt dialogs, but there are a lot of potentially dubious and tricky things developers can do to try and ‘artificially’ boost their ratings. There are also some really solid, thoughtful ways to accomplish the same goal. My general recommendations about ways this could be improved. Define a clear policy about where, how, and when applications may prompt for reviews. Much of the discussion around the dialog prompts stemmed from a feeling that ‘everyone was doing it’ so ‘I need to too’. The best way to reward earnest developers who are trying to optimize for their users’ experience is to level the playing field by establishing exactly what is permitted. Make the rating scale a rolling, weighted average rather than just current, at least soon after updates. I remember when Apple changed the review score from a global average to only the current version. This was an attempt to make sure that a single buggy version didn’t forever hang around your neck. It also makes the reviews perhaps more reflective of the experience the customer should expect. The challenge though is that immediately after submitting your update your reviews all go to zero which gives the customer a very different perspective about your app. It makes it look unused or low quality. This discourages updates and encourages annoying your users with review prompts immediately after updates. Either show the overall average or a rolling, weighted average, even if only recently after update. Editorial While the role and scope of editorial (feature) coverage of the store has been steadily improving over the years I think there is still a massive amount of room to be done here. Apart from the top lists, the featured area is probably the most visible place your app can be found. Building an app with the goal of being featured incentivizes quality, thoughtful and relevant app creation. Which is great but means that the value of being featured should be less abrupt. Expand the scope and frequency of editorial coverage in the Store It seems very odd that features are only ever updated once a week (typically thursday afternoon). New apps are added to the store constantly, updates are submitted constantly, it seems like features should be updated accordingly. I’d love to see things like ‘daily picks’/promotions or similar. Things that could potentially drive user engagement with the App Store app, checking in on what is new and interesting. Make an app’s featured status visible after their initial feature If an app is featured I’d love to see some kind of badge or notation on its App Store page promoting its selection. Apple has already taken the time and effort to identify apps that are worth the user’s attention, why not communicate that to user’s on the actual product page for the app. Similarly I’d love to see the curated lists that Apple puts together show up as search results. For example, if you search for ‘accounting’ the featured list for “Managing your Money” would seem like a great place to present the user with some apps that might be worth initially considering. This has the added benefit of improving the quality of search results. Categories Expand the diversity of categories associated with each app. Lastly I’d love to see the variety and specificity of categories you could assign to an app be expanded. The current metadata assignment into one of only 24 categories seems paltry when trying to catalog over a million individual apps. I’m sure based on the search data that Apple has at its disposal I’m sure they could subdivide of the existing categories into several useful sub-categories (much like how games are treated). This would also help improve the relevance of the top charts. Being the top app in a more niche sub-category might be genuinely useful for developers and customers alike. This concludes this series on the App Store. I hope you fared better in the WWDC lottery than I did, though I’m hopeful for a possibility of a second round on Monday (maybe?). The system and process generally went really well and I think this is likely the process we’ll see going forward. It isn’t perfect but is as good as I could imagine. Improving the App Store: Part 5 Ratings The star rating of an application is the most important aspects of the sale experience that is outside of the developer’s direct control. It is displayed on every page and instance where your app is shown and gives the customer a general cue about the quality of your app. As such developers tend to take whatever actions they can to increase it. If this were just a question of improving the quality of their apps that would be fine but that isn’t where most developers stop off. Not to reopen the tempest about prompt dialogs, but there are a lot of potentially dubious and tricky things developers can do to try and ‘artificially’ boost their ratings. There are also some really solid, thoughtful ways to accomplish the same goal. My general recommendations about ways this could be improved. Define a clear policy about where, how, and when applications may prompt for reviews. Much of the discussion around the dialog prompts stemmed from a feeling that ‘everyone was doing it’ so ‘I need to too’. The best way to reward earnest developers who are trying to optimize for their users’ experience is to level the playing field by establishing exactly what is permitted. Make the rating scale a rolling, weighted average rather than just current, at least soon after updates. I remember when Apple changed the review score from a global average to only the current version. This was an attempt to make sure that a single buggy version didn’t forever hang around your neck. It also makes the reviews perhaps more reflective of the experience the customer should expect. The challenge though is that immediately after submitting your update your reviews all go to zero which gives the customer a very different perspective about your app. It makes it look unused or low quality. This discourages updates and encourages annoying your users with review prompts immediately after updates. Either show the overall average or a rolling, weighted average, even if only recently after update. Editorial While the role and scope of editorial (feature) coverage of the store has been steadily improving over the years I think there is still a massive amount of room to be done here. Apart from the top lists, the featured area is probably the most visible place your app can be found. Building an app with the goal of being featured incentivizes quality, thoughtful and relevant app creation. Which is great but means that the value of being featured should be less abrupt. Expand the scope and frequency of editorial coverage in the Store It seems very odd that features are only ever updated once a week (typically thursday afternoon). New apps are added to the store constantly, updates are submitted constantly, it seems like features should be updated accordingly. I’d love to see things like ‘daily picks’/promotions or similar. Things that could potentially drive user engagement with the App Store app, checking in on what is new and interesting. Make an app’s featured status visible after their initial feature If an app is featured I’d love to see some kind of badge or notation on its App Store page promoting its selection. Apple has already taken the time and effort to identify apps that are worth the user’s attention, why not communicate that to user’s on the actual product page for the app. Similarly I’d love to see the curated lists that Apple puts together show up as search results. For example, if you search for ‘accounting’ the featured list for “Managing your Money” would seem like a great place to present the user with some apps that might be worth initially considering. This has the added benefit of improving the quality of search results. Categories Expand the diversity of categories associated with each app. Lastly I’d love to see the variety and specificity of categories you could assign to an app be expanded. The current metadata assignment into one of only 24 categories seems paltry when trying to catalog over a million individual apps. I’m sure based on the search data that Apple has at its disposal I’m sure they could subdivide of the existing categories into several useful sub-categories (much like how games are treated). This would also help improve the relevance of the top charts. Being the top app in a more niche sub-category might be genuinely useful for developers and customers alike. This concludes this series on the App Store. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #179: Avoiding the Stampede. http://developingperspective.com/2014/04/03/179/ Thu, 03 Apr 2014 16:27:00 -0400 David http://developingperspective.com/?p=555383629766179 A few words of appreciation for the new lottery based WWDC ticket sales. Get your name in the hat by Monday morning.

    Then I talk through some of the tradeoffs involved in choosing the level of abstraction to use for your web-service backends, explaining my own tendency to go pretty low level. Starting from these few posts:

    ]]>
    A few words of appreciation for the new lottery based WWDC ticket sales. Get your name in the hat by Monday morning.

    Then I talk through some of the tradeoffs involved in choosing the level of abstraction to use for your web-service backends, explaining my own tendency to go pretty low level. Starting from these few posts:

    ]]>
    0 892 A few words of appreciation for the new lottery based WWDC ticket sales. Get your name in the hat by Monday morning. Then I talk through some of the tradeoffs involved in choosing the level of abstraction to use for your web-service backends, explaining my own tendency to go pretty low level. Starting from these few posts: The Parts of Your Platform Web Hosting For App Developers On Running Your Own Servers, and Why We’re Not A few words of appreciation for the new lottery based WWDC ticket sales. Get your name in the hat by Monday morning. Then I talk through some of the tradeoffs involved in choosing the level of abstraction to use for your web-service backends, explaining my own tendency to go pretty low level. Starting from these few posts: The Parts of Your Platform Web Hosting For App Developers On Running Your Own Servers, and Why We’re Not iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #178: Customer Escape Hatches http://developingperspective.com/2014/03/27/178/ Thu, 27 Mar 2014 12:57:00 -0400 David http://developingperspective.com/?p=555321445869178 After taking credit ;) for Apple’s experiments in search improvements I dive into a few changes to the App Store that could improve doing business in the store.

    Make the App Store Refund policy more obvious

    I really don’t understand why Apple makes the refund process so opaque and awkward. I know from my own experience in physical stores that a clear and easy refund policy helps drive sales. It is far better than a ‘trial-mode’ because it sustains the value of the app (rather than giving it away for free then asking for money later). However, it still maintains that escape hatch for purchases unsure of whether they really want the app.

    I’d love two things, neither of which are actually policy changes.

    • Educate App Store customers about what the policy is and ideally phrase it in clear terms.

    I’m sure there is an internal policy within Apple customer support, but I haven’t been able to find a clear explanation of it. The legalese Terms and Conditions for the App Store states that “All sales and rentals of products are final” but that is clearly not the actual policy since people get refunds all the time. Whatever the policy is this should be clear the customers.

    • Make the process of applying for a refund clear and straightforward.

    Right now you go to reportaproblem.apple.com and then fill in a form. I’d love to see this integrated into the App Store app itself. Perhaps even into the Purchased Apps area.

    Make in-app purchases (especially consumable) more honest

    Building on a blog post I wrote last year I would love to see the App Store better inform its customers about how in-app purchases will affect their experience of an app.

    • Present a typical overall cost for an app in the App Store description

    Make it clear that when you are downloading an app that says ‘free’ next to it that you may not actually be making the less expensive choice. Also, provides a clear expectation about the type of app the user is about to interact with.

    • Show how much you have spent on the app with each new purchase.

    Be upfront with the user about how much money they have spent. Allowing them to make a more informed (and less manipulated) decision.

    Drop or reframe the Top Grossing Chart

    The Top Grossing chart was ostensibly added to help improve the visibility of higher paid apps within the store, at least that is how it appeared to me externally. If that is the goal it entirely fails to do that. Either drop the list or perhaps change it to only include paid apps, or at least exclude consumable in-app purchases from the ‘app revenue’ number.

    ]]>
    After taking credit ;) for Apple’s experiments in search improvements I dive into a few changes to the App Store that could improve doing business in the store.

    Make the App Store Refund policy more obvious

    I really don’t understand why Apple makes the refund process so opaque and awkward. I know from my own experience in physical stores that a clear and easy refund policy helps drive sales. It is far better than a ‘trial-mode’ because it sustains the value of the app (rather than giving it away for free then asking for money later). However, it still maintains that escape hatch for purchases unsure of whether they really want the app.

    I’d love two things, neither of which are actually policy changes.

    • Educate App Store customers about what the policy is and ideally phrase it in clear terms.

    I’m sure there is an internal policy within Apple customer support, but I haven’t been able to find a clear explanation of it. The legalese Terms and Conditions for the App Store states that “All sales and rentals of products are final” but that is clearly not the actual policy since people get refunds all the time. Whatever the policy is this should be clear the customers.

    • Make the process of applying for a refund clear and straightforward.

    Right now you go to reportaproblem.apple.com and then fill in a form. I’d love to see this integrated into the App Store app itself. Perhaps even into the Purchased Apps area.

    Make in-app purchases (especially consumable) more honest

    Building on a blog post I wrote last year I would love to see the App Store better inform its customers about how in-app purchases will affect their experience of an app.

    • Present a typical overall cost for an app in the App Store description

    Make it clear that when you are downloading an app that says ‘free’ next to it that you may not actually be making the less expensive choice. Also, provides a clear expectation about the type of app the user is about to interact with.

    • Show how much you have spent on the app with each new purchase.

    Be upfront with the user about how much money they have spent. Allowing them to make a more informed (and less manipulated) decision.

    Drop or reframe the Top Grossing Chart

    The Top Grossing chart was ostensibly added to help improve the visibility of higher paid apps within the store, at least that is how it appeared to me externally. If that is the goal it entirely fails to do that. Either drop the list or perhaps change it to only include paid apps, or at least exclude consumable in-app purchases from the ‘app revenue’ number.

    ]]>
    0 868 After taking credit ;) for Apple’s experiments in search improvements I dive into a few changes to the App Store that could improve doing business in the store. Make the App Store Refund policy more obvious I really don’t understand why Apple makes the refund process so opaque and awkward. I know from my own experience in physical stores that a clear and easy refund policy helps drive sales. It is far better than a ‘trial-mode’ because it sustains the value of the app (rather than giving it away for free then asking for money later). However, it still maintains that escape hatch for purchases unsure of whether they really want the app. I’d love two things, neither of which are actually policy changes. Educate App Store customers about what the policy is and ideally phrase it in clear terms. I’m sure there is an internal policy within Apple customer support, but I haven’t been able to find a clear explanation of it. The legalese Terms and Conditions for the App Store states that “All sales and rentals of products are final” but that is clearly not the actual policy since people get refunds all the time. Whatever the policy is this should be clear the customers. Make the process of applying for a refund clear and straightforward. Right now you go to reportaproblem.apple.com and then fill in a form. I’d love to see this integrated into the App Store app itself. Perhaps even into the Purchased Apps area. Make in-app purchases (especially consumable) more honest Building on a blog post I wrote last year I would love to see the App Store better inform its customers about how in-app purchases will affect their experience of an app. Present a typical overall cost for an app in the App Store description Make it clear that when you are downloading an app that says ‘free’ next to it that you may not actually be making the less expensive choice. Also, provides a clear expectation about the type of app the user is about to interact with. Show how much you have spent on the app with each new purchase. Be upfront with the user about how much money they have spent. Allowing them to make a more informed (and less manipulated) decision. Drop or reframe the Top Grossing Chart The Top Grossing chart was ostensibly added to help improve the visibility of higher paid apps within the store, at least that is how it appeared to me externally. If that is the goal it entirely fails to do that. Either drop the list or perhaps change it to only include paid apps, or at least exclude consumable in-app purchases from the ‘app revenue’ number. After taking credit ;) for Apple’s experiments in search improvements I dive into a few changes to the App Store that could improve doing business in the store. Make the App Store Refund policy more obvious I really don’t understand why Apple makes the refund process so opaque and awkward. I know from my own experience in physical stores that a clear and easy refund policy helps drive sales. It is far better than a ‘trial-mode’ because it sustains the value of the app (rather than giving it away for free then asking for money later). However, it still maintains that escape hatch for purchases unsure of whether they really want the app. I’d love two things, neither of which are actually policy changes. Educate App Store customers about what the policy is and ideally phrase it in clear terms. I’m sure there is an internal policy within Apple customer support, but I haven’t been able to find a clear explanation of it. The legalese Terms and Conditions for the App Store states that “All sales and rentals of products are final” but that is clearly not the actual policy since people get refunds all the time. Whatever the policy is this should be clear the customers. Make the process of applying for a refund clear and straightforward. Right now you go to reportaproblem.apple.com and then fill in a form. I’d love to see this integrated into the App Store app itself. Perhaps even into the Purchased Apps area. Make in-app purchases (especially consumable) more honest Building on a blog post I wrote last year I would love to see the App Store better inform its customers about how in-app purchases will affect their experience of an app. Present a typical overall cost for an app in the App Store description Make it clear that when you are downloading an app that says ‘free’ next to it that you may not actually be making the less expensive choice. Also, provides a clear expectation about the type of app the user is about to interact with. Show how much you have spent on the app with each new purchase. Be upfront with the user about how much money they have spent. Allowing them to make a more informed (and less manipulated) decision. Drop or reframe the Top Grossing Chart The Top Grossing chart was ostensibly added to help improve the visibility of higher paid apps within the store, at least that is how it appeared to me externally. If that is the goal it entirely fails to do that. Either drop the list or perhaps change it to only include paid apps, or at least exclude consumable in-app purchases from the ‘app revenue’ number. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #177: Something in Mind. http://developingperspective.com/2014/03/13/177/ Thu, 13 Mar 2014 21:50:00 -0400 David http://developingperspective.com/?p=555713817296177 I will be at NSConference next week, if you are a listener of the show please make sure you find me and say hi.

    Continuing my series of Towards a Better App Store, trying to find practical suggestions for how we could improve the App Store. Today I’m going to focus on Search.

    • Physical Design: Make the cards interface for search optional (if not eliminated).
    • Ranking: Rewards or punish applications based on objective measures. For example, recently updated, crash frequency, refund requests, reviews, etc.
    • Curation: While still algorithmically based periodically vet the most popular keywords to ensure good relevance.
    • Power Search: Add the ability to filter and manage search results to more finely tune the results.
    ]]>
    I will be at NSConference next week, if you are a listener of the show please make sure you find me and say hi.

    Continuing my series of Towards a Better App Store, trying to find practical suggestions for how we could improve the App Store. Today I’m going to focus on Search.

    • Physical Design: Make the cards interface for search optional (if not eliminated).
    • Ranking: Rewards or punish applications based on objective measures. For example, recently updated, crash frequency, refund requests, reviews, etc.
    • Curation: While still algorithmically based periodically vet the most popular keywords to ensure good relevance.
    • Power Search: Add the ability to filter and manage search results to more finely tune the results.
    ]]>
    0 836 I will be at NSConference next week, if you are a listener of the show please make sure you find me and say hi. Continuing my series of Towards a Better App Store, trying to find practical suggestions for how we could improve the App Store. Today I’m going to focus on Search. Physical Design: Make the cards interface for search optional (if not eliminated). Ranking: Rewards or punish applications based on objective measures. For example, recently updated, crash frequency, refund requests, reviews, etc. Curation: While still algorithmically based periodically vet the most popular keywords to ensure good relevance. Power Search: Add the ability to filter and manage search results to more finely tune the results. I will be at NSConference next week, if you are a listener of the show please make sure you find me and say hi. Continuing my series of Towards a Better App Store, trying to find practical suggestions for how we could improve the App Store. Today I’m going to focus on Search. Physical Design: Make the cards interface for search optional (if not eliminated). Ranking: Rewards or punish applications based on objective measures. For example, recently updated, crash frequency, refund requests, reviews, etc. Curation: While still algorithmically based periodically vet the most popular keywords to ensure good relevance. Power Search: Add the ability to filter and manage search results to more finely tune the results. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #176: Make it up in Volume http://developingperspective.com/2014/03/06/176/ Thu, 06 Mar 2014 16:41:00 -0500 David http://developingperspective.com/?p=55520807661176 Towards a Better App Store: Part 2

    Make it up in Volume

    This is Part 2 of an ongoing series trying to explore practical ways that the App Store could be better for customers. Today I’m going to talk about the Store’s size.

    The size of the App Store’s catalog is often thrown around as a valuable, useful metric for judging the heath and vitality of the ecosystem. That may have been true before a certain scale. There is value in having a diverse and deep inventory that mets every need but beyond a certain point it completely looses relevance. Duplication, ‘spamming’ and decay of older apps hurts the store more than helps it. In many ways the incredible volume of the Store is at the core of many of the other challenges it faces. App Review takes longer than developers would like. Search becomes tricky. Editorially curating new arrivals becomes daunting.

    It isn’t an easy problem to solve. How do you determine which apps should be allowed in which should not. Just how many Flappy clones should be allowed to exist in the Store? 5, 10, 1000? It isn’t just the overall size that is a problem though, the rate of increase is also increasing.

    This is only new apps approved on the store (taken from 148Apps), add to this updates and it is an incredible volume.

    Also, how many of the apps on the App Store are being actively maintained. I’d guess the number is pretty low but the old apps still stay there. Buoying the numbers but not actually providing good value to

    Aside on Apple

    For this whole series I’m going to assume that tackling the questions of making the App Store better aren’t constrained by budget nor desire. I’m going to assume that somewhere in Apple’s Profit & Loss they can find whatever resources they need to attack these challenges. Furthermore, I’m going to assume that they have a desire to make the App Store as customer friendly a place as possible. Both of these seem like reasonable things to assume but I feel I should put that out there before I begin.

    Recommendations

    I had initially gone down the road of trying to work out ways to make judgments about which apps are the ‘good’ ones and which ‘deserved’ to be in the Store. It very quickly became clear that this was nearly impossible to do. While I (personally) can look at apps on the store and say they don’t belong, based on my own tastes. This never generalized. The App Store would be worse off if it were filtered with too harsh an opinion. I had also thought of applying other external limits on the number of apps. Things like raising the cost per submission or number of new apps per developer per year. These would only really affect the current trend of re-skinned apps (which can be better addressed directly), I’d rather have things simple for the majority than punish everyone for a few bad apples.

    I’m reminded of a parenting adage. Have few rules but strictly enforce them. I think this would do much to improve the situation on the Store. The App Review Guidelines are a pretty solid set of rules. They have evolved and adapted to the times but overall they do a pretty good job of keeping out the stuff that is objectively ‘junk’. There are of course grey areas, as there should be, but I don’t have too many complaints with the guidelines we have today. The area that I think we could do much better on is the way in which they are enforced. Specifically, when they are enforced. As best I can tell, other than in exceptional cases once an app is approved it is always approved.

    #1: Apps should be required to pass approval on an ongoing basis.

    The purpose of the having app review and rules about what constitutes an acceptable app is to form and direct the content of the store in the customer’s favor. This applies to things like avoiding crashing, malware ridden software. It equally applies to establishing a baseline of design and development standards that everyone must meet. Having things like the Human Interface Guidelines (HIG) as a requirement for submissions establishes a bare minimum for quality for all apps. However, the App Store is a vibrant, ever moving ecosystem. What was acceptable a few years ago is likely not today, at least not without any adaptations. This applies most concretely to supporting new versions of iOS. Since February 1st all new submissions just be built against the latest SDK and be “optimized for iOS 7”. If that applies on the front end, it should be reapplied to the back-catalog as well.

    Exactly how this would be applied doesn’t really matter. It could be applied on a monthly, quarterly or (honestly) even annual basis. The important thing is that it would create a Store where any app a customer purchases would be assured of meeting and complying with the current set of guidelines. The stated goal of the Guidelines is to “ensure they are reliable, perform as expected, and are free of offensive material.” I believe every app on the store should meet those criteria.

    If older apps no longer meet the stated guidelines for what an app should be they should be de-listed (still available to re-download if already purchased). Leaving space on the virtual shelves for apps that provide the best possible experience for customers. This would constitute a lot of work for the App Review team, but I think it is hard to argue that the result wouldn’t be worth it for customers.

    ]]>
    Towards a Better App Store: Part 2

    Make it up in Volume

    This is Part 2 of an ongoing series trying to explore practical ways that the App Store could be better for customers. Today I’m going to talk about the Store’s size.

    The size of the App Store’s catalog is often thrown around as a valuable, useful metric for judging the heath and vitality of the ecosystem. That may have been true before a certain scale. There is value in having a diverse and deep inventory that mets every need but beyond a certain point it completely looses relevance. Duplication, ‘spamming’ and decay of older apps hurts the store more than helps it. In many ways the incredible volume of the Store is at the core of many of the other challenges it faces. App Review takes longer than developers would like. Search becomes tricky. Editorially curating new arrivals becomes daunting.

    It isn’t an easy problem to solve. How do you determine which apps should be allowed in which should not. Just how many Flappy clones should be allowed to exist in the Store? 5, 10, 1000? It isn’t just the overall size that is a problem though, the rate of increase is also increasing.

    This is only new apps approved on the store (taken from 148Apps), add to this updates and it is an incredible volume.

    Also, how many of the apps on the App Store are being actively maintained. I’d guess the number is pretty low but the old apps still stay there. Buoying the numbers but not actually providing good value to

    Aside on Apple

    For this whole series I’m going to assume that tackling the questions of making the App Store better aren’t constrained by budget nor desire. I’m going to assume that somewhere in Apple’s Profit & Loss they can find whatever resources they need to attack these challenges. Furthermore, I’m going to assume that they have a desire to make the App Store as customer friendly a place as possible. Both of these seem like reasonable things to assume but I feel I should put that out there before I begin.

    Recommendations

    I had initially gone down the road of trying to work out ways to make judgments about which apps are the ‘good’ ones and which ‘deserved’ to be in the Store. It very quickly became clear that this was nearly impossible to do. While I (personally) can look at apps on the store and say they don’t belong, based on my own tastes. This never generalized. The App Store would be worse off if it were filtered with too harsh an opinion. I had also thought of applying other external limits on the number of apps. Things like raising the cost per submission or number of new apps per developer per year. These would only really affect the current trend of re-skinned apps (which can be better addressed directly), I’d rather have things simple for the majority than punish everyone for a few bad apples.

    I’m reminded of a parenting adage. Have few rules but strictly enforce them. I think this would do much to improve the situation on the Store. The App Review Guidelines are a pretty solid set of rules. They have evolved and adapted to the times but overall they do a pretty good job of keeping out the stuff that is objectively ‘junk’. There are of course grey areas, as there should be, but I don’t have too many complaints with the guidelines we have today. The area that I think we could do much better on is the way in which they are enforced. Specifically, when they are enforced. As best I can tell, other than in exceptional cases once an app is approved it is always approved.

    #1: Apps should be required to pass approval on an ongoing basis.

    The purpose of the having app review and rules about what constitutes an acceptable app is to form and direct the content of the store in the customer’s favor. This applies to things like avoiding crashing, malware ridden software. It equally applies to establishing a baseline of design and development standards that everyone must meet. Having things like the Human Interface Guidelines (HIG) as a requirement for submissions establishes a bare minimum for quality for all apps. However, the App Store is a vibrant, ever moving ecosystem. What was acceptable a few years ago is likely not today, at least not without any adaptations. This applies most concretely to supporting new versions of iOS. Since February 1st all new submissions just be built against the latest SDK and be “optimized for iOS 7”. If that applies on the front end, it should be reapplied to the back-catalog as well.

    Exactly how this would be applied doesn’t really matter. It could be applied on a monthly, quarterly or (honestly) even annual basis. The important thing is that it would create a Store where any app a customer purchases would be assured of meeting and complying with the current set of guidelines. The stated goal of the Guidelines is to “ensure they are reliable, perform as expected, and are free of offensive material.” I believe every app on the store should meet those criteria.

    If older apps no longer meet the stated guidelines for what an app should be they should be de-listed (still available to re-download if already purchased). Leaving space on the virtual shelves for apps that provide the best possible experience for customers. This would constitute a lot of work for the App Review team, but I think it is hard to argue that the result wouldn’t be worth it for customers.

    ]]>
    0 0 Towards a Better App Store: Part 2 Make it up in Volume This is Part 2 of an ongoing series trying to explore practical ways that the App Store could be better for customers. Today I’m going to talk about the Store’s size. The size of the App Store’s catalog is often thrown around as a valuable, useful metric for judging the heath and vitality of the ecosystem. That may have been true before a certain scale. There is value in having a diverse and deep inventory that mets every need but beyond a certain point it completely looses relevance. Duplication, ‘spamming’ and decay of older apps hurts the store more than helps it. In many ways the incredible volume of the Store is at the core of many of the other challenges it faces. App Review takes longer than developers would like. Search becomes tricky. Editorially curating new arrivals becomes daunting. It isn’t an easy problem to solve. How do you determine which apps should be allowed in which should not. Just how many Flappy clones should be allowed to exist in the Store? 5, 10, 1000? It isn’t just the overall size that is a problem though, the rate of increase is also increasing. This is only new apps approved on the store (taken from 148Apps), add to this updates and it is an incredible volume. Also, how many of the apps on the App Store are being actively maintained. I’d guess the number is pretty low but the old apps still stay there. Buoying the numbers but not actually providing good value to Aside on Apple For this whole series I’m going to assume that tackling the questions of making the App Store better aren’t constrained by budget nor desire. I’m going to assume that somewhere in Apple’s Profit & Loss they can find whatever resources they need to attack these challenges. Furthermore, I’m going to assume that they have a desire to make the App Store as customer friendly a place as possible. Both of these seem like reasonable things to assume but I feel I should put that out there before I begin. Recommendations I had initially gone down the road of trying to work out ways to make judgments about which apps are the ‘good’ ones and which ‘deserved’ to be in the Store. It very quickly became clear that this was nearly impossible to do. While I (personally) can look at apps on the store and say they don’t belong, based on my own tastes. This never generalized. The App Store would be worse off if it were filtered with too harsh an opinion. I had also thought of applying other external limits on the number of apps. Things like raising the cost per submission or number of new apps per developer per year. These would only really affect the current trend of re-skinned apps (which can be better addressed directly), I’d rather have things simple for the majority than punish everyone for a few bad apples. I’m reminded of a parenting adage. Have few rules but strictly enforce them. I think this would do much to improve the situation on the Store. The App Review Guidelines are a pretty solid set of rules. They have evolved and adapted to the times but overall they do a pretty good job of keeping out the stuff that is objectively ‘junk’. There are of course grey areas, as there should be, but I don’t have too many complaints with the guidelines we have today. The area that I think we could do much better on is the way in which they are enforced. Specifically, when they are enforced. As best I can tell, other than in exceptional cases once an app is approved it is always approved. #1: Apps should be required to pass approval on an ongoing basis. The purpose of the having app review and rules about what constitutes an acceptable app is to form and direct the content of the store in the customer’s favor. This applies to things like avoiding crashing, malware ridden software. It equally applies to establishing a baseline of design and development standards that everyone must meet. Having things like the Human Interface Guidelines (HIG) as a requirement for submissions establishes a bare minimum for quality for all apps. However, the App Store is a vibrant, ever moving ecosystem. What was acceptable a few years ago is likely not today, at least not without any adaptations. This applies most concretely to supporting new versions of iOS. Since February 1st all new submissions just be built against the latest SDK and be “optimized for iOS 7”. If that applies on the front end, it should be reapplied to the back-catalog as well. Exactly how this would be applied doesn’t really matter. It could be applied on a monthly, quarterly or (honestly) even annual basis. The important thing is that it would create a Store where any app a customer purchases would be assured of meeting and complying with the current set of guidelines. The stated goal of the Guidelines is to “ensure they are reliable, perform as expected, and are free of offensive material.” I believe every app on the store should meet those criteria. If older apps no longer meet the stated guidelines for what an app should be they should be de-listed (still available to re-download if already purchased). Leaving space on the virtual shelves for apps that provide the best possible experience for customers. This would constitute a lot of work for the App Review team, but I think it is hard to argue that the result wouldn’t be worth it for customers. Towards a Better App Store: Part 2 Make it up in Volume This is Part 2 of an ongoing series trying to explore practical ways that the App Store could be better for customers. Today I’m going to talk about the Store’s size. The size of the App Store’s catalog is often thrown around as a valuable, useful metric for judging the heath and vitality of the ecosystem. That may have been true before a certain scale. There is value in having a diverse and deep inventory that mets every need but beyond a certain point it completely looses relevance. Duplication, ‘spamming’ and decay of older apps hurts the store more than helps it. In many ways the incredible volume of the Store is at the core of many of the other challenges it faces. App Review takes longer than developers would like. Search becomes tricky. Editorially curating new arrivals becomes daunting. It isn’t an easy problem to solve. How do you determine which apps should be allowed in which should not. Just how many Flappy clones should be allowed to exist in the Store? 5, 10, 1000? It isn’t just the overall size that is a problem though, the rate of increase is also increasing. This is only new apps approved on the store (taken from 148Apps), add to this updates and it is an incredible volume. Also, how many of the apps on the App Store are being actively maintained. I’d guess the number is pretty low but the old apps still stay there. Buoying the numbers but not actually providing good value to Aside on Apple For this whole series I’m going to assume that tackling the questions of making the App Store better aren’t constrained by budget nor desire. I’m going to assume that somewhere in Apple’s Profit & Loss they can find whatever resources they need to attack these challenges. Furthermore, I’m going to assume that they have a desire to make the App Store as customer friendly a place as possible. Both of these seem like reasonable things to assume but I feel I should put that out there before I begin. Recommendations I had initially gone down the road of trying to work out ways to make judgments about which apps are the ‘good’ ones and which ‘deserved’ to be in the Store. It very quickly became clear that this was nearly impossible to do. While I (personally) can look at apps on the store and say they don’t belong, based on my own tastes. This never generalized. The App Store would be worse off if it were filtered with too harsh an opinion. I had also thought of applying other external limits on the number of apps. Things like raising the cost per submission or number of new apps per developer per year. These would only really affect the current trend of re-skinned apps (which can be better addressed directly), I’d rather have things simple for the majority than punish everyone for a few bad apples. I’m reminded of a parenting adage. Have few rules but strictly enforce them. I think this would do much to improve the situation on the Store. The App Review Guidelines are a pretty solid set of rules. They have evolved and adapted to the times but overall they do a pretty good job of keeping out the stuff that is objectively ‘junk’. There are of course grey areas, as there should be, but I don’t have too many complaints with the guidelines we have today. The area that I think we could do much better on is the way in which they are enforced. Specifically, when they are enforced. As best I can tell, other than in exceptional cases once an app is approved it is always approved. #1: Apps should be required to pass approval on an ongoing basis. The purpose of the having app review and rules about what constitutes an acceptable app is to form and direct the content of the store in the customer’s favor. This applies to things like avoiding crashing, malware ridden software. It equally applies to establishing a baseline of design and development standards that everyone must meet. Having things like the Human Interface Guidelines (HIG) as a requirement for submissions establishes a bare minimum for quality for all apps. However, the App Store is a vibrant, ever moving ecosystem. What was acceptable a few years ago is likely not today, at least not without any adaptations. This applies most concretely to supporting new versions of iOS. Since February 1st all new submissions just be built against the latest SDK and be “optimized for iOS 7”. If that applies on the front end, it should be reapplied to the back-catalog as well. Exactly how this would be applied doesn’t really matter. It could be applied on a monthly, quarterly or (honestly) even annual basis. The important thing is that it would create a Store where any app a customer purchases would be assured of meeting and complying with the current set of guidelines. The stated goal of the Guidelines is to “ensure they are reliable, perform as expected, and are free of offensive material.” I believe every app on the store should meet those criteria. If older apps no longer meet the stated guidelines for what an app should be they should be de-listed (still available to re-download if already purchased). Leaving space on the virtual shelves for apps that provide the best possible experience for customers. This would constitute a lot of work for the App Review team, but I think it is hard to argue that the result wouldn’t be worth it for customers. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #175: Towards a Better App Store: Part 1 http://developingperspective.com/2014/02/27/0/ Thu, 27 Feb 2014 10:27:00 -0500 David http://developingperspective.com/?p=5556702835660 This begins a multi-part series on how I think we could move the App Store forward. I had initially thought this could be a single show but quickly realized that it will take quite a few 15 minute conversations to really unpack what can practically be done to make the App Store a better place.

    A note on Show Notes. I’m planning to continue the long form notes for now, but realize that they are only a taste of what is discussed in the show and not a transcript.

    The Goal

    It is perhaps a bit glib to assume that the App Store is in need of fixing. It is perhaps the most success software marketplace in history. It has facilitated the download of over 60 billion applications. It removed a tremendous amount of friction and hassle with software distribution. It has allowed the creation of a new way for customers to think about software.

    But I think it can be better. I have genuine, personal affection for the App Store. It has allowed me personally to do things I never thought possible. But (to quote myself):

    I want to believe that the App Store is a special place. I want for it to be the singularly best venue for customers to come and find innovative, well designed, quality software. Software that pushes the boundaries of what is possible and continually amazes and delights its customers. I want for there to be an aspirational pull upwards on my own development. I want to feel like I need to work extra hard to make sure my apps meet the high standards my customers have been trained to expect.

    I don’t think the App Store lives up to these projected goals, but I think it could.

    When trying to think of the areas and ways in which the App Store could be improved it is likely not productive to think from a developer’s point of view. In all cases for the App Store to be successful it needs to be customer oriented. I need a target towards which to aim. With this in mind I started out with the goal making an app store that:

    Helps customers find quality apps to fill their current need as quickly as possible.

    That need could be specific (I need to listen to a podcast) or general (I’m bored, What fun apps have come out recently). In either case the goal of the App Store should be to help customers find a robust, quality app in as few taps as possible. Stated in the converse it would minimize customer confusion, disappointment and regret.

    Generally speaking this will also help out developers. Many discussions of what would make the App Store better tend to focus around a theoretical divide between “Good” developers and “Bad” developers. I know I myself have fallen into this stereotyping, but it is unlikely to be productive when considering a broader context. There are some behaviors that we can likely all agree are undesirable (copyright infringement, deceptive marketing, etc) but beyond that it is constructive to start with an assumption that all apps enter the store equal and are differentiated based on the market itself not our own notions.

    The Problems

    Over the next few weeks I plan to unpack ways this could improve in the following areas:

    • Catalog Size
    • Business Models
    • Search
    • Ratings
    • Editorial
    • Categories
    • Top Charts
    ]]>
    This begins a multi-part series on how I think we could move the App Store forward. I had initially thought this could be a single show but quickly realized that it will take quite a few 15 minute conversations to really unpack what can practically be done to make the App Store a better place.

    A note on Show Notes. I’m planning to continue the long form notes for now, but realize that they are only a taste of what is discussed in the show and not a transcript.

    The Goal

    It is perhaps a bit glib to assume that the App Store is in need of fixing. It is perhaps the most success software marketplace in history. It has facilitated the download of over 60 billion applications. It removed a tremendous amount of friction and hassle with software distribution. It has allowed the creation of a new way for customers to think about software.

    But I think it can be better. I have genuine, personal affection for the App Store. It has allowed me personally to do things I never thought possible. But (to quote myself):

    I want to believe that the App Store is a special place. I want for it to be the singularly best venue for customers to come and find innovative, well designed, quality software. Software that pushes the boundaries of what is possible and continually amazes and delights its customers. I want for there to be an aspirational pull upwards on my own development. I want to feel like I need to work extra hard to make sure my apps meet the high standards my customers have been trained to expect.

    I don’t think the App Store lives up to these projected goals, but I think it could.

    When trying to think of the areas and ways in which the App Store could be improved it is likely not productive to think from a developer’s point of view. In all cases for the App Store to be successful it needs to be customer oriented. I need a target towards which to aim. With this in mind I started out with the goal making an app store that:

    Helps customers find quality apps to fill their current need as quickly as possible.

    That need could be specific (I need to listen to a podcast) or general (I’m bored, What fun apps have come out recently). In either case the goal of the App Store should be to help customers find a robust, quality app in as few taps as possible. Stated in the converse it would minimize customer confusion, disappointment and regret.

    Generally speaking this will also help out developers. Many discussions of what would make the App Store better tend to focus around a theoretical divide between “Good” developers and “Bad” developers. I know I myself have fallen into this stereotyping, but it is unlikely to be productive when considering a broader context. There are some behaviors that we can likely all agree are undesirable (copyright infringement, deceptive marketing, etc) but beyond that it is constructive to start with an assumption that all apps enter the store equal and are differentiated based on the market itself not our own notions.

    The Problems

    Over the next few weeks I plan to unpack ways this could improve in the following areas:

    • Catalog Size
    • Business Models
    • Search
    • Ratings
    • Editorial
    • Categories
    • Top Charts
    ]]>
    0 900 This begins a multi-part series on how I think we could move the App Store forward. I had initially thought this could be a single show but quickly realized that it will take quite a few 15 minute conversations to really unpack what can practically be done to make the App Store a better place. A note on Show Notes. I’m planning to continue the long form notes for now, but realize that they are only a taste of what is discussed in the show and not a transcript. The Goal It is perhaps a bit glib to assume that the App Store is in need of fixing. It is perhaps the most success software marketplace in history. It has facilitated the download of over 60 billion applications. It removed a tremendous amount of friction and hassle with software distribution. It has allowed the creation of a new way for customers to think about software. But I think it can be better. I have genuine, personal affection for the App Store. It has allowed me personally to do things I never thought possible. But (to quote myself): I want to believe that the App Store is a special place. I want for it to be the singularly best venue for customers to come and find innovative, well designed, quality software. Software that pushes the boundaries of what is possible and continually amazes and delights its customers. I want for there to be an aspirational pull upwards on my own development. I want to feel like I need to work extra hard to make sure my apps meet the high standards my customers have been trained to expect. I don’t think the App Store lives up to these projected goals, but I think it could. When trying to think of the areas and ways in which the App Store could be improved it is likely not productive to think from a developer’s point of view. In all cases for the App Store to be successful it needs to be customer oriented. I need a target towards which to aim. With this in mind I started out with the goal making an app store that: Helps customers find quality apps to fill their current need as quickly as possible. That need could be specific (I need to listen to a podcast) or general (I’m bored, What fun apps have come out recently). In either case the goal of the App Store should be to help customers find a robust, quality app in as few taps as possible. Stated in the converse it would minimize customer confusion, disappointment and regret. Generally speaking this will also help out developers. Many discussions of what would make the App Store better tend to focus around a theoretical divide between “Good” developers and “Bad” developers. I know I myself have fallen into this stereotyping, but it is unlikely to be productive when considering a broader context. There are some behaviors that we can likely all agree are undesirable (copyright infringement, deceptive marketing, etc) but beyond that it is constructive to start with an assumption that all apps enter the store equal and are differentiated based on the market itself not our own notions. The Problems Over the next few weeks I plan to unpack ways this could improve in the following areas: Catalog Size Business Models Search Ratings Editorial Categories Top Charts This begins a multi-part series on how I think we could move the App Store forward. I had initially thought this could be a single show but quickly realized that it will take quite a few 15 minute conversations to really unpack what can practically be done to make the App Store a better place. A note on Show Notes. I’m planning to continue the long form notes for now, but realize that they are only a taste of what is discussed in the show and not a transcript. The Goal It is perhaps a bit glib to assume that the App Store is in need of fixing. It is perhaps the most success software marketplace in history. It has facilitated the download of over 60 billion applications. It removed a tremendous amount of friction and hassle with software distribution. It has allowed the creation of a new way for customers to think about software. But I think it can be better. I have genuine, personal affection for the App Store. It has allowed me personally to do things I never thought possible. But (to quote myself): I want to believe that the App Store is a special place. I want for it to be the singularly best venue for customers to come and find innovative, well designed, quality software. Software that pushes the boundaries of what is possible and continually amazes and delights its customers. I want for there to be an aspirational pull upwards on my own development. I want to feel like I need to work extra hard to make sure my apps meet the high standards my customers have been trained to expect. I don’t think the App Store lives up to these projected goals, but I think it could. When trying to think of the areas and ways in which the App Store could be improved it is likely not productive to think from a developer’s point of view. In all cases for the App Store to be successful it needs to be customer oriented. I need a target towards which to aim. With this in mind I started out with the goal making an app store that: Helps customers find quality apps to fill their current need as quickly as possible. That need could be specific (I need to listen to a podcast) or general (I’m bored, What fun apps have come out recently). In either case the goal of the App Store should be to help customers find a robust, quality app in as few taps as possible. Stated in the converse it would minimize customer confusion, disappointment and regret. Generally speaking this will also help out developers. Many discussions of what would make the App Store better tend to focus around a theoretical divide between “Good” developers and “Bad” developers. I know I myself have fallen into this stereotyping, but it is unlikely to be productive when considering a broader context. There are some behaviors that we can likely all agree are undesirable (copyright infringement, deceptive marketing, etc) but beyond that it is constructive to start with an assumption that all apps enter the store equal and are differentiated based on the market itself not our own notions. The Problems Over the next few weeks I plan to unpack ways this could improve in the following areas: Catalog Size Business Models Search Ratings Editorial Categories Top Charts iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #174: A Livelihood http://developingperspective.com/2014/02/12/0/ Wed, 12 Feb 2014 09:17:00 -0500 David http://developingperspective.com/?p=5556739449980 There is something tragic about the Flappy Bird saga. The events and realities of it aren’t necessarily anything new but they showcase some of the darker sides of our industry.

    The Hate

    Things like Twitter and the short attention span culture that grows up around it have developed a mentality where it seems perfectly acceptable to tear apart other people or their work. Over the weekend I was disheartened to see so many people I know and admire passing judgement on someone they didn’t know based on 140 character messages. Guessing the motives of anyone other than your closest friends is a fools errand, and even for them it is usually a terrible idea (just ask my friends). People are complicated, fragile and valuable. Projecting into someone else’s situation and then passing degrees on how they respond isn’t nearly as productive as projecting yourself into their situation and trying to learn for yourself.

    Words have meaning and I see no clearer example of how powerful they can be than what happened to Dong Nguyen. I genuinely hope he is able to move on from this in a positive way.

    Jeff Vogel’s take on this is worth a read. He comes from a background where he has had to deal with this type of interaction. While he has a variety of good points I found his observations about the role PR companies play in business very germane to this audience. The blessing and curse of being an independent is that you often interact directly with your customers. It is impossible for this to not impact you personally and emotionally. Human nature is to dwell on the negative far more than the positive. If you aren’t careful about drawing boundaries you’ll go crazy.

    A lesson

    There are a number of more squishy lessons to learn from Flappy Bird, but there is one that is manifestly practical. Never, ever, ever share revenue numbers publicly. As soon as you throw a number out there it will be all anyone can talk about. This is a natural reaction since it is one of the only things about your unique situation that is directly comparable to theirs. That voyeuristic tendency is highly venomous. Every single article I’ve read since has thrown that number around as a core part of their justifications. Just don’t do it. While I know it can be frustrating to see y-axis without numbers or to want to learn from the experiences of others it is never a great idea, and this coming from someone who tries very hard to share my numbers, stats and results.

    Localization Results

    I published a breakdown of the impact of localizing Pedometer++. Overall it was a great success.

    A request

    I’ve never really asked for iTunes reviews, it isn’t something I think is particularly important nor something I like doing. However, the quantitative side of me really wonders if it is as important as various podcast hosts say. So I’d like to conduct a little experiment. If you have time over the next week I’d love for you to write or rate the show in iTunes. You can find it here. I’m skeptical but very curious about what an influx of reviews would do. Thank you.

    ]]>
    There is something tragic about the Flappy Bird saga. The events and realities of it aren’t necessarily anything new but they showcase some of the darker sides of our industry.

    The Hate

    Things like Twitter and the short attention span culture that grows up around it have developed a mentality where it seems perfectly acceptable to tear apart other people or their work. Over the weekend I was disheartened to see so many people I know and admire passing judgement on someone they didn’t know based on 140 character messages. Guessing the motives of anyone other than your closest friends is a fools errand, and even for them it is usually a terrible idea (just ask my friends). People are complicated, fragile and valuable. Projecting into someone else’s situation and then passing degrees on how they respond isn’t nearly as productive as projecting yourself into their situation and trying to learn for yourself.

    Words have meaning and I see no clearer example of how powerful they can be than what happened to Dong Nguyen. I genuinely hope he is able to move on from this in a positive way.

    Jeff Vogel’s take on this is worth a read. He comes from a background where he has had to deal with this type of interaction. While he has a variety of good points I found his observations about the role PR companies play in business very germane to this audience. The blessing and curse of being an independent is that you often interact directly with your customers. It is impossible for this to not impact you personally and emotionally. Human nature is to dwell on the negative far more than the positive. If you aren’t careful about drawing boundaries you’ll go crazy.

    A lesson

    There are a number of more squishy lessons to learn from Flappy Bird, but there is one that is manifestly practical. Never, ever, ever share revenue numbers publicly. As soon as you throw a number out there it will be all anyone can talk about. This is a natural reaction since it is one of the only things about your unique situation that is directly comparable to theirs. That voyeuristic tendency is highly venomous. Every single article I’ve read since has thrown that number around as a core part of their justifications. Just don’t do it. While I know it can be frustrating to see y-axis without numbers or to want to learn from the experiences of others it is never a great idea, and this coming from someone who tries very hard to share my numbers, stats and results.

    Localization Results

    I published a breakdown of the impact of localizing Pedometer++. Overall it was a great success.

    A request

    I’ve never really asked for iTunes reviews, it isn’t something I think is particularly important nor something I like doing. However, the quantitative side of me really wonders if it is as important as various podcast hosts say. So I’d like to conduct a little experiment. If you have time over the next week I’d love for you to write or rate the show in iTunes. You can find it here. I’m skeptical but very curious about what an influx of reviews would do. Thank you.

    ]]>
    0 0 There is something tragic about the Flappy Bird saga. The events and realities of it aren’t necessarily anything new but they showcase some of the darker sides of our industry. The Hate Things like Twitter and the short attention span culture that grows up around it have developed a mentality where it seems perfectly acceptable to tear apart other people or their work. Over the weekend I was disheartened to see so many people I know and admire passing judgement on someone they didn’t know based on 140 character messages. Guessing the motives of anyone other than your closest friends is a fools errand, and even for them it is usually a terrible idea (just ask my friends). People are complicated, fragile and valuable. Projecting into someone else’s situation and then passing degrees on how they respond isn’t nearly as productive as projecting yourself into their situation and trying to learn for yourself. Words have meaning and I see no clearer example of how powerful they can be than what happened to Dong Nguyen. I genuinely hope he is able to move on from this in a positive way. Jeff Vogel’s take on this is worth a read. He comes from a background where he has had to deal with this type of interaction. While he has a variety of good points I found his observations about the role PR companies play in business very germane to this audience. The blessing and curse of being an independent is that you often interact directly with your customers. It is impossible for this to not impact you personally and emotionally. Human nature is to dwell on the negative far more than the positive. If you aren’t careful about drawing boundaries you’ll go crazy. A lesson There are a number of more squishy lessons to learn from Flappy Bird, but there is one that is manifestly practical. Never, ever, ever share revenue numbers publicly. As soon as you throw a number out there it will be all anyone can talk about. This is a natural reaction since it is one of the only things about your unique situation that is directly comparable to theirs. That voyeuristic tendency is highly venomous. Every single article I’ve read since has thrown that number around as a core part of their justifications. Just don’t do it. While I know it can be frustrating to see y-axis without numbers or to want to learn from the experiences of others it is never a great idea, and this coming from someone who tries very hard to share my numbers, stats and results. Localization Results I published a breakdown of the impact of localizing Pedometer++. Overall it was a great success. A request I’ve never really asked for iTunes reviews, it isn’t something I think is particularly important nor something I like doing. However, the quantitative side of me really wonders if it is as important as various podcast hosts say. So I’d like to conduct a little experiment. If you have time over the next week I’d love for you to write or rate the show in iTunes. You can find it here. I’m skeptical but very curious about what an influx of reviews would do. Thank you. There is something tragic about the Flappy Bird saga. The events and realities of it aren’t necessarily anything new but they showcase some of the darker sides of our industry. The Hate Things like Twitter and the short attention span culture that grows up around it have developed a mentality where it seems perfectly acceptable to tear apart other people or their work. Over the weekend I was disheartened to see so many people I know and admire passing judgement on someone they didn’t know based on 140 character messages. Guessing the motives of anyone other than your closest friends is a fools errand, and even for them it is usually a terrible idea (just ask my friends). People are complicated, fragile and valuable. Projecting into someone else’s situation and then passing degrees on how they respond isn’t nearly as productive as projecting yourself into their situation and trying to learn for yourself. Words have meaning and I see no clearer example of how powerful they can be than what happened to Dong Nguyen. I genuinely hope he is able to move on from this in a positive way. Jeff Vogel’s take on this is worth a read. He comes from a background where he has had to deal with this type of interaction. While he has a variety of good points I found his observations about the role PR companies play in business very germane to this audience. The blessing and curse of being an independent is that you often interact directly with your customers. It is impossible for this to not impact you personally and emotionally. Human nature is to dwell on the negative far more than the positive. If you aren’t careful about drawing boundaries you’ll go crazy. A lesson There are a number of more squishy lessons to learn from Flappy Bird, but there is one that is manifestly practical. Never, ever, ever share revenue numbers publicly. As soon as you throw a number out there it will be all anyone can talk about. This is a natural reaction since it is one of the only things about your unique situation that is directly comparable to theirs. That voyeuristic tendency is highly venomous. Every single article I’ve read since has thrown that number around as a core part of their justifications. Just don’t do it. While I know it can be frustrating to see y-axis without numbers or to want to learn from the experiences of others it is never a great idea, and this coming from someone who tries very hard to share my numbers, stats and results. Localization Results I published a breakdown of the impact of localizing Pedometer++. Overall it was a great success. A request I’ve never really asked for iTunes reviews, it isn’t something I think is particularly important nor something I like doing. However, the quantitative side of me really wonders if it is as important as various podcast hosts say. So I’d like to conduct a little experiment. If you have time over the next week I’d love for you to write or rate the show in iTunes. You can find it here. I’m skeptical but very curious about what an influx of reviews would do. Thank you. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #173: Roses by Other Names http://developingperspective.com/2014/02/05/0/ Wed, 05 Feb 2014 10:14:00 -0500 David http://developingperspective.com/?p=5555325451360 I’m trying a new format for show notes. This is half blog post, half podcast. Let me know what you think.

    I’m not going to wade into the specifics of the Paper-on-Paper-on-Paper-on-Paper battle but I thought it was an interesting topic to address more generally. Naming is an important part of creating, launching and marketing a product. Along with your icon it is probably the single most significant part of your branding efforts. It is what people will search for and how they will tell others about your app. Here are some of the things I’ve learned from my tenure in the App Store.

    Remember folks, I’m not a lawyer. Don’t base your legal or branding choices solely on the recommendation of a 15 minute podcast.

    Considerations when choosing a name

    There are two general groups that your app’s name can fall into:

    • A unique, contrived or invented word. Some examples of this category are Groupon, YouTube, Snapchat and Pinterest. The advantage of these is that they are typically easier to defend and protect. Because you made up a word it is hard for people to claim collisions are coincidence.
    • A more generic term. Some examples of this category are Audiobooks, Paper, Flashlight and Camera. The advantage of these is that they are easily recognizable and have built in search optimization. However, they are much trickier to defend and lay claim to.

    Some App Store Realities

    • Name “squatting” is a reality of the Store. While Apple has a variety of policies in place to attempt to mitigate this it is easy for someone to lay claim to a name in the Store without really using it to sell an actual product.
    • As of today there have been 1,509,669 apps approved in the life of the App Store. With that large of a pool it is very likely that all the basic, short names have already been used for most common nouns and verbs (The Oxford English Dictionary only has around 250,000 words for comparison).
    • Name duplication is possible through a variety of means. I used to think that once a name was “claimed” it was no longer possible for another app to have the exact same name. This isn’t true. Whether by guile or glitch I’ve seen many instances where a name has been duplicated exactly.
    • Beyond direct duplication you can also indirectly duplicate an app by adding text or characters to the end of the name. Just do a search for “Flashlight” in the App Store to see what this looks like. This is often also done to improve search ranking in the Store.
    • Search optimization is an important part of getting your app in front of your customers. Your app’s name (whether just a name or name-plus-tagline) and keywords are the only texts used in search so what you choose for this is very important. This is another area where being more generic can be useful. Naming your app Camera+, Camera Awesome, or Camera Plus gives you immediate advantage for people going to the store and searching for “camera” apps.

    Higher Powers

    • Trademarks are the legal means of protecting your name and preventing customer confusion. Not everything can be trademarked, nor does getting a trademark solve all your problems.
    • As with most things involving lawyers it is only partially a question of who is “right” in a trademark dispute. It is who can fight the longest, best fight and convince the highest power to take their side. I know of many stories of “little guys” getting trampled by someone who had the budget mount legal battles that the rightful owner just couldn’t sustain.
    • Apple generally seems to have a two tier approach to disputes. When it is a clear violation of an valid, simple trademark they are very quick to act. When things start to get more gray and complicated they step back and let the parties work it out between themselves. I think this approach makes a lot of sense and while it can be frustrating if you are fighting the later case its really the most reasonable approach for them to take.

    General recommendations

    The easiest way to avoid his whole thing is to try and name your apps in as unique a manner as possible. Invent a name and then market around that. You can incorporate parts of the generic terms to make it more recognizable (e.g. Fantastical). You loose the native search optimization of this but can easily make up for that using your keywords.

    Trademark your name and hope for the best, realizing that whatever you do you may need to get a lawyer involved at some point.

    ]]>
    I’m trying a new format for show notes. This is half blog post, half podcast. Let me know what you think.

    I’m not going to wade into the specifics of the Paper-on-Paper-on-Paper-on-Paper battle but I thought it was an interesting topic to address more generally. Naming is an important part of creating, launching and marketing a product. Along with your icon it is probably the single most significant part of your branding efforts. It is what people will search for and how they will tell others about your app. Here are some of the things I’ve learned from my tenure in the App Store.

    Remember folks, I’m not a lawyer. Don’t base your legal or branding choices solely on the recommendation of a 15 minute podcast.

    Considerations when choosing a name

    There are two general groups that your app’s name can fall into:

    • A unique, contrived or invented word. Some examples of this category are Groupon, YouTube, Snapchat and Pinterest. The advantage of these is that they are typically easier to defend and protect. Because you made up a word it is hard for people to claim collisions are coincidence.
    • A more generic term. Some examples of this category are Audiobooks, Paper, Flashlight and Camera. The advantage of these is that they are easily recognizable and have built in search optimization. However, they are much trickier to defend and lay claim to.

    Some App Store Realities

    • Name “squatting” is a reality of the Store. While Apple has a variety of policies in place to attempt to mitigate this it is easy for someone to lay claim to a name in the Store without really using it to sell an actual product.
    • As of today there have been 1,509,669 apps approved in the life of the App Store. With that large of a pool it is very likely that all the basic, short names have already been used for most common nouns and verbs (The Oxford English Dictionary only has around 250,000 words for comparison).
    • Name duplication is possible through a variety of means. I used to think that once a name was “claimed” it was no longer possible for another app to have the exact same name. This isn’t true. Whether by guile or glitch I’ve seen many instances where a name has been duplicated exactly.
    • Beyond direct duplication you can also indirectly duplicate an app by adding text or characters to the end of the name. Just do a search for “Flashlight” in the App Store to see what this looks like. This is often also done to improve search ranking in the Store.
    • Search optimization is an important part of getting your app in front of your customers. Your app’s name (whether just a name or name-plus-tagline) and keywords are the only texts used in search so what you choose for this is very important. This is another area where being more generic can be useful. Naming your app Camera+, Camera Awesome, or Camera Plus gives you immediate advantage for people going to the store and searching for “camera” apps.

    Higher Powers

    • Trademarks are the legal means of protecting your name and preventing customer confusion. Not everything can be trademarked, nor does getting a trademark solve all your problems.
    • As with most things involving lawyers it is only partially a question of who is “right” in a trademark dispute. It is who can fight the longest, best fight and convince the highest power to take their side. I know of many stories of “little guys” getting trampled by someone who had the budget mount legal battles that the rightful owner just couldn’t sustain.
    • Apple generally seems to have a two tier approach to disputes. When it is a clear violation of an valid, simple trademark they are very quick to act. When things start to get more gray and complicated they step back and let the parties work it out between themselves. I think this approach makes a lot of sense and while it can be frustrating if you are fighting the later case its really the most reasonable approach for them to take.

    General recommendations

    The easiest way to avoid his whole thing is to try and name your apps in as unique a manner as possible. Invent a name and then market around that. You can incorporate parts of the generic terms to make it more recognizable (e.g. Fantastical). You loose the native search optimization of this but can easily make up for that using your keywords.

    Trademark your name and hope for the best, realizing that whatever you do you may need to get a lawyer involved at some point.

    ]]>
    0 886 I’m trying a new format for show notes. This is half blog post, half podcast. Let me know what you think. I’m not going to wade into the specifics of the Paper-on-Paper-on-Paper-on-Paper battle but I thought it was an interesting topic to address more generally. Naming is an important part of creating, launching and marketing a product. Along with your icon it is probably the single most significant part of your branding efforts. It is what people will search for and how they will tell others about your app. Here are some of the things I’ve learned from my tenure in the App Store. Remember folks, I’m not a lawyer. Don’t base your legal or branding choices solely on the recommendation of a 15 minute podcast. Considerations when choosing a name There are two general groups that your app’s name can fall into: A unique, contrived or invented word. Some examples of this category are Groupon, YouTube, Snapchat and Pinterest. The advantage of these is that they are typically easier to defend and protect. Because you made up a word it is hard for people to claim collisions are coincidence. A more generic term. Some examples of this category are Audiobooks, Paper, Flashlight and Camera. The advantage of these is that they are easily recognizable and have built in search optimization. However, they are much trickier to defend and lay claim to. Some App Store Realities Name “squatting” is a reality of the Store. While Apple has a variety of policies in place to attempt to mitigate this it is easy for someone to lay claim to a name in the Store without really using it to sell an actual product. As of today there have been 1,509,669 apps approved in the life of the App Store. With that large of a pool it is very likely that all the basic, short names have already been used for most common nouns and verbs (The Oxford English Dictionary only has around 250,000 words for comparison). Name duplication is possible through a variety of means. I used to think that once a name was “claimed” it was no longer possible for another app to have the exact same name. This isn’t true. Whether by guile or glitch I’ve seen many instances where a name has been duplicated exactly. Beyond direct duplication you can also indirectly duplicate an app by adding text or characters to the end of the name. Just do a search for “Flashlight” in the App Store to see what this looks like. This is often also done to improve search ranking in the Store. Search optimization is an important part of getting your app in front of your customers. Your app’s name (whether just a name or name-plus-tagline) and keywords are the only texts used in search so what you choose for this is very important. This is another area where being more generic can be useful. Naming your app Camera+, Camera Awesome, or Camera Plus gives you immediate advantage for people going to the store and searching for “camera” apps. Higher Powers Trademarks are the legal means of protecting your name and preventing customer confusion. Not everything can be trademarked, nor does getting a trademark solve all your problems. As with most things involving lawyers it is only partially a question of who is “right” in a trademark dispute. It is who can fight the longest, best fight and convince the highest power to take their side. I know of many stories of “little guys” getting trampled by someone who had the budget mount legal battles that the rightful owner just couldn’t sustain. Apple generally seems to have a two tier approach to disputes. When it is a clear violation of an valid, simple trademark they are very quick to act. When things start to get more gray and complicated they step back and let the parties work it out between themselves. I think this approach makes a lot of sense and while it can be frustrating if you are fighting the later case its really the most reasonable approach for them to take. General recommendations The easiest way to avoid his whole thing is to try and name your apps in as unique a manner as possible. Invent a name and then market around that. You can incorporate parts of the generic terms to make it more recognizable (e.g. Fantastical). You loose the native search optimization of this but can easily make up for that using your keywords. Trademark your name and hope for the best, realizing that whatever you do you may need to get a lawyer involved at some point. I’m trying a new format for show notes. This is half blog post, half podcast. Let me know what you think. I’m not going to wade into the specifics of the Paper-on-Paper-on-Paper-on-Paper battle but I thought it was an interesting topic to address more generally. Naming is an important part of creating, launching and marketing a product. Along with your icon it is probably the single most significant part of your branding efforts. It is what people will search for and how they will tell others about your app. Here are some of the things I’ve learned from my tenure in the App Store. Remember folks, I’m not a lawyer. Don’t base your legal or branding choices solely on the recommendation of a 15 minute podcast. Considerations when choosing a name There are two general groups that your app’s name can fall into: A unique, contrived or invented word. Some examples of this category are Groupon, YouTube, Snapchat and Pinterest. The advantage of these is that they are typically easier to defend and protect. Because you made up a word it is hard for people to claim collisions are coincidence. A more generic term. Some examples of this category are Audiobooks, Paper, Flashlight and Camera. The advantage of these is that they are easily recognizable and have built in search optimization. However, they are much trickier to defend and lay claim to. Some App Store Realities Name “squatting” is a reality of the Store. While Apple has a variety of policies in place to attempt to mitigate this it is easy for someone to lay claim to a name in the Store without really using it to sell an actual product. As of today there have been 1,509,669 apps approved in the life of the App Store. With that large of a pool it is very likely that all the basic, short names have already been used for most common nouns and verbs (The Oxford English Dictionary only has around 250,000 words for comparison). Name duplication is possible through a variety of means. I used to think that once a name was “claimed” it was no longer possible for another app to have the exact same name. This isn’t true. Whether by guile or glitch I’ve seen many instances where a name has been duplicated exactly. Beyond direct duplication you can also indirectly duplicate an app by adding text or characters to the end of the name. Just do a search for “Flashlight” in the App Store to see what this looks like. This is often also done to improve search ranking in the Store. Search optimization is an important part of getting your app in front of your customers. Your app’s name (whether just a name or name-plus-tagline) and keywords are the only texts used in search so what you choose for this is very important. This is another area where being more generic can be useful. Naming your app Camera+, Camera Awesome, or Camera Plus gives you immediate advantage for people going to the store and searching for “camera” apps. Higher Powers Trademarks are the legal means of protecting your name and preventing customer confusion. Not everything can be trademarked, nor does getting a trademark solve all your problems. As with most things involving lawyers it is only partially a question of who is “right” in a trademark dispute. It is who can fight the longest, best fight and convince the highest power to take their side. I know of many stories of “little guys” getting trampled by someone who had the budget mount legal battles that the rightful owner just couldn’t sustain. Apple generally seems to have a two tier approach to disputes. When it is a clear violation of an valid, simple trademark they are very quick to act. When things start to get more gray and complicated they step back and let the parties work it out between themselves. I think this approach makes a lot of sense and while it can be frustrating if you are fighting the later case its really the most reasonable approach for them to take. General recommendations The easiest way to avoid his whole thing is to try and name your apps in as unique a manner as possible. Invent a name and then market around that. You can incorporate parts of the generic terms to make it more recognizable (e.g. Fantastical). You loose the native search optimization of this but can easily make up for that using your keywords. Trademark your name and hope for the best, realizing that whatever you do you may need to get a lawyer involved at some point. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #172: Going Global. http://developingperspective.com/2014/02/03/0/ Mon, 03 Feb 2014 10:16:00 -0500 David http://developingperspective.com/?p=555199386070 Lessons learned from launching Pedometer++ 2.0. Stopping worrying too much about version numbers. Leaving time buffers to accommodate iTunes Connect issues. The success of localization.

    ]]>
    Lessons learned from launching Pedometer++ 2.0. Stopping worrying too much about version numbers. Leaving time buffers to accommodate iTunes Connect issues. The success of localization.

    ]]>
    0 890 Lessons learned from launching Pedometer++ 2.0. Stopping worrying too much about version numbers. Leaving time buffers to accommodate iTunes Connect issues. The success of localization. Lessons learned from launching Pedometer++ 2.0. Stopping worrying too much about version numbers. Leaving time buffers to accommodate iTunes Connect issues. The success of localization. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #171: Pros and Cons of Localization. http://developingperspective.com/2014/01/22/171/ Wed, 22 Jan 2014 15:28:00 -0500 David http://developingperspective.com/?p=55588251648171 I recently went through the process of localizing Pedometer++. Today I walk through my thought process and experience doing that. Whether you should localize isn’t always a simple question.

    ]]>
    I recently went through the process of localizing Pedometer++. Today I walk through my thought process and experience doing that. Whether you should localize isn’t always a simple question.

    ]]>
    0 890 I recently went through the process of localizing Pedometer++. Today I walk through my thought process and experience doing that. Whether you should localize isn’t always a simple question. Previous Episode on Localization WWDC Video about Localization Apple Developer Overview My Cheat Sheet for looking up Languages iTunes Connect Transporter Tethras, the service I use I recently went through the process of localizing Pedometer++. Today I walk through my thought process and experience doing that. Whether you should localize isn’t always a simple question. Previous Episode on Localization WWDC Video about Localization Apple Developer Overview My Cheat Sheet for looking up Languages iTunes Connect Transporter Tethras, the service I use iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #170(#156): Distinctiveness http://developingperspective.com/2014/01/15/170/ Wed, 15 Jan 2014 09:40:00 -0500 David http://developingperspective.com/?p=555181656611170 I’m renumbering the shows going forward. Early on the show’s history I made a few mistakes where I skipped numbers in the ordering. Now the numbers correctly reflect the number of episodes I’ve created to-date.

    I’ll be speaking at NSNorth in Ottawa, Canada. The conference runs from May 8-10.

    Today my main topic is about distinctiveness. Stemming from my experience with copy-cat apps of Pedometer++.

    ]]>
    I’m renumbering the shows going forward. Early on the show’s history I made a few mistakes where I skipped numbers in the ordering. Now the numbers correctly reflect the number of episodes I’ve created to-date.

    I’ll be speaking at NSNorth in Ottawa, Canada. The conference runs from May 8-10.

    Today my main topic is about distinctiveness. Stemming from my experience with copy-cat apps of Pedometer++.

    ]]>
    0 892 I’m renumbering the shows going forward. Early on the show’s history I made a few mistakes where I skipped numbers in the ordering. Now the numbers correctly reflect the number of episodes I’ve created to-date. I’ll be speaking at NSNorth in Ottawa, Canada. The conference runs from May 8-10. Today my main topic is about distinctiveness. Stemming from my experience with copy-cat apps of Pedometer++. I’m renumbering the shows going forward. Early on the show’s history I made a few mistakes where I skipped numbers in the ordering. Now the numbers correctly reflect the number of episodes I’ve created to-date. I’ll be speaking at NSNorth in Ottawa, Canada. The conference runs from May 8-10. Today my main topic is about distinctiveness. Stemming from my experience with copy-cat apps of Pedometer++. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #155: Headroom http://developingperspective.com/2014/01/06/155/ Mon, 06 Jan 2014 15:13:00 -0500 David http://developingperspective.com/?p=555266097994155 I took two weeks off the internet and work. Here are a few of the things I learned from the experience and the changes I’m making in my own life.

    • Invest in fewer but more personal relationships.
    • Avoid controversies.
    • Slow Down, stabilize on quality before moving forward.
    • Try to be less cynical. Read my App Store reviews. Listen to all my customers.

    The video I mentioned in the intro.

    ]]>
    I took two weeks off the internet and work. Here are a few of the things I learned from the experience and the changes I’m making in my own life.

    • Invest in fewer but more personal relationships.
    • Avoid controversies.
    • Slow Down, stabilize on quality before moving forward.
    • Try to be less cynical. Read my App Store reviews. Listen to all my customers.

    The video I mentioned in the intro.

    ]]>
    0 880 I took two weeks off the internet and work. Here are a few of the things I learned from the experience and the changes I’m making in my own life. Invest in fewer but more personal relationships. Avoid controversies. Slow Down, stabilize on quality before moving forward. Try to be less cynical. Read my App Store reviews. Listen to all my customers. The video I mentioned in the intro. App Store Distribution and Marketing for Apps I took two weeks off the internet and work. Here are a few of the things I learned from the experience and the changes I’m making in my own life. Invest in fewer but more personal relationships. Avoid controversies. Slow Down, stabilize on quality before moving forward. Try to be less cynical. Read my App Store reviews. Listen to all my customers. The video I mentioned in the intro. App Store Distribution and Marketing for Apps iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #154: Something You Are Proud Of. http://developingperspective.com/2013/12/13/154/ Fri, 13 Dec 2013 11:13:00 -0500 David http://developingperspective.com/?p=555794998259154 It matters that you can make a living — but it matters more how you make your living.

    ]]>
    It matters that you can make a living — but it matters more how you make your living.

    ]]>
    0 794 It matters that you can make a living — but it matters more how you make your living. Decisions and Tensions It matters that you can make a living — but it matters more how you make your living. Decisions and Tensions iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #153: It’s beginning to look a lot like Christmas. http://developingperspective.com/2013/12/05/153/ Thu, 05 Dec 2013 17:05:00 -0500 David http://developingperspective.com/?p=55523498042153 Talking through some of the implications of the Christmas bump in the App Store. How to prepare for it and some mistakes I’d like to avoid making again. Allowing yourself to be a bit creative and exploratory with features.

    I’ll be speaking at two conferences next spring.

    ]]>
    Talking through some of the implications of the Christmas bump in the App Store. How to prepare for it and some mistakes I’d like to avoid making again. Allowing yourself to be a bit creative and exploratory with features.

    I’ll be speaking at two conferences next spring.

    ]]>
    0 817 Talking through some of the implications of the Christmas bump in the App Store. How to prepare for it and some mistakes I’d like to avoid making again. Allowing yourself to be a bit creative and exploratory with features. I’ll be speaking at two conferences next spring. NSConf CocoaConf Talking through some of the implications of the Christmas bump in the App Store. How to prepare for it and some mistakes I’d like to avoid making again. Allowing yourself to be a bit creative and exploratory with features. I’ll be speaking at two conferences next spring. NSConf CocoaConf iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #152: Push-Pull Marketing. http://developingperspective.com/2013/11/19/152/ Tue, 19 Nov 2013 10:23:00 -0500 David http://developingperspective.com/?p=555530303753152 Looking at app marketing as a spectrum between push and pull. Each developer needs to decide how much they want to interject themselves into a potential customer’s attention. How much do you value your own attention?

    ]]>
    Looking at app marketing as a spectrum between push and pull. Each developer needs to decide how much they want to interject themselves into a potential customer’s attention. How much do you value your own attention?

    ]]>
    0 886 Looking at app marketing as a spectrum between push and pull. Each developer needs to decide how much they want to interject themselves into a potential customer’s attention. How much do you value your own attention? Looking at app marketing as a spectrum between push and pull. Each developer needs to decide how much they want to interject themselves into a potential customer’s attention. How much do you value your own attention? iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #151: A tree falls in the Woods. http://developingperspective.com/2013/11/13/151/ Wed, 13 Nov 2013 10:13:00 -0500 David http://developingperspective.com/?p=555134889105151 Some lessons and storytelling about the extended outage Feed Wrangler experienced this past weekend.

    ]]>
    Some lessons and storytelling about the extended outage Feed Wrangler experienced this past weekend.

    ]]>
    0 872 Some lessons and storytelling about the extended outage Feed Wrangler experienced this past weekend. Some lessons and storytelling about the extended outage Feed Wrangler experienced this past weekend. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #150: Five Years in the App Store http://developingperspective.com/2013/11/08/0/ Fri, 08 Nov 2013 17:27:00 -0500 David http://developingperspective.com/?p=555454924810 A retrospective on the lessons I’ve learned from 5 years working in the App Store.

    Five Years in the App Store

    ]]>
    A retrospective on the lessons I’ve learned from 5 years working in the App Store.

    Five Years in the App Store

    ]]>
    0 0 A retrospective on the lessons I’ve learned from 5 years working in the App Store. Five Years in the App Store A retrospective on the lessons I’ve learned from 5 years working in the App Store. Five Years in the App Store iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #149: Audits. http://developingperspective.com/2013/10/31/0/ Thu, 31 Oct 2013 13:45:00 -0400 David http://developingperspective.com/?p=5551903336960 An overview of my experience surviving my first government audit and how I try to take a very conservative approach to accounting and tax compliance.

    ]]>
    An overview of my experience surviving my first government audit and how I try to take a very conservative approach to accounting and tax compliance.

    ]]>
    0 815 An overview of my experience surviving my first government audit and how I try to take a very conservative approach to accounting and tax compliance. An overview of my experience surviving my first government audit and how I try to take a very conservative approach to accounting and tax compliance. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #148: Trading in Pork Bellies. http://developingperspective.com/2013/10/25/0/ Fri, 25 Oct 2013 11:14:00 -0400 David http://developingperspective.com/?p=5555146506930 A few lessons for Tuesday’s keynote. We are living in the world of commodity software. The faster we adapt and react to that the better we will be able to continue making the software we love.

    ]]>
    A few lessons for Tuesday’s keynote. We are living in the world of commodity software. The faster we adapt and react to that the better we will be able to continue making the software we love.

    ]]>
    0 840 A few lessons for Tuesday’s keynote. We are living in the world of commodity software. The faster we adapt and react to that the better we will be able to continue making the software we love. A few lessons for Tuesday’s keynote. We are living in the world of commodity software. The faster we adapt and react to that the better we will be able to continue making the software we love. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #147: Our Retina Futures. http://developingperspective.com/2013/10/18/0/ Fri, 18 Oct 2013 10:19:00 -0400 David http://developingperspective.com/?p=5557667699810 Wrap up from Cingleton. Initial reactions and thoughts about Tip Jar In-App Purchases. Some predictions and thoughts about next week’s Apple event.

    ]]>
    Wrap up from Cingleton. Initial reactions and thoughts about Tip Jar In-App Purchases. Some predictions and thoughts about next week’s Apple event.

    ]]>
    0 855 Wrap up from Cingleton. Initial reactions and thoughts about Tip Jar In-App Purchases. Some predictions and thoughts about next week’s Apple event. Wrap up from Cingleton. Initial reactions and thoughts about Tip Jar In-App Purchases. Some predictions and thoughts about next week’s Apple event. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #146: Get up, Get Moving. http://developingperspective.com/2013/10/04/0/ Fri, 04 Oct 2013 14:04:00 -0400 David http://developingperspective.com/?p=5556844949090 Looking for unique opportunities and taking risks. Embracing experimentation. The importance of getting up and moving.

    ]]>
    Looking for unique opportunities and taking risks. Embracing experimentation. The importance of getting up and moving.

    ]]>
    0 798 Looking for unique opportunities and taking risks. Embracing experimentation. The importance of getting up and moving. The Prompt: The Mind of the Underscore Pedometer++ Looking for unique opportunities and taking risks. Embracing experimentation. The importance of getting up and moving. The Prompt: The Mind of the Underscore Pedometer++ iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #145: Real World Price Dynamics with Lauren Smith. http://developingperspective.com/2013/09/27/app-store-pricing/ Fri, 27 Sep 2013 14:27:00 -0400 David http://developingperspective.com/?p=5555109114570 With all the recent discussion about App Store pricing and the sustainability of making a living from the Store I thought it might be constructive to bring actual customers into the conversation. While talking with my wife, Lauren, about what was going on our resulting discussion got interesting. I recorded it and thought I’d post it here. She sits at an interesting intersection between a typical App Store customer and someone who knows the business realities of running an indie app company.

    Please excuse my audio quality. I only have a single proper microphone, so I had her record with that while I used a USB headset.

    • We start off talking about some implications of Realmac’s decision to backpedal on the pricing structure for Clear. How the decision to offer a paid, separate upgrade creates a situation where customers are apt to seek out other alternatives. The dynamics of this seem to play out differently than doing an in-app upgrade.
    • The fear of wasting money in purchasing apps and how that can often drive people towards free apps simply because the apparent risks are so much lower. One of the implications of this fear or hesitation is that purchases made within an app are much less daunting than purchases directly from the App Store.
    • How social proof and personal recommendations can drive purchases in a way that less personal marketing never does.
    • The misconception that the App Store is stocked by Apple directly rather than by independent 3rd Party apps. This sets up unrealistic expectations with customers about what is sustainable and reasonable to expect from developers. How Apple’s decision to make the iWork suite free feeds into this perception with customers that Apps should come free with their devices with infinite free updates.
    • The role that good customer service can provide to personalize and humanize your relationship with customers. This can serve as a great avenue both for their continued support and to help give them a realistic set of expectations.
    ]]>
    With all the recent discussion about App Store pricing and the sustainability of making a living from the Store I thought it might be constructive to bring actual customers into the conversation. While talking with my wife, Lauren, about what was going on our resulting discussion got interesting. I recorded it and thought I’d post it here. She sits at an interesting intersection between a typical App Store customer and someone who knows the business realities of running an indie app company.

    Please excuse my audio quality. I only have a single proper microphone, so I had her record with that while I used a USB headset.

    • We start off talking about some implications of Realmac’s decision to backpedal on the pricing structure for Clear. How the decision to offer a paid, separate upgrade creates a situation where customers are apt to seek out other alternatives. The dynamics of this seem to play out differently than doing an in-app upgrade.
    • The fear of wasting money in purchasing apps and how that can often drive people towards free apps simply because the apparent risks are so much lower. One of the implications of this fear or hesitation is that purchases made within an app are much less daunting than purchases directly from the App Store.
    • How social proof and personal recommendations can drive purchases in a way that less personal marketing never does.
    • The misconception that the App Store is stocked by Apple directly rather than by independent 3rd Party apps. This sets up unrealistic expectations with customers about what is sustainable and reasonable to expect from developers. How Apple’s decision to make the iWork suite free feeds into this perception with customers that Apps should come free with their devices with infinite free updates.
    • The role that good customer service can provide to personalize and humanize your relationship with customers. This can serve as a great avenue both for their continued support and to help give them a realistic set of expectations.
    ]]>
    0 1351 With all the recent discussion about App Store pricing and the sustainability of making a living from the Store I thought it might be constructive to bring actual customers into the conversation. While talking with my wife, Lauren, about what was going on our resulting discussion got interesting. I recorded it and thought I’d post it here. She sits at an interesting intersection between a typical App Store customer and someone who knows the business realities of running an indie app company. Please excuse my audio quality. I only have a single proper microphone, so I had her record with that while I used a USB headset. We start off talking about some implications of Realmac’s decision to backpedal on the pricing structure for Clear. How the decision to offer a paid, separate upgrade creates a situation where customers are apt to seek out other alternatives. The dynamics of this seem to play out differently than doing an in-app upgrade. The fear of wasting money in purchasing apps and how that can often drive people towards free apps simply because the apparent risks are so much lower. One of the implications of this fear or hesitation is that purchases made within an app are much less daunting than purchases directly from the App Store. How social proof and personal recommendations can drive purchases in a way that less personal marketing never does. The misconception that the App Store is stocked by Apple directly rather than by independent 3rd Party apps. This sets up unrealistic expectations with customers about what is sustainable and reasonable to expect from developers. How Apple’s decision to make the iWork suite free feeds into this perception with customers that Apps should come free with their devices with infinite free updates. The role that good customer service can provide to personalize and humanize your relationship with customers. This can serve as a great avenue both for their continued support and to help give them a realistic set of expectations. With all the recent discussion about App Store pricing and the sustainability of making a living from the Store I thought it might be constructive to bring actual customers into the conversation. While talking with my wife, Lauren, about what was going on our resulting discussion got interesting. I recorded it and thought I’d post it here. She sits at an interesting intersection between a typical App Store customer and someone who knows the business realities of running an indie app company. Please excuse my audio quality. I only have a single proper microphone, so I had her record with that while I used a USB headset. We start off talking about some implications of Realmac’s decision to backpedal on the pricing structure for Clear. How the decision to offer a paid, separate upgrade creates a situation where customers are apt to seek out other alternatives. The dynamics of this seem to play out differently than doing an in-app upgrade. The fear of wasting money in purchasing apps and how that can often drive people towards free apps simply because the apparent risks are so much lower. One of the implications of this fear or hesitation is that purchases made within an app are much less daunting than purchases directly from the App Store. How social proof and personal recommendations can drive purchases in a way that less personal marketing never does. The misconception that the App Store is stocked by Apple directly rather than by independent 3rd Party apps. This sets up unrealistic expectations with customers about what is sustainable and reasonable to expect from developers. How Apple’s decision to make the iWork suite free feeds into this perception with customers that Apps should come free with their devices with infinite free updates. The role that good customer service can provide to personalize and humanize your relationship with customers. This can serve as a great avenue both for their continued support and to help give them a realistic set of expectations. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #144: Pod Wrangler and Getting Creative. http://developingperspective.com/2013/09/26/0/ Thu, 26 Sep 2013 16:25:00 -0400 David http://developingperspective.com/?p=5556324576000 Thursday, September 26, 2013 - Introducing Pod Wrangler. Looking for places where you have unique experiences or resources that let you make things faster or better. Getting creative for business models to adapt to the ever changing app store environment.

    ]]>
    Thursday, September 26, 2013 - Introducing Pod Wrangler. Looking for places where you have unique experiences or resources that let you make things faster or better. Getting creative for business models to adapt to the ever changing app store environment.

    ]]>
    0 889 Thursday, September 26, 2013 - Introducing Pod Wrangler. Looking for places where you have unique experiences or resources that let you make things faster or better. Getting creative for business models to adapt to the ever changing app store environment. Pod Wrangler iOS Version Stats Thursday, September 26, 2013 - Introducing Pod Wrangler. Looking for places where you have unique experiences or resources that let you make things faster or better. Getting creative for business models to adapt to the ever changing app store environment. Pod Wrangler iOS Version Stats iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #143: Bare Metal. http://developingperspective.com/2013/09/17/0/ Tue, 17 Sep 2013 10:57:00 -0400 David http://developingperspective.com/?p=20130917 As an engineer my tendency is to think that all problems are best solved by cleverness. This week I’ve learned that the reality is that I should not try to solve with cleverness that which can easily be solved with money.

    ]]>
    As an engineer my tendency is to think that all problems are best solved by cleverness. This week I’ve learned that the reality is that I should not try to solve with cleverness that which can easily be solved with money.

    ]]>
    0 896 As an engineer my tendency is to think that all problems are best solved by cleverness. This week I’ve learned that the reality is that I should not try to solve with cleverness that which can easily be solved with money. Changing a Car Tire while Driving As an engineer my tendency is to think that all problems are best solved by cleverness. This week I’ve learned that the reality is that I should not try to solve with cleverness that which can easily be solved with money. Changing a Car Tire while Driving iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #142: iPhone 5s/5c First Impressions. http://developingperspective.com/2013/09/10/142/ Tue, 10 Sep 2013 20:51:00 -0400 David http://developingperspective.com/?p=555142 Tuesday, September 10, 2013 - First Impressions on the iPhone 5s/5c event. Generally it met expectations, which makes me very happy.

    ]]>
    Tuesday, September 10, 2013 - First Impressions on the iPhone 5s/5c event. Generally it met expectations, which makes me very happy.

    ]]>
    0 748 Tuesday, September 10, 2013 - First Impressions on the iPhone 5s/5c event. Generally it met expectations, which makes me very happy. Tuesday, September 10, 2013 - First Impressions on the iPhone 5s/5c event. Generally it met expectations, which makes me very happy. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #141: Sweeping Statements with Incomplete Information. http://developingperspective.com/2013/09/06/141/ Fri, 06 Sep 2013 09:49:00 -0400 David http://developingperspective.com/?p=555141 Friday, September 06, 2013 - Taking pundit commentary with a grain of salt and a few thoughts about next week’s event.

    ]]>
    Friday, September 06, 2013 - Taking pundit commentary with a grain of salt and a few thoughts about next week’s event.

    ]]>
    0 842 Friday, September 06, 2013 - Taking pundit commentary with a grain of salt and a few thoughts about next week’s event. Developing Perspective t-shirt The Inspirational Mug Grain of Salt Origin Friday, September 06, 2013 - Taking pundit commentary with a grain of salt and a few thoughts about next week’s event. Developing Perspective t-shirt The Inspirational Mug Grain of Salt Origin iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #140: Managing Beta Testing. http://developingperspective.com/2013/08/30/140/ Fri, 30 Aug 2013 14:28:00 -0400 David http://developingperspective.com/?p=555140 Friday, August 30, 2013 - Announcing the first ever Developing Perspective t-shirt. A discussion about how I beta test my apps to get them ready for the store.

    ]]>
    Friday, August 30, 2013 - Announcing the first ever Developing Perspective t-shirt. A discussion about how I beta test my apps to get them ready for the store.

    ]]>
    0 889 Friday, August 30, 2013 - Announcing the first ever Developing Perspective t-shirt. A discussion about how I beta test my apps to get them ready for the store. Developing Perspective T-shirt HockeyApp TestFlight Friday, August 30, 2013 - Announcing the first ever Developing Perspective t-shirt. A discussion about how I beta test my apps to get them ready for the store. Developing Perspective T-shirt HockeyApp TestFlight iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #139: Transferring Apps and Affiliate Linking. http://developingperspective.com/2013/08/21/139/ Wed, 21 Aug 2013 10:11:00 -0400 David http://developingperspective.com/?p=555139 Wednesday, August 21, 2013 - Understanding the App Transfer process and an overview of Apple’s new affiliate marketing system.

    ]]>
    Wednesday, August 21, 2013 - Understanding the App Transfer process and an overview of Apple’s new affiliate marketing system.

    ]]>
    0 877 Wednesday, August 21, 2013 - Understanding the App Transfer process and an overview of Apple’s new affiliate marketing system. #72: Mistakes, Designing Icons and getting Acquired. iTunes Connect Developer Guide iTunes Affiliate Linking Wednesday, August 21, 2013 - Understanding the App Transfer process and an overview of Apple’s new affiliate marketing system. #72: Mistakes, Designing Icons and getting Acquired. iTunes Connect Developer Guide iTunes Affiliate Linking iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #138: The New World. http://developingperspective.com/2013/08/16/138/ Fri, 16 Aug 2013 12:35:00 -0400 David http://developingperspective.com/?p=555138 Friday, August 16, 2013 - Walking through the tricky decision I have made about dropping support for iOS 6 in a lot of my adds. What the new ‘cheaper’ iPhone means for developers in the App Store.

    ]]>
    Friday, August 16, 2013 - Walking through the tricky decision I have made about dropping support for iOS 6 in a lot of my adds. What the new ‘cheaper’ iPhone means for developers in the App Store.

    ]]>
    0 861 Friday, August 16, 2013 - Walking through the tricky decision I have made about dropping support for iOS 6 in a lot of my adds. What the new ‘cheaper’ iPhone means for developers in the App Store. Friday, August 16, 2013 - Walking through the tricky decision I have made about dropping support for iOS 6 in a lot of my adds. What the new ‘cheaper’ iPhone means for developers in the App Store. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #137: Catastrophic Failure http://developingperspective.com/2013/08/08/137/ Thu, 08 Aug 2013 10:49:00 -0400 David http://developingperspective.com/?p=555137 Thursday, August 08, 2013 - A behind-the-scenes look at what it was like to respond to a catastrophic database migration that took down Feed Wrangler. What happened and a few things I’ve learned from the experience. With surprise special guest.

    ]]>
    Thursday, August 08, 2013 - A behind-the-scenes look at what it was like to respond to a catastrophic database migration that took down Feed Wrangler. What happened and a few things I’ve learned from the experience. With surprise special guest.

    ]]>
    0 871 Thursday, August 08, 2013 - A behind-the-scenes look at what it was like to respond to a catastrophic database migration that took down Feed Wrangler. What happened and a few things I’ve learned from the experience. With surprise special guest. Thursday, August 08, 2013 - A behind-the-scenes look at what it was like to respond to a catastrophic database migration that took down Feed Wrangler. What happened and a few things I’ve learned from the experience. With surprise special guest. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #136: The iOS 7 Conundrum. http://developingperspective.com/2013/08/02/136/ Fri, 02 Aug 2013 11:25:00 -0400 David http://developingperspective.com/?p=555136 Friday, August 02, 2013 - The release of iOS 7 “This Fall” brings with it a number of challenges. In this episode I try to unpack the tensions between market timing and technical timing. Also, why I think I’ll be more expansive with my iOS adoption than I had originally thought.

    ]]>
    Friday, August 02, 2013 - The release of iOS 7 “This Fall” brings with it a number of challenges. In this episode I try to unpack the tensions between market timing and technical timing. Also, why I think I’ll be more expansive with my iOS adoption than I had originally thought.

    ]]>
    0 782 Friday, August 02, 2013 - The release of iOS 7 “This Fall” brings with it a number of challenges. In this episode I try to unpack the tensions between market timing and technical timing. Also, why I think I’ll be more expansive with my iOS adoption than I had originally thought. Friday, August 02, 2013 - The release of iOS 7 “This Fall” brings with it a number of challenges. In this episode I try to unpack the tensions between market timing and technical timing. Also, why I think I’ll be more expansive with my iOS adoption than I had originally thought. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #135: Choices. http://developingperspective.com/2013/07/26/135/ Fri, 26 Jul 2013 16:02:00 -0400 David http://developingperspective.com/?p=555135 Friday, July 26, 2013 - Grab-bag episode. The Developer Portal outage. Deciding the kind of business you want to run. Leverging your past solutions to new problems. Staying with it when you get stuck. Recommending the Çingleton Symposium.

    ]]>
    Friday, July 26, 2013 - Grab-bag episode. The Developer Portal outage. Deciding the kind of business you want to run. Leverging your past solutions to new problems. Staying with it when you get stuck. Recommending the Çingleton Symposium.

    ]]>
    0 893 Friday, July 26, 2013 - Grab-bag episode. The Developer Portal outage. Deciding the kind of business you want to run. Leverging your past solutions to new problems. Staying with it when you get stuck. Recommending the Çingleton Symposium. Dev Portal Status Honest In-App Purchases Çingleton Symposium 3 Friday, July 26, 2013 - Grab-bag episode. The Developer Portal outage. Deciding the kind of business you want to run. Leverging your past solutions to new problems. Staying with it when you get stuck. Recommending the Çingleton Symposium. Dev Portal Status Honest In-App Purchases Çingleton Symposium 3 iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #134: Useful Toys. http://developingperspective.com/2013/07/19/0/ Fri, 19 Jul 2013 11:42:00 -0400 David http://developingperspective.com/?p=5550 Friday, July 19, 2013 - The important and useful role that test projects can serve. How I re-wrote SimpleGram to learn about iOS 7. Using SQLite for applications where batch operations are common.

    ]]>
    Friday, July 19, 2013 - The important and useful role that test projects can serve. How I re-wrote SimpleGram to learn about iOS 7. Using SQLite for applications where batch operations are common.

    ]]>
    0 762 Friday, July 19, 2013 - The important and useful role that test projects can serve. How I re-wrote SimpleGram to learn about iOS 7. Using SQLite for applications where batch operations are common. FMDB Base Friday, July 19, 2013 - The important and useful role that test projects can serve. How I re-wrote SimpleGram to learn about iOS 7. Using SQLite for applications where batch operations are common. FMDB Base iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #133: Two Years and Principles of Solid Design. http://developingperspective.com/2013/07/12/133/ Fri, 12 Jul 2013 15:57:00 -0400 David http://developingperspective.com/?p=555133 Celebrating 2 years of Developing Perspective. 38 hours of me jabbering on about development. Thanks for putting up with me.

    Discussing a few principles of solid design that apply very strongly to iOS 7. Contrast, Repetition, Alignment & Proximity. Taken from The Non-Designer’s Design Book (3rd Edition).

    ]]>
    Celebrating 2 years of Developing Perspective. 38 hours of me jabbering on about development. Thanks for putting up with me.

    Discussing a few principles of solid design that apply very strongly to iOS 7. Contrast, Repetition, Alignment & Proximity. Taken from The Non-Designer’s Design Book (3rd Edition).

    ]]>
    0 899 Celebrating 2 years of Developing Perspective. 38 hours of me jabbering on about development. Thanks for putting up with me. Discussing a few principles of solid design that apply very strongly to iOS 7. Contrast, Repetition, Alignment & Proximity. Taken from The Non-Designer’s Design Book (3rd Edition). First Episode of Developing Perspective, 2 years ago Celebrating 2 years of Developing Perspective. 38 hours of me jabbering on about development. Thanks for putting up with me. Discussing a few principles of solid design that apply very strongly to iOS 7. Contrast, Repetition, Alignment & Proximity. Taken from The Non-Designer’s Design Book (3rd Edition). First Episode of Developing Perspective, 2 years ago iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #132: Embracing the Future. http://developingperspective.com/2013/07/05/132/ Fri, 05 Jul 2013 14:28:00 -0400 David http://developingperspective.com/?p=555132 Friday, July 05, 2013 - How to get yourself ready for iOS 7 and the changes it will bring. My strategy for using iOS 7 in my daily life. Approaching iOS 7 adoption.

    ]]>
    Friday, July 05, 2013 - How to get yourself ready for iOS 7 and the changes it will bring. My strategy for using iOS 7 in my daily life. Approaching iOS 7 adoption.

    ]]>
    0 888 Friday, July 05, 2013 - How to get yourself ready for iOS 7 and the changes it will bring. My strategy for using iOS 7 in my daily life. Approaching iOS 7 adoption. iOS 7 Redesigns Friday, July 05, 2013 - How to get yourself ready for iOS 7 and the changes it will bring. My strategy for using iOS 7 in my daily life. Approaching iOS 7 adoption. iOS 7 Redesigns iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #131: The Greatest Good for the Greatest Number. http://developingperspective.com/2013/06/28/131/ Fri, 28 Jun 2013 16:56:00 -0400 David http://developingperspective.com/?p=555131 Friday, June 28, 2013 - Some reflections on a crazy week scaling Feed Wrangler and the often difficult choices that result of trying to build good products…in a practical way.

    ]]>
    Friday, June 28, 2013 - Some reflections on a crazy week scaling Feed Wrangler and the often difficult choices that result of trying to build good products…in a practical way.

    ]]>
    0 880 Friday, June 28, 2013 - Some reflections on a crazy week scaling Feed Wrangler and the often difficult choices that result of trying to build good products…in a practical way. Pinboard Article Friday, June 28, 2013 - Some reflections on a crazy week scaling Feed Wrangler and the often difficult choices that result of trying to build good products…in a practical way. Pinboard Article iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #130: WWDC Final Impressions. http://developingperspective.com/2013/06/14/130/ Fri, 14 Jun 2013 07:58:00 -0400 David http://developingperspective.com/?p=555130 Friday, June 14, 2013 - My overall impressions from the week of WWDC 2013. Lots of opportunities and difficult decisions for developers going forward. Be bold, Be Brave.

    ]]>
    Friday, June 14, 2013 - My overall impressions from the week of WWDC 2013. Lots of opportunities and difficult decisions for developers going forward. Be bold, Be Brave.

    ]]>
    0 784 Friday, June 14, 2013 - My overall impressions from the week of WWDC 2013. Lots of opportunities and difficult decisions for developers going forward. Be bold, Be Brave. Friday, June 14, 2013 - My overall impressions from the week of WWDC 2013. Lots of opportunities and difficult decisions for developers going forward. Be bold, Be Brave. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #129: WWDC 2013 First Impressions http://developingperspective.com/2013/06/10/129/ Mon, 10 Jun 2013 14:10:00 -0400 David http://developingperspective.com/?p=555129 Monday, June 10, 2013 - My first impressions from this morning’s Keynote. I recorded this directly after the announcements so that I could talk freely before learning any NDA information.

    ]]>
    Monday, June 10, 2013 - My first impressions from this morning’s Keynote. I recorded this directly after the announcements so that I could talk freely before learning any NDA information.

    ]]>
    0 811 Monday, June 10, 2013 - My first impressions from this morning’s Keynote. I recorded this directly after the announcements so that I could talk freely before learning any NDA information. Monday, June 10, 2013 - My first impressions from this morning’s Keynote. I recorded this directly after the announcements so that I could talk freely before learning any NDA information. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #128: WWDC Tips and Etiquette. http://developingperspective.com/2013/06/06/128/ Thu, 06 Jun 2013 10:13:00 -0400 David http://developingperspective.com/?p=555128 Thursday, June 06, 2013

    General Tips

    Etiquette Soapbox

    AKA: Please, don’t be a jerk at WWDC.

    • Be thankful to the Apple engineers and employees
    • Be considerate of others and your presenter during sessions
    • Make sure all your technology is on Silent (not vibrate)
    • Please, don’t noisily pack up your stuff and leave before the presenter actually concludes.  Wait until they are done!
    • Pick up your trash
    • Be polite in line and don’t hold spaces for unreasonable numbers of people
    • Be aware and respectful of people’s time and attention
    • Don’t be a pushy salesman for your apps
    ]]>
    Thursday, June 06, 2013

    General Tips

    Etiquette Soapbox

    AKA: Please, don’t be a jerk at WWDC.

    • Be thankful to the Apple engineers and employees
    • Be considerate of others and your presenter during sessions
    • Make sure all your technology is on Silent (not vibrate)
    • Please, don’t noisily pack up your stuff and leave before the presenter actually concludes.  Wait until they are done!
    • Pick up your trash
    • Be polite in line and don’t hold spaces for unreasonable numbers of people
    • Be aware and respectful of people’s time and attention
    • Don’t be a pushy salesman for your apps
    ]]>
    0 900 Thursday, June 06, 2013 General Tips Casey’s WWDC Tips Jeff LaMarche First Timer’s Guide Pick up your badge Sunday Have questions prepared for the Labs Don’t feel like you have to do something in every slot, take care of yourself Etiquette Soapbox AKA: Please, don’t be a jerk at WWDC. Be thankful to the Apple engineers and employees Be considerate of others and your presenter during sessions Make sure all your technology is on Silent (not vibrate) Please, don’t noisily pack up your stuff and leave before the presenter actually concludes.  Wait until they are done! Pick up your trash Be polite in line and don’t hold spaces for unreasonable numbers of people Be aware and respectful of people’s time and attention Don’t be a pushy salesman for your apps Thursday, June 06, 2013 General Tips Casey’s WWDC Tips Jeff LaMarche First Timer’s Guide Pick up your badge Sunday Have questions prepared for the Labs Don’t feel like you have to do something in every slot, take care of yourself Etiquette Soapbox AKA: Please, don’t be a jerk at WWDC. Be thankful to the Apple engineers and employees Be considerate of others and your presenter during sessions Make sure all your technology is on Silent (not vibrate) Please, don’t noisily pack up your stuff and leave before the presenter actually concludes.  Wait until they are done! Pick up your trash Be polite in line and don’t hold spaces for unreasonable numbers of people Be aware and respectful of people’s time and attention Don’t be a pushy salesman for your apps iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #127: Hopes for iOS7 http://developingperspective.com/2013/05/30/127/ Thu, 30 May 2013 09:48:00 -0400 David http://developingperspective.com/?p=555127 Thursday, May 30, 2013 - Some of my hopes and desires for what will be unveiled at WWDC regarding iOS 7.

    ]]>
    Thursday, May 30, 2013 - Some of my hopes and desires for what will be unveiled at WWDC regarding iOS 7.

    ]]>
    0 892 Thursday, May 30, 2013 - Some of my hopes and desires for what will be unveiled at WWDC regarding iOS 7. Thursday, May 30, 2013 - Some of my hopes and desires for what will be unveiled at WWDC regarding iOS 7. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #126: Scaling. http://developingperspective.com/2013/05/23/126/ Thu, 23 May 2013 13:48:00 -0400 David http://developingperspective.com/?p=555126 Thursday, May 23, 2013 - A quick survey of my preparation for and process of scaling a backend webservice. Also walk through the process setting up useful monitoring.

    ]]>
    Thursday, May 23, 2013 - A quick survey of my preparation for and process of scaling a backend webservice. Also walk through the process setting up useful monitoring.

    ]]>
    0 899 Thursday, May 23, 2013 - A quick survey of my preparation for and process of scaling a backend webservice. Also walk through the process setting up useful monitoring. Thursday, May 23, 2013 - A quick survey of my preparation for and process of scaling a backend webservice. Also walk through the process setting up useful monitoring. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #125: Invisible App Store Hands. http://developingperspective.com/2013/05/17/125/ Fri, 17 May 2013 11:14:00 -0400 David http://developingperspective.com/?p=555125 Friday, May 17, 2013 - My take on our Semi-Annual discussion about App Store pricing and whether things should change in the Stores.

    ]]>
    Friday, May 17, 2013 - My take on our Semi-Annual discussion about App Store pricing and whether things should change in the Stores.

    ]]>
    0 875 Friday, May 17, 2013 - My take on our Semi-Annual discussion about App Store pricing and whether things should change in the Stores. Friday, May 17, 2013 - My take on our Semi-Annual discussion about App Store pricing and whether things should change in the Stores. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #124: Fear and Learning. http://developingperspective.com/2013/05/10/124/ Fri, 10 May 2013 09:13:00 -0400 David http://developingperspective.com/?p=555124 Friday, May 10, 2013 - My experience of fear and insecurity whenever I launch something and some of the coping mechanisms that I’ve had to developed to get over it and actually ship software.

    ]]>
    Friday, May 10, 2013 - My experience of fear and insecurity whenever I launch something and some of the coping mechanisms that I’ve had to developed to get over it and actually ship software.

    ]]>
    0 552 Friday, May 10, 2013 - My experience of fear and insecurity whenever I launch something and some of the coping mechanisms that I’ve had to developed to get over it and actually ship software. Friday, May 10, 2013 - My experience of fear and insecurity whenever I launch something and some of the coping mechanisms that I’ve had to developed to get over it and actually ship software. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #123: Introducing Feed Wrangler. http://developingperspective.com/2013/05/02/123/ Thu, 02 May 2013 15:48:00 -0400 David http://developingperspective.com/?p=555123 Thursday, May 02, 2013 - Introducing Feed Wrangler, my latest product. I talk through some of the motivations behind it and how it works. I also talk through why I chose subscription pricing for it.

    ]]>
    Thursday, May 02, 2013 - Introducing Feed Wrangler, my latest product. I talk through some of the motivations behind it and how it works. I also talk through why I chose subscription pricing for it.

    ]]>
    0 900 Thursday, May 02, 2013 - Introducing Feed Wrangler, my latest product. I talk through some of the motivations behind it and how it works. I also talk through why I chose subscription pricing for it. Feed Wrangler Briefs Thursday, May 02, 2013 - Introducing Feed Wrangler, my latest product. I talk through some of the motivations behind it and how it works. I also talk through why I chose subscription pricing for it. Feed Wrangler Briefs iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #122: A Few thoughts on WWDC 2013. http://developingperspective.com/2013/04/24/122/ Wed, 24 Apr 2013 13:35:00 -0400 David http://developingperspective.com/?p=555122 Wednesday, April 24, 2013 - A few thoughts about this mornings announcement of WWDC 2013 and the way they are handling tickets this year.

    ]]>
    Wednesday, April 24, 2013 - A few thoughts about this mornings announcement of WWDC 2013 and the way they are handling tickets this year.

    ]]>
    0 837 Wednesday, April 24, 2013 - A few thoughts about this mornings announcement of WWDC 2013 and the way they are handling tickets this year. WWDC Tickets WWDC Apple Design Awards WWDC Student Scholarships Wednesday, April 24, 2013 - A few thoughts about this mornings announcement of WWDC 2013 and the way they are handling tickets this year. WWDC Tickets WWDC Apple Design Awards WWDC Student Scholarships iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #121: Dealing with Rejection. http://developingperspective.com/2013/04/23/121/ Tue, 23 Apr 2013 11:30:00 -0400 David http://developingperspective.com/?p=555121 Tuesday, April 23, 2013 - How I deal with the app rejection process, things to look out for and how to act.

    ]]>
    Tuesday, April 23, 2013 - How I deal with the app rejection process, things to look out for and how to act.

    ]]>
    0 898 Tuesday, April 23, 2013 - How I deal with the app rejection process, things to look out for and how to act. Napkin App ADN Invite Link Tuesday, April 23, 2013 - How I deal with the app rejection process, things to look out for and how to act. Napkin App ADN Invite Link iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #120: Setting up an App Store Developer Account. http://developingperspective.com/2013/04/15/120/ Mon, 15 Apr 2013 10:38:00 -0400 David http://developingperspective.com/?p=555120 Monday, April 15, 2013 - I walk through the process of setting initially setup to distribute apps within the App Store.

    ]]>
    Monday, April 15, 2013 - I walk through the process of setting initially setup to distribute apps within the App Store.

    ]]>
    0 896 Monday, April 15, 2013 - I walk through the process of setting initially setup to distribute apps within the App Store. Apple Walkthrough Monday, April 15, 2013 - I walk through the process of setting initially setup to distribute apps within the App Store. Apple Walkthrough iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #119: Go Big or Ship? http://developingperspective.com/2013/04/12/119/ Fri, 12 Apr 2013 10:17:00 -0400 David http://developingperspective.com/?p=555119 Friday, April 12, 2013 - Thinking about App Store rejections. Building reliable, queue based app components. Whether it is better to build out everything you want or ship a small polished kernel. Linode’s memory bump halving my hosting costs.

    ]]>
    Friday, April 12, 2013 - Thinking about App Store rejections. Building reliable, queue based app components. Whether it is better to build out everything you want or ship a small polished kernel. Linode’s memory bump halving my hosting costs.

    ]]>
    0 866 Friday, April 12, 2013 - Thinking about App Store rejections. Building reliable, queue based app components. Whether it is better to build out everything you want or ship a small polished kernel. Linode’s memory bump halving my hosting costs. Linode’s New Memory Blog Post Friday, April 12, 2013 - Thinking about App Store rejections. Building reliable, queue based app components. Whether it is better to build out everything you want or ship a small polished kernel. Linode’s memory bump halving my hosting costs. Linode’s New Memory Blog Post iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #118: Ambitious. http://developingperspective.com/2013/04/09/118/ Tue, 09 Apr 2013 16:44:00 -0400 David http://developingperspective.com/?p=555118 Tuesday, April 09, 2013 - Talking through one crazy week. The wisdom or folly of attacking ambitious goals. Why you want to own your sync solution. What’s next.

    ]]>
    Tuesday, April 09, 2013 - Talking through one crazy week. The wisdom or folly of attacking ambitious goals. Why you want to own your sync solution. What’s next.

    ]]>
    0 889 Tuesday, April 09, 2013 - Talking through one crazy week. The wisdom or folly of attacking ambitious goals. Why you want to own your sync solution. What’s next. Tuesday, April 09, 2013 - Talking through one crazy week. The wisdom or folly of attacking ambitious goals. Why you want to own your sync solution. What’s next. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #117: Avoid, Defer, Remember. http://developingperspective.com/2013/04/02/117/ Tue, 02 Apr 2013 16:17:00 -0400 David http://developingperspective.com/?p=555117 Tuesday, April 02, 2013 - How I approach improving the performance of my apps, products and my work more generally.

    ]]>
    Tuesday, April 02, 2013 - How I approach improving the performance of my apps, products and my work more generally.

    ]]>
    0 734 Tuesday, April 02, 2013 - How I approach improving the performance of my apps, products and my work more generally. Tuesday, April 02, 2013 - How I approach improving the performance of my apps, products and my work more generally. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #116: Competing with rather than against. http://developingperspective.com/2013/03/21/116/ Thu, 21 Mar 2013 15:22:00 -0400 David http://developingperspective.com/?p=555116 Thursday, March 21, 2013 - Some thoughts on how to manage splitting your attention and not going crazy. Then developing a healthy view on competition.

    ]]>
    Thursday, March 21, 2013 - Some thoughts on how to manage splitting your attention and not going crazy. Then developing a healthy view on competition.

    ]]>
    0 882 Thursday, March 21, 2013 - Some thoughts on how to manage splitting your attention and not going crazy. Then developing a healthy view on competition. Ash Furrow’s Your First iOS App project Thursday, March 21, 2013 - Some thoughts on how to manage splitting your attention and not going crazy. Then developing a healthy view on competition. Ash Furrow’s Your First iOS App project iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #115: Pitching the Press with Shawn Blanc http://developingperspective.com/2013/03/18/pitching-the-press-with-shawn-blanc/ Mon, 18 Mar 2013 14:43:00 -0400 David http://developingperspective.com/?p=5550 Monday, March 18, 2013 - I take a break from the usual 15 minute show format and talk with writer Shawn Blanc about interacting with the press. We discuss how to pitch your app or idea in such a way as to maximize the likelihood of them giving you attention. We also talk about some pitfalls to avoid.

    ]]>
    Monday, March 18, 2013 - I take a break from the usual 15 minute show format and talk with writer Shawn Blanc about interacting with the press. We discuss how to pitch your app or idea in such a way as to maximize the likelihood of them giving you attention. We also talk about some pitfalls to avoid.

    ]]>
    0 2809 Monday, March 18, 2013 - I take a break from the usual 15 minute show format and talk with writer Shawn Blanc about interacting with the press. We discuss how to pitch your app or idea in such a way as to maximize the likelihood of them giving you attention. We also talk about some pitfalls to avoid. Monday, March 18, 2013 - I take a break from the usual 15 minute show format and talk with writer Shawn Blanc about interacting with the press. We discuss how to pitch your app or idea in such a way as to maximize the likelihood of them giving you attention. We also talk about some pitfalls to avoid. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #114: Google Reader and Feed Wrangler. http://developingperspective.com/2013/03/14/114/ Thu, 14 Mar 2013 10:33:00 -0400 David http://developingperspective.com/?p=555114 Thursday, March 14, 2013 - I unpack the news that Google Reader is being killed off and pre-announce my next big project, Feed Wrangler. Feed Wrangler is an alternative service that I’m looking to launch very soon.

    More details and a sign-up for getting notified when it launches here:

    ]]>
    Thursday, March 14, 2013 - I unpack the news that Google Reader is being killed off and pre-announce my next big project, Feed Wrangler. Feed Wrangler is an alternative service that I’m looking to launch very soon.

    More details and a sign-up for getting notified when it launches here:

    ]]>
    0 893 Thursday, March 14, 2013 - I unpack the news that Google Reader is being killed off and pre-announce my next big project, Feed Wrangler. Feed Wrangler is an alternative service that I’m looking to launch very soon. More details and a sign-up for getting notified when it launches here: FeedWrangler.net My blog post about Feed Wrangler Thursday, March 14, 2013 - I unpack the news that Google Reader is being killed off and pre-announce my next big project, Feed Wrangler. Feed Wrangler is an alternative service that I’m looking to launch very soon. More details and a sign-up for getting notified when it launches here: FeedWrangler.net My blog post about Feed Wrangler iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #113: The One vs The Many. http://developingperspective.com/2013/03/12/113/ Tue, 12 Mar 2013 11:13:00 -0400 David http://developingperspective.com/?p=555113 Tuesday, March 12, 2013 - Thinking out loud about the challenges and dynamics of working by yourself versus working with others.

    ]]>
    Tuesday, March 12, 2013 - Thinking out loud about the challenges and dynamics of working by yourself versus working with others.

    ]]>
    0 877 Tuesday, March 12, 2013 - Thinking out loud about the challenges and dynamics of working by yourself versus working with others. Tuesday, March 12, 2013 - Thinking out loud about the challenges and dynamics of working by yourself versus working with others. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #112: Servers, Servers Everywhere. http://developingperspective.com/2013/03/08/112/ Fri, 08 Mar 2013 11:55:00 -0500 David http://developingperspective.com/?p=555112 Friday, March 08, 2013 - How I manage my server infrastructure and a few things I’ve learned.

    ]]>
    Friday, March 08, 2013 - How I manage my server infrastructure and a few things I’ve learned.

    ]]>
    0 866 Friday, March 08, 2013 - How I manage my server infrastructure and a few things I’ve learned. RailsCasts Recipes for provisioning servers Linode (affiliate link) Friday, March 08, 2013 - How I manage my server infrastructure and a few things I’ve learned. RailsCasts Recipes for provisioning servers Linode (affiliate link) iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #111: In it for the long haul. http://developingperspective.com/2013/03/05/111/ Tue, 05 Mar 2013 14:05:00 -0500 David http://developingperspective.com/?p=555111 Tuesday, March 05, 2013 - Talking about how to handle upgrades of older apps and dealing with burn out.

    ]]>
    Tuesday, March 05, 2013 - Talking about how to handle upgrades of older apps and dealing with burn out.

    ]]>
    0 893 Tuesday, March 05, 2013 - Talking about how to handle upgrades of older apps and dealing with burn out. My website, David-Smith.org Tuesday, March 05, 2013 - Talking about how to handle upgrades of older apps and dealing with burn out. My website, David-Smith.org iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #110: Stay in School. http://developingperspective.com/2013/02/25/110/ Mon, 25 Feb 2013 16:01:00 -0500 David http://developingperspective.com/?p=555110 Monday, February 25, 2013 - Answering a question about the values of a university education and some advice about what to do while you are there. Then, a discussion about App.Net and what that means for developers.

    ]]>
    Monday, February 25, 2013 - Answering a question about the values of a university education and some advice about what to do while you are there. Then, a discussion about App.Net and what that means for developers.

    ]]>
    0 880 Monday, February 25, 2013 - Answering a question about the values of a university education and some advice about what to do while you are there. Then, a discussion about App.Net and what that means for developers. App.Net’s Free Tier The Realities of App.net App Pricing Monday, February 25, 2013 - Answering a question about the values of a university education and some advice about what to do while you are there. Then, a discussion about App.Net and what that means for developers. App.Net’s Free Tier The Realities of App.net App Pricing iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Marco Arment. Infinite Potential. http://developingperspective.com/2013/02/18/marco/ Mon, 18 Feb 2013 10:28:00 -0500 David http://developingperspective.com/?p=5550201302181028 Monday, February 18, 2013 - A conversation with Marco Arment.

    ]]>
    Monday, February 18, 2013 - A conversation with Marco Arment.

    ]]>
    0 4217 Monday, February 18, 2013 - A conversation with Marco Arment. Marco.org Marco on Twitter Marco on App.Net Instapaper The Magazine TextMate 2 Beta Soulver Monday, February 18, 2013 - A conversation with Marco Arment. Marco.org Marco on Twitter Marco on App.Net Instapaper The Magazine TextMate 2 Beta Soulver iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #108: Negotiating. http://developingperspective.com/2013/02/15/108/ Fri, 15 Feb 2013 09:54:00 -0500 David http://developingperspective.com/?p=555108201302150954 Friday, February 15, 2013 - A discussion about some lessons I’ve learned in how to negotiate.

    ]]>
    Friday, February 15, 2013 - A discussion about some lessons I’ve learned in how to negotiate.

    ]]>
    0 886 Friday, February 15, 2013 - A discussion about some lessons I’ve learned in how to negotiate. Interview with Brent Simmons My Article about Negotiating Friday, February 15, 2013 - A discussion about some lessons I’ve learned in how to negotiate. Interview with Brent Simmons My Article about Negotiating iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Brent Simmons. The Village Toymaker. http://developingperspective.com/2013/02/12/brent/ Tue, 12 Feb 2013 10:36:00 -0500 David http://developingperspective.com/?p=5550201302121036 Tuesday, February 12, 2013 - An interview with Brent Simmons of Ranchero software.

    ]]>
    Tuesday, February 12, 2013 - An interview with Brent Simmons of Ranchero software.

    ]]>
    0 3883 Tuesday, February 12, 2013 - An interview with Brent Simmons of Ranchero software. Inessential, Brent’s Blog Identical Cousins, Brent’s Podcast Azure Heroku Linode xScope Skala Preview Kaleidoscope Glassboard Lighthouse BitBucket Tuesday, February 12, 2013 - An interview with Brent Simmons of Ranchero software. Inessential, Brent’s Blog Identical Cousins, Brent’s Podcast Azure Heroku Linode xScope Skala Preview Kaleidoscope Glassboard Lighthouse BitBucket iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #107: Adoption Rates and Reasons for Independence. http://developingperspective.com/2013/02/06/107/ Wed, 06 Feb 2013 15:20:00 -0500 David http://developingperspective.com/?p=555107201302061520 Wednesday, February 06, 2013 - iOS Adoption rates and the age old question of when to drop old OSs. A discussion recommending the Identical Cousins podcast and seconding Brent’s reasons for going back to indie life.

    ]]>
    Wednesday, February 06, 2013 - iOS Adoption rates and the age old question of when to drop old OSs. A discussion recommending the Identical Cousins podcast and seconding Brent’s reasons for going back to indie life.

    ]]>
    0 869 Wednesday, February 06, 2013 - iOS Adoption rates and the age old question of when to drop old OSs. A discussion recommending the Identical Cousins podcast and seconding Brent’s reasons for going back to indie life. Identical Cousins Gone Indie Wednesday, February 06, 2013 - iOS Adoption rates and the age old question of when to drop old OSs. A discussion recommending the Identical Cousins podcast and seconding Brent’s reasons for going back to indie life. Identical Cousins Gone Indie iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #106: Fashionable Apps. http://developingperspective.com/2013/01/29/106/ Tue, 29 Jan 2013 15:19:00 -0500 David http://developingperspective.com/?p=555106201301291519 Tuesday, January 29, 2013 - The role of fashion in making timeless apps.

    ]]>
    Tuesday, January 29, 2013 - The role of fashion in making timeless apps.

    ]]>
    0 735 Tuesday, January 29, 2013 - The role of fashion in making timeless apps. Tuesday, January 29, 2013 - The role of fashion in making timeless apps. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #105: An Ergonomic Work Environment. http://developingperspective.com/2013/01/25/105/ Fri, 25 Jan 2013 10:19:00 -0500 David http://developingperspective.com/?p=555105201301251019 Friday, January 25, 2013 - Walking through the aspects and characteristics of a comfortable work environment.

    I’ll be in San Francisco coincident with MacWorld this year. If you want to meet up please get in touch.

    ]]>
    Friday, January 25, 2013 - Walking through the aspects and characteristics of a comfortable work environment.

    I’ll be in San Francisco coincident with MacWorld this year. If you want to meet up please get in touch.

    ]]>
    0 896 Friday, January 25, 2013 - Walking through the aspects and characteristics of a comfortable work environment. I’ll be in San Francisco coincident with MacWorld this year. If you want to meet up please get in touch. Chair - Embody Keyboard - Microsoft Natural Mouse - Razer Deathadder (Wired) Mouse Pad - SteelSeries 4HD Friday, January 25, 2013 - Walking through the aspects and characteristics of a comfortable work environment. I’ll be in San Francisco coincident with MacWorld this year. If you want to meet up please get in touch. Chair - Embody Keyboard - Microsoft Natural Mouse - Razer Deathadder (Wired) Mouse Pad - SteelSeries 4HD iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #104: Learning to Love App Review. http://developingperspective.com/2013/01/21/104/ Mon, 21 Jan 2013 11:07:00 -0500 David http://developingperspective.com/?p=555104201301211107 Monday, January 21, 2013 - A brief discussion of Apple’s new screenshot policy. Followed by a more broad discussion of why I love App Review and how to take advantage of it.

    ]]>
    Monday, January 21, 2013 - A brief discussion of Apple’s new screenshot policy. Followed by a more broad discussion of why I love App Review and how to take advantage of it.

    ]]>
    0 897 Monday, January 21, 2013 - A brief discussion of Apple’s new screenshot policy. Followed by a more broad discussion of why I love App Review and how to take advantage of it. Monday, January 21, 2013 - A brief discussion of Apple’s new screenshot policy. Followed by a more broad discussion of why I love App Review and how to take advantage of it. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #103: Coding Sins. http://developingperspective.com/2013/01/08/103/ Tue, 08 Jan 2013 11:23:00 -0500 David http://developingperspective.com/?p=555103201301081123 Tuesday, January 08, 2013 - Some great advice about writing better Objective-C based on articles by Brent Simmons and Ash Furrow.

    ]]>
    Tuesday, January 08, 2013 - Some great advice about writing better Objective-C based on articles by Brent Simmons and Ash Furrow.

    ]]>
    0 874 Tuesday, January 08, 2013 - Some great advice about writing better Objective-C based on articles by Brent Simmons and Ash Furrow. Seven Deadly Sins of Modern Objective-C Coders in the Hands of an Angry God UITableViewCell Is Not a Controller Tuesday, January 08, 2013 - Some great advice about writing better Objective-C based on articles by Brent Simmons and Ash Furrow. Seven Deadly Sins of Modern Objective-C Coders in the Hands of an Angry God UITableViewCell Is Not a Controller iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #102: Sharpening Your Skills. http://developingperspective.com/2013/01/03/102/ Thu, 03 Jan 2013 14:54:00 -0500 David http://developingperspective.com/?p=555102201301031454 Thursday, January 03, 2013 - How to stay sharp and keep your coding skills getting better and better.

    ]]>
    Thursday, January 03, 2013 - How to stay sharp and keep your coding skills getting better and better.

    ]]>
    0 879 Thursday, January 03, 2013 - How to stay sharp and keep your coding skills getting better and better. nshipster Mattt Thompson on github Objective-C on github Mike Ash Peter Steinberger Thursday, January 03, 2013 - How to stay sharp and keep your coding skills getting better and better. nshipster Mattt Thompson on github Objective-C on github Mike Ash Peter Steinberger iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #101: The 3 C’s of a balanced life. http://developingperspective.com/2013/01/01/101/ Tue, 01 Jan 2013 15:14:00 -0500 David http://developingperspective.com/?p=555101201301011514 Tuesday, January 01, 2013 - Some things I’ve learned (often the hard way) about how to try and balance your work and personal life.

    ]]>
    Tuesday, January 01, 2013 - Some things I’ve learned (often the hard way) about how to try and balance your work and personal life.

    ]]>
    0 803 Tuesday, January 01, 2013 - Some things I’ve learned (often the hard way) about how to try and balance your work and personal life. Tuesday, January 01, 2013 - Some things I’ve learned (often the hard way) about how to try and balance your work and personal life. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #100: Showing Up. http://developingperspective.com/2012/12/12/100/ Wed, 12 Dec 2012 16:03:00 -0500 David http://developingperspective.com/?p=555100201212121603 Wednesday, December 12, 2012 - A few thoughts on how to stay motivated and stick with something, prompted by reaching episode 100.

    ]]>
    Wednesday, December 12, 2012 - A few thoughts on how to stay motivated and stick with something, prompted by reaching episode 100.

    ]]>
    0 810 Wednesday, December 12, 2012 - A few thoughts on how to stay motivated and stick with something, prompted by reaching episode 100. Wednesday, December 12, 2012 - A few thoughts on how to stay motivated and stick with something, prompted by reaching episode 100. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #99: Handling your Finances. http://developingperspective.com/2012/12/06/99/ Thu, 06 Dec 2012 15:18:00 -0500 David http://developingperspective.com/?p=55599201212061518 Thursday, December 06, 2012 - Some practical thoughts about handling the financial side of a small business.

    ]]>
    Thursday, December 06, 2012 - Some practical thoughts about handling the financial side of a small business.

    ]]>
    0 793 Thursday, December 06, 2012 - Some practical thoughts about handling the financial side of a small business. Thursday, December 06, 2012 - Some practical thoughts about handling the financial side of a small business. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #98: Practical Helpdesk http://developingperspective.com/2012/12/04/98/ Tue, 04 Dec 2012 10:13:00 -0500 David http://developingperspective.com/?p=55598201212041013 Tuesday, December 04, 2012 - How I handle the email that comes into my helpdesk system. A few little tricks helps the process take very little time.

    ]]>
    Tuesday, December 04, 2012 - How I handle the email that comes into my helpdesk system. A few little tricks helps the process take very little time.

    ]]>
    0 889 Tuesday, December 04, 2012 - How I handle the email that comes into my helpdesk system. A few little tricks helps the process take very little time. Google Apps TextExpander Tuesday, December 04, 2012 - How I handle the email that comes into my helpdesk system. A few little tricks helps the process take very little time. Google Apps TextExpander iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #97: Sales and Power Songs. http://developingperspective.com/2012/11/27/97/ Tue, 27 Nov 2012 16:05:00 -0500 David http://developingperspective.com/?p=55597201211271605 Tuesday, November 27, 2012 - The mechanics of putting an app on sale and trying to gain focus.

    ]]>
    Tuesday, November 27, 2012 - The mechanics of putting an app on sale and trying to gain focus.

    ]]>
    0 807 Tuesday, November 27, 2012 - The mechanics of putting an app on sale and trying to gain focus. Dragonforce Tuesday, November 27, 2012 - The mechanics of putting an app on sale and trying to gain focus. Dragonforce iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #96: Ending Something, Splitting Something, Analyzing Something. http://developingperspective.com/2012/11/20/96/ Tue, 20 Nov 2012 16:02:00 -0500 David http://developingperspective.com/?p=55596201211201602 Tuesday, November 20, 2012 - Deciding when is the right time to end something. How to submit multiple versions of the same app. When and how to use analytics in your apps.

    ]]>
    Tuesday, November 20, 2012 - Deciding when is the right time to end something. How to submit multiple versions of the same app. When and how to use analytics in your apps.

    ]]>
    0 678 Tuesday, November 20, 2012 - Deciding when is the right time to end something. How to submit multiple versions of the same app. When and how to use analytics in your apps. Tuesday, November 20, 2012 - Deciding when is the right time to end something. How to submit multiple versions of the same app. When and how to use analytics in your apps. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #95: Reinventing the Wheel http://developingperspective.com/2012/11/16/95/ Fri, 16 Nov 2012 15:27:00 -0500 David http://developingperspective.com/?p=55595201211161527 Friday, November 16, 2012 - How to decided if when to use external services or APIs. Considering the cost of external services. Staying motivated when working with new services.

    ]]>
    Friday, November 16, 2012 - How to decided if when to use external services or APIs. Considering the cost of external services. Staying motivated when working with new services.

    ]]>
    0 877 Friday, November 16, 2012 - How to decided if when to use external services or APIs. Considering the cost of external services. Staying motivated when working with new services. Friday, November 16, 2012 - How to decided if when to use external services or APIs. Considering the cost of external services. Staying motivated when working with new services. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #94: Git and Source Control. http://developingperspective.com/2012/11/08/94/ Thu, 08 Nov 2012 16:25:00 -0500 David http://developingperspective.com/?p=55594201211081625 Thursday, November 08, 2012 - I’m moving into a season of answering your questions. If you have topics you’d like me to cover let me know on Twitter (@_DavidSmith) or ADN (@DavidSmith). Today I talk about Git and Source Control more generally.

    ]]>
    Thursday, November 08, 2012 - I’m moving into a season of answering your questions. If you have topics you’d like me to cover let me know on Twitter (@_DavidSmith) or ADN (@DavidSmith). Today I talk about Git and Source Control more generally.

    ]]>
    0 889 Thursday, November 08, 2012 - I’m moving into a season of answering your questions. If you have topics you’d like me to cover let me know on Twitter (@_DavidSmith) or ADN (@DavidSmith). Today I talk about Git and Source Control more generally. Pro Git Thursday, November 08, 2012 - I’m moving into a season of answering your questions. If you have topics you’d like me to cover let me know on Twitter (@_DavidSmith) or ADN (@DavidSmith). Today I talk about Git and Source Control more generally. Pro Git iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #93: Universal and Lite. http://developingperspective.com/2012/11/01/93/ Thu, 01 Nov 2012 11:06:00 -0400 David http://developingperspective.com/?p=55593201211011106 Thursday, November 01, 2012 - Thinking through whether to make your app Universal or have a separate iPad version. When having a Lite version makes sense.

    ]]>
    Thursday, November 01, 2012 - Thinking through whether to make your app Universal or have a separate iPad version. When having a Lite version makes sense.

    ]]>
    0 888 Thursday, November 01, 2012 - Thinking through whether to make your app Universal or have a separate iPad version. When having a Lite version makes sense. Thursday, November 01, 2012 - Thinking through whether to make your app Universal or have a separate iPad version. When having a Lite version makes sense. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #92: The New Developer Machine Landscape. http://developingperspective.com/2012/10/24/92/ Wed, 24 Oct 2012 09:42:00 -0400 David http://developingperspective.com/?p=55592201210240942 Wednesday, October 24, 2012 - A few thoughts about the new iPad lineup and then a longer discussion about how the new Macs change the ideal developer machine equation.

    ]]>
    Wednesday, October 24, 2012 - A few thoughts about the new iPad lineup and then a longer discussion about how the new Macs change the ideal developer machine equation.

    ]]>
    0 951 Wednesday, October 24, 2012 - A few thoughts about the new iPad lineup and then a longer discussion about how the new Macs change the ideal developer machine equation. Wednesday, October 24, 2012 - A few thoughts about the new iPad lineup and then a longer discussion about how the new Macs change the ideal developer machine equation. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #91: Thank you and the Road from Here. http://developingperspective.com/2012/10/18/91/ Thu, 18 Oct 2012 15:59:00 -0400 David http://developingperspective.com/?p=55591201210181559 Thursday, October 18, 2012 - Thank you all for the amazing response to Check the Weather. Today I talk about two lesson I’ve learned in development that apply very well to the launch.

    ]]>
    Thursday, October 18, 2012 - Thank you all for the amazing response to Check the Weather. Today I talk about two lesson I’ve learned in development that apply very well to the launch.

    ]]>
    0 863 Thursday, October 18, 2012 - Thank you all for the amazing response to Check the Weather. Today I talk about two lesson I’ve learned in development that apply very well to the launch. Malcom Gladwell at TED Thursday, October 18, 2012 - Thank you all for the amazing response to Check the Weather. Today I talk about two lesson I’ve learned in development that apply very well to the launch. Malcom Gladwell at TED iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #90: Check the Weather http://developingperspective.com/2012/10/17/90/ Wed, 17 Oct 2012 13:22:00 -0400 David http://developingperspective.com/?p=55590201210171322 Wednesday, October 17, 2012 - Introducing my new weather app, Check the Weather. Thank you for helping me get it out the door. This is also coincidentally the 100th regular episode of Developing Perspective. So thanks all around.

    ]]>
    Wednesday, October 17, 2012 - Introducing my new weather app, Check the Weather. Thank you for helping me get it out the door. This is also coincidentally the 100th regular episode of Developing Perspective. So thanks all around.

    ]]>
    0 846 Wednesday, October 17, 2012 - Introducing my new weather app, Check the Weather. Thank you for helping me get it out the door. This is also coincidentally the 100th regular episode of Developing Perspective. So thanks all around. Check the Weather Wednesday, October 17, 2012 - Introducing my new weather app, Check the Weather. Thank you for helping me get it out the door. This is also coincidentally the 100th regular episode of Developing Perspective. So thanks all around. Check the Weather iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #89: Counting Down. http://developingperspective.com/2012/10/16/89/ Tue, 16 Oct 2012 16:51:00 -0400 David http://developingperspective.com/?p=55589201210161651 Tuesday, October 16, 2012 - Walking through the steps you do right before launching an app.

    ]]>
    Tuesday, October 16, 2012 - Walking through the steps you do right before launching an app.

    ]]>
    0 712 Tuesday, October 16, 2012 - Walking through the steps you do right before launching an app. Tuesday, October 16, 2012 - Walking through the steps you do right before launching an app. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #88: Conferences and Unique Opportunities. http://developingperspective.com/2012/10/15/88/ Mon, 15 Oct 2012 10:10:00 -0400 David http://developingperspective.com/?p=55588201210151010 Monday, October 15, 2012 - I talk about my experiences at Cingleton and generally how I try to handle the potentially awkward and complicated social opportunities of a conference. Then, I dive into a very brief talk about how to look for unique opportunities in the App Store.

    ]]>
    Monday, October 15, 2012 - I talk about my experiences at Cingleton and generally how I try to handle the potentially awkward and complicated social opportunities of a conference. Then, I dive into a very brief talk about how to look for unique opportunities in the App Store.

    ]]>
    0 898 Monday, October 15, 2012 - I talk about my experiences at Cingleton and generally how I try to handle the potentially awkward and complicated social opportunities of a conference. Then, I dive into a very brief talk about how to look for unique opportunities in the App Store. The Magazine Monday, October 15, 2012 - I talk about my experiences at Cingleton and generally how I try to handle the potentially awkward and complicated social opportunities of a conference. Then, I dive into a very brief talk about how to look for unique opportunities in the App Store. The Magazine iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #87: Basic App Marketing. http://developingperspective.com/2012/10/09/87/ Tue, 09 Oct 2012 10:22:00 -0400 David http://developingperspective.com/?p=55587201210091022 Tuesday, October 09, 2012 - Check the Weather is now approved and heading to launch next week. My thoughts on generating buzz.

    ]]>
    Tuesday, October 09, 2012 - Check the Weather is now approved and heading to launch next week. My thoughts on generating buzz.

    ]]>
    0 900 Tuesday, October 09, 2012 - Check the Weather is now approved and heading to launch next week. My thoughts on generating buzz. TestFlight User Friendly Promo Codes Tuesday, October 09, 2012 - Check the Weather is now approved and heading to launch next week. My thoughts on generating buzz. TestFlight User Friendly Promo Codes iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #86: App Pricing. http://developingperspective.com/2012/10/05/86/ Fri, 05 Oct 2012 16:55:00 -0400 David http://developingperspective.com/?p=55586201210051655 Friday, October 05, 2012 - App Store pricing.

    ]]>
    Friday, October 05, 2012 - App Store pricing.

    ]]>
    0 865 Friday, October 05, 2012 - App Store pricing. Friday, October 05, 2012 - App Store pricing. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #85: Pragmatism. http://developingperspective.com/2012/10/04/85/ Thu, 04 Oct 2012 10:48:00 -0400 David http://developingperspective.com/?p=55585201210041048 Thursday, October 04, 2012 - Being pragmatic about how ‘good’ your software is and avoiding fear of it not living up to impossible expectations.

    ]]>
    Thursday, October 04, 2012 - Being pragmatic about how ‘good’ your software is and avoiding fear of it not living up to impossible expectations.

    ]]>
    0 900 Thursday, October 04, 2012 - Being pragmatic about how ‘good’ your software is and avoiding fear of it not living up to impossible expectations. Thursday, October 04, 2012 - Being pragmatic about how ‘good’ your software is and avoiding fear of it not living up to impossible expectations. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #84: Shipped it. http://developingperspective.com/2012/09/28/84/ Fri, 28 Sep 2012 09:40:00 -0400 David http://developingperspective.com/?p=55584201209280940 Friday, September 28, 2012 - The importance of celebration when you ship a project…oh and I shipped Check the Weather ;)

    ]]>
    Friday, September 28, 2012 - The importance of celebration when you ship a project…oh and I shipped Check the Weather ;)

    ]]>
    0 385 Friday, September 28, 2012 - The importance of celebration when you ship a project…oh and I shipped Check the Weather ;) Friday, September 28, 2012 - The importance of celebration when you ship a project…oh and I shipped Check the Weather ;) iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #83: Performance and Letting Go. http://developingperspective.com/2012/09/27/83/ Thu, 27 Sep 2012 15:23:00 -0400 David http://developingperspective.com/?p=55583201209271523 Thursday, September 27, 2012 - Performance tuning your application and embracing the process of showing it off to new people.

    ]]>
    Thursday, September 27, 2012 - Performance tuning your application and embracing the process of showing it off to new people.

    ]]>
    0 900 Thursday, September 27, 2012 - Performance tuning your application and embracing the process of showing it off to new people. Thursday, September 27, 2012 - Performance tuning your application and embracing the process of showing it off to new people. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #82: Localizing an App. http://developingperspective.com/2012/09/25/82/ Tue, 25 Sep 2012 09:50:00 -0400 David http://developingperspective.com/?p=55582201209250950 Tuesday, September 25, 2012 - Walking through the process of localizing an app. It is remarkably straightforward.

    App Localization Services:

    ]]>
    Tuesday, September 25, 2012 - Walking through the process of localizing an app. It is remarkably straightforward.

    App Localization Services:

    ]]>
    0 899 Tuesday, September 25, 2012 - Walking through the process of localizing an app. It is remarkably straightforward. Linguan App Localization Services: Tethras - My chosen provider. I went with them because they seemed to have a good balance between cost and quality. I wasn’t disappointed. AppLingua Wordcrafts iCanLocalize Tuesday, September 25, 2012 - Walking through the process of localizing an app. It is remarkably straightforward. Linguan App Localization Services: Tethras - My chosen provider. I went with them because they seemed to have a good balance between cost and quality. I wasn’t disappointed. AppLingua Wordcrafts iCanLocalize iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    The iPhone 5. http://developingperspective.com/2012/09/21/81/ Fri, 21 Sep 2012 11:02:00 -0400 David http://developingperspective.com/?p=55581201209211102 Friday, September 21, 2012 - First impressions on the iPhone 5 then a few considerations it and iOS 6 bring to developers.

    ]]>
    Friday, September 21, 2012 - First impressions on the iPhone 5 then a few considerations it and iOS 6 bring to developers.

    ]]>
    0 811 Friday, September 21, 2012 - First impressions on the iPhone 5 then a few considerations it and iOS 6 bring to developers. Smart App Banners Friday, September 21, 2012 - First impressions on the iPhone 5 then a few considerations it and iOS 6 bring to developers. Smart App Banners iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #80: Managing functionality. http://developingperspective.com/2012/09/19/80/ Wed, 19 Sep 2012 15:24:00 -0400 David http://developingperspective.com/?p=55580201209191524 Wednesday, September 19, 2012 - Talking about how to best manage the feature-set and functionality of a new app. Don’t worry about building everything, start with the kernel of a good idea and build out from there.

    ]]>
    Wednesday, September 19, 2012 - Talking about how to best manage the feature-set and functionality of a new app. Don’t worry about building everything, start with the kernel of a good idea and build out from there.

    ]]>
    0 872 Wednesday, September 19, 2012 - Talking about how to best manage the feature-set and functionality of a new app. Don’t worry about building everything, start with the kernel of a good idea and build out from there. Wednesday, September 19, 2012 - Talking about how to best manage the feature-set and functionality of a new app. Don’t worry about building everything, start with the kernel of a good idea and build out from there. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #79: Getting Ready for iOS 6. http://developingperspective.com/2012/09/13/79/ Thu, 13 Sep 2012 16:19:00 -0400 David http://developingperspective.com/?p=55579201209131619 Thursday, September 13, 2012 - Talking about the new iPhone 5 and getting ready for iOS 6.

    ]]>
    Thursday, September 13, 2012 - Talking about the new iPhone 5 and getting ready for iOS 6.

    ]]>
    0 754 Thursday, September 13, 2012 - Talking about the new iPhone 5 and getting ready for iOS 6. iOS Version Stats Thursday, September 13, 2012 - Talking about the new iPhone 5 and getting ready for iOS 6. iOS Version Stats iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #78: Managing 3rd Party Libraries. http://developingperspective.com/2012/09/11/78/ Tue, 11 Sep 2012 15:47:00 -0400 David http://developingperspective.com/?p=55578201209111547 Tuesday, September 11, 2012 - Another quick tip on prototyping, then how I managed 3rd party libraries.

    ]]>
    Tuesday, September 11, 2012 - Another quick tip on prototyping, then how I managed 3rd party libraries.

    ]]>
    0 880 Tuesday, September 11, 2012 - Another quick tip on prototyping, then how I managed 3rd party libraries. CocoaPods Tuesday, September 11, 2012 - Another quick tip on prototyping, then how I managed 3rd party libraries. CocoaPods iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #77: Prototyping a new project. http://developingperspective.com/2012/09/06/77/ Thu, 06 Sep 2012 10:05:00 -0400 David http://developingperspective.com/?p=55577201209061005 Thursday, September 06, 2012 - I kick off a multi episode arc discussing my process in developing a weather application. Today I’ll be talking about how to jump start development with rapid prototyping and getting working things as soon as possible.

    ]]>
    Thursday, September 06, 2012 - I kick off a multi episode arc discussing my process in developing a weather application. Today I’ll be talking about how to jump start development with rapid prototyping and getting working things as soon as possible.

    ]]>
    0 880 Thursday, September 06, 2012 - I kick off a multi episode arc discussing my process in developing a weather application. Today I’ll be talking about how to jump start development with rapid prototyping and getting working things as soon as possible. Thursday, September 06, 2012 - I kick off a multi episode arc discussing my process in developing a weather application. Today I’ll be talking about how to jump start development with rapid prototyping and getting working things as soon as possible. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #76: The best way to avoid distractions. http://developingperspective.com/2012/09/04/76/ Tue, 04 Sep 2012 09:56:00 -0400 David http://developingperspective.com/?p=55575201209040956 Tuesday, September 04, 2012 - I talk about my experience with getting excited about my latest project and how that improves productivity. If you aren’t excited about what you are doing, why are you doing it?

    ]]>
    Tuesday, September 04, 2012 - I talk about my experience with getting excited about my latest project and how that improves productivity. If you aren’t excited about what you are doing, why are you doing it?

    ]]>
    0 839 Tuesday, September 04, 2012 - I talk about my experience with getting excited about my latest project and how that improves productivity. If you aren’t excited about what you are doing, why are you doing it? Apple’s Unsolicited Idea Submission Policy Tuesday, September 04, 2012 - I talk about my experience with getting excited about my latest project and how that improves productivity. If you aren’t excited about what you are doing, why are you doing it? Apple’s Unsolicited Idea Submission Policy iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #75: Rates and Contracts http://developingperspective.com/2012/08/30/75/ Thu, 30 Aug 2012 15:41:00 -0400 David http://developingperspective.com/?p=55575201208301541 Thursday, August 30, 2012 - Talking about different types of contracting and how to choose a good rate for your work.

    ]]>
    Thursday, August 30, 2012 - Talking about different types of contracting and how to choose a good rate for your work.

    ]]>
    0 900 Thursday, August 30, 2012 - Talking about different types of contracting and how to choose a good rate for your work. Thursday, August 30, 2012 - Talking about different types of contracting and how to choose a good rate for your work. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Rob Rhyne http://developingperspective.com/2012/08/29/rhyne/ Wed, 29 Aug 2012 11:36:00 -0400 David http://developingperspective.com/?p=5550201208291136 Wednesday, August 29, 2012 - An interview with Rob Rhyne of MartianCraft. We discuss design and its role in software development. Rob comes at the development from a design savvy background and walks through how that informs the decisions he makes while coding.

    ]]>
    Wednesday, August 29, 2012 - An interview with Rob Rhyne of MartianCraft. We discuss design and its role in software development. Rob comes at the development from a design savvy background and walks through how that informs the decisions he makes while coding.

    ]]>
    0 3614 Wednesday, August 29, 2012 - An interview with Rob Rhyne of MartianCraft. We discuss design and its role in software development. Rob comes at the development from a design savvy background and walks through how that informs the decisions he makes while coding. Rob Rhyne on Twitter Rob’s Blog MartianCraft Invincible - transitional music Epic Soundtracks on Pandora xScope Favorite Mailboxes by Matt Gemmell Acorn The Design of Everyday Things Mike Rundle Matt Gemmell Sticky Notifications Wednesday, August 29, 2012 - An interview with Rob Rhyne of MartianCraft. We discuss design and its role in software development. Rob comes at the development from a design savvy background and walks through how that informs the decisions he makes while coding. Rob Rhyne on Twitter Rob’s Blog MartianCraft Invincible - transitional music Epic Soundtracks on Pandora xScope Favorite Mailboxes by Matt Gemmell Acorn The Design of Everyday Things Mike Rundle Matt Gemmell Sticky Notifications iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #74: Transitioning to iOS http://developingperspective.com/2012/08/28/74/ Tue, 28 Aug 2012 10:31:00 -0400 David http://developingperspective.com/?p=55574201208281031 Tuesday, August 28, 2012 - Making the move to iOS development from an experienced background on another platform.

    ]]>
    Tuesday, August 28, 2012 - Making the move to iOS development from an experienced background on another platform.

    ]]>
    0 835 Tuesday, August 28, 2012 - Making the move to iOS development from an experienced background on another platform. Tuesday, August 28, 2012 - Making the move to iOS development from an experienced background on another platform. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #73: Updates, Updates, Updates. http://developingperspective.com/2012/08/21/72/ Tue, 21 Aug 2012 13:14:00 -0400 David http://developingperspective.com/?p=55572201208211314 Tuesday, August 21, 2012 - Talking about how to manage and understand App Store updates.

    ]]>
    Tuesday, August 21, 2012 - Talking about how to manage and understand App Store updates.

    ]]>
    0 892 Tuesday, August 21, 2012 - Talking about how to manage and understand App Store updates. Tuesday, August 21, 2012 - Talking about how to manage and understand App Store updates. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #72: Mistakes, Designing Icons and getting Acquired. http://developingperspective.com/2012/08/16/72/ Thu, 16 Aug 2012 12:52:00 -0400 David http://developingperspective.com/?p=55572201208161252 Thursday, August 16, 2012 - A brief apology and how to appropriately handle mistakes, a discussion on the process of designing an app icon, and the options you have when your app gets acquired.

    ]]>
    Thursday, August 16, 2012 - A brief apology and how to appropriately handle mistakes, a discussion on the process of designing an app icon, and the options you have when your app gets acquired.

    ]]>
    0 900 Thursday, August 16, 2012 - A brief apology and how to appropriately handle mistakes, a discussion on the process of designing an app icon, and the options you have when your app gets acquired. New My Recipe Book icon Iconfactory Thursday, August 16, 2012 - A brief apology and how to appropriately handle mistakes, a discussion on the process of designing an app icon, and the options you have when your app gets acquired. New My Recipe Book icon Iconfactory iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Bill Dudney http://developingperspective.com/2012/08/15/1/ Wed, 15 Aug 2012 09:55:00 -0400 David http://developingperspective.com/?p=5552222 Wednesday, August 15, 2012 - A conversation with Bill Dudney about learning Objective-C, how to be productive in solving hard programming problems and effectively using Apple’s debugging tools.

    ]]>
    Wednesday, August 15, 2012 - A conversation with Bill Dudney about learning Objective-C, how to be productive in solving hard programming problems and effectively using Apple’s debugging tools.

    ]]>
    0 3261 Wednesday, August 15, 2012 - A conversation with Bill Dudney about learning Objective-C, how to be productive in solving hard programming problems and effectively using Apple’s debugging tools. Bill Dudney on Twitter Bill Dudney’s Blog iOS Programming Course with The Pragmatic Studio iOS SDK Development by Chris Adamson and Bill Dudney TextMate OmniGraffle Pro Git Tower - Git Client Learn to Program by Chris Pine Programming in Objective-C by Stephen Kochan LEGO Mindstorms Sinclair Spectrum Wednesday, August 15, 2012 - A conversation with Bill Dudney about learning Objective-C, how to be productive in solving hard programming problems and effectively using Apple’s debugging tools. Bill Dudney on Twitter Bill Dudney’s Blog iOS Programming Course with The Pragmatic Studio iOS SDK Development by Chris Adamson and Bill Dudney TextMate OmniGraffle Pro Git Tower - Git Client Learn to Program by Chris Pine Programming in Objective-C by Stephen Kochan LEGO Mindstorms Sinclair Spectrum iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #71: Pruning your App Garden http://developingperspective.com/2012/08/14/71/ Tue, 14 Aug 2012 10:25:00 -0400 David http://developingperspective.com/?p=55571 Tuesday, August 14, 2012 - A discussion of how to manage your time when it comes to working on something new or updating an existing app.

    ]]>
    Tuesday, August 14, 2012 - A discussion of how to manage your time when it comes to working on something new or updating an existing app.

    ]]>
    0 901 Tuesday, August 14, 2012 - A discussion of how to manage your time when it comes to working on something new or updating an existing app. Build and Analyze #90: This Person Isn’t Really Here Ulrik Damm Robocat Apps App Store Metrics Tuesday, August 14, 2012 - A discussion of how to manage your time when it comes to working on something new or updating an existing app. Build and Analyze #90: This Person Isn’t Really Here Ulrik Damm Robocat Apps App Store Metrics iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #70: The Importance of Rest http://developingperspective.com/2012/08/02/70/ Thu, 02 Aug 2012 17:03:00 -0400 David http://developingperspective.com/?p=55570 Thursday, August 02, 2012 - Discussing the importance of integrating rest into our daily or weekly schedules.

    ]]>
    Thursday, August 02, 2012 - Discussing the importance of integrating rest into our daily or weekly schedules.

    ]]>
    0 800 Thursday, August 02, 2012 - Discussing the importance of integrating rest into our daily or weekly schedules. Thursday, August 02, 2012 - Discussing the importance of integrating rest into our daily or weekly schedules. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Matthew Bischoff http://developingperspective.com/2012/07/31/bischoff/ Tue, 31 Jul 2012 11:57:00 -0400 David http://developingperspective.com/?p=5551 Tuesday, July 31, 2012 - A conversation with Matthew Bischoff of Lickability and the New York Times.

    ]]>
    Tuesday, July 31, 2012 - A conversation with Matthew Bischoff of Lickability and the New York Times.

    ]]>
    0 2872 Tuesday, July 31, 2012 - A conversation with Matthew Bischoff of Lickability and the New York Times. Matthew Bischoff on Twitter MatthewBischoff.com Quotebook Pair Programming Tomorrow Theme Advanced Appearance Customization on iOS - WWDC Video Code Complete Tuesday, July 31, 2012 - A conversation with Matthew Bischoff of Lickability and the New York Times. Matthew Bischoff on Twitter MatthewBischoff.com Quotebook Pair Programming Tomorrow Theme Advanced Appearance Customization on iOS - WWDC Video Code Complete iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #69: Talking about money http://developingperspective.com/2012/07/31/69/ Tue, 31 Jul 2012 05:33:00 -0400 David http://developingperspective.com/?p=55569 Tuesday, July 31, 2012 - Announcing a new segment where I’ll be having conversations with prominent developers and a discussion of why I never talk about money publicly.

    ]]>
    Tuesday, July 31, 2012 - Announcing a new segment where I’ll be having conversations with prominent developers and a discussion of why I never talk about money publicly.

    ]]>
    0 859 Tuesday, July 31, 2012 - Announcing a new segment where I’ll be having conversations with prominent developers and a discussion of why I never talk about money publicly. Tuesday, July 31, 2012 - Announcing a new segment where I’ll be having conversations with prominent developers and a discussion of why I never talk about money publicly. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #68: Being a Student of the App Store http://developingperspective.com/2012/07/26/68/ Thu, 26 Jul 2012 10:57:00 -0400 David http://developingperspective.com/?p=55568 Thursday, July 26, 2012 - Why I haven’t upgrade to Mountain Lion yet and how I am a ‘Student’ of the App Store.

    Some People to Follow:

    ]]>
    Thursday, July 26, 2012 - Why I haven’t upgrade to Mountain Lion yet and how I am a ‘Student’ of the App Store.

    Some People to Follow:

    ]]>
    0 902 Thursday, July 26, 2012 - Why I haven’t upgrade to Mountain Lion yet and how I am a ‘Student’ of the App Store. #58: Managing new SDKs The Path to Success in the App Store AppAnnie App Figures Some People to Follow: Ian Marsh David Barnard Eli Hodapp Phill Ryu Blake Patterson Marco Arment Paul Haddad Steve Streza Federico Viticci Thursday, July 26, 2012 - Why I haven’t upgrade to Mountain Lion yet and how I am a ‘Student’ of the App Store. #58: Managing new SDKs The Path to Success in the App Store AppAnnie App Figures Some People to Follow: Ian Marsh David Barnard Eli Hodapp Phill Ryu Blake Patterson Marco Arment Paul Haddad Steve Streza Federico Viticci iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #67: The Apple Business Team http://developingperspective.com/2012/07/24/67/ Tue, 24 Jul 2012 11:02:00 -0400 David http://developingperspective.com/?p=55567 Tuesday, July 24, 2012 - Announcing a new schedule for Developing Perspective. New episodes will now be posted on Tuesdays and Thursdays.

    My first impressions of the Retina MacBook Pro and how I used the Apple Business Team to get it.

    ]]>
    Tuesday, July 24, 2012 - Announcing a new schedule for Developing Perspective. New episodes will now be posted on Tuesdays and Thursdays.

    My first impressions of the Retina MacBook Pro and how I used the Apple Business Team to get it.

    ]]>
    0 890 Tuesday, July 24, 2012 - Announcing a new schedule for Developing Perspective. New episodes will now be posted on Tuesdays and Thursdays. My first impressions of the Retina MacBook Pro and how I used the Apple Business Team to get it. Tuesday, July 24, 2012 - Announcing a new schedule for Developing Perspective. New episodes will now be posted on Tuesdays and Thursdays. My first impressions of the Retina MacBook Pro and how I used the Apple Business Team to get it. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #66: Pricing for Features http://developingperspective.com/2012/07/18/66/ Wed, 18 Jul 2012 10:44:00 -0400 David http://developingperspective.com/?p=55566 Wednesday, July 18, 2012 - A bit of housekeeping. Comparing the various advantages and disadvantages of charging for features. Also whether to be universal or have two seperate apps.

    Question via @nalenb.

    ]]>
    Wednesday, July 18, 2012 - A bit of housekeeping. Comparing the various advantages and disadvantages of charging for features. Also whether to be universal or have two seperate apps.

    Question via @nalenb.

    ]]>
    0 907 Wednesday, July 18, 2012 - A bit of housekeeping. Comparing the various advantages and disadvantages of charging for features. Also whether to be universal or have two seperate apps. Survey Edge Cases Episode 64 Question via @nalenb. Wednesday, July 18, 2012 - A bit of housekeeping. Comparing the various advantages and disadvantages of charging for features. Also whether to be universal or have two seperate apps. Survey Edge Cases Episode 64 Question via @nalenb. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #65: Pirates and Piracy http://developingperspective.com/2012/07/16/65/ Mon, 16 Jul 2012 10:50:00 -0400 David http://developingperspective.com/?p=55565 Monday, July 16, 2012 - Recommending Edge Cases podcast, the origin of the Underscore, and discussion about Piracy.

    ]]>
    Monday, July 16, 2012 - Recommending Edge Cases podcast, the origin of the Underscore, and discussion about Piracy.

    ]]>
    0 889 Monday, July 16, 2012 - Recommending Edge Cases podcast, the origin of the Underscore, and discussion about Piracy. Edge Cases Popular Names Monday, July 16, 2012 - Recommending Edge Cases podcast, the origin of the Underscore, and discussion about Piracy. Edge Cases Popular Names iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #64: Footnotes on Side Projects and iCloud Data Sync http://developingperspective.com/2012/07/13/64/ Fri, 13 Jul 2012 16:20:00 -0400 David http://developingperspective.com/?p=55564 Friday, July 13, 2012 - Some footnotes on having Side Projects and a few thoughts on using iCloud for Core Data syncing.

    ]]>
    Friday, July 13, 2012 - Some footnotes on having Side Projects and a few thoughts on using iCloud for Core Data syncing.

    ]]>
    0 894 Friday, July 13, 2012 - Some footnotes on having Side Projects and a few thoughts on using iCloud for Core Data syncing. Show 63 Simperium Parse Friday, July 13, 2012 - Some footnotes on having Side Projects and a few thoughts on using iCloud for Core Data syncing. Show 63 Simperium Parse iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #63: Side Projects and Internationalization http://developingperspective.com/2012/07/12/63/ Thu, 12 Jul 2012 14:24:00 -0400 David http://developingperspective.com/?p=55563 Thursday, July 12, 2012 - The importance of having Side Projects and Internationalization.

    Question from Paul Dunahoo.

    ]]>
    Thursday, July 12, 2012 - The importance of having Side Projects and Internationalization.

    Question from Paul Dunahoo.

    ]]>
    0 872 Thursday, July 12, 2012 - The importance of having Side Projects and Internationalization. iOS and Mac Podcasts Plain Wallpapers Cheddar API Question from Paul Dunahoo. Thursday, July 12, 2012 - The importance of having Side Projects and Internationalization. iOS and Mac Podcasts Plain Wallpapers Cheddar API Question from Paul Dunahoo. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #62: Size Does Matter http://developingperspective.com/2012/07/09/62/ Mon, 09 Jul 2012 11:27:00 -0400 David http://developingperspective.com/?p=55562 Monday, July 09, 2012 - Discussing the implications and considerations that a smaller iPad Mini would introduce.

    ]]>
    Monday, July 09, 2012 - Discussing the implications and considerations that a smaller iPad Mini would introduce.

    ]]>
    0 893 Monday, July 09, 2012 - Discussing the implications and considerations that a smaller iPad Mini would introduce. Monday, July 09, 2012 - Discussing the implications and considerations that a smaller iPad Mini would introduce. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #61: Having a healthy relationship with Twitter http://developingperspective.com/2012/07/05/61/ Thu, 05 Jul 2012 11:14:00 -0400 David http://developingperspective.com/?p=55561 Thursday, July 05, 2012 - How to make peace with checking Twitter/RSS feeds during your work day.

    Question via @EricWelander

    ]]>
    Thursday, July 05, 2012 - How to make peace with checking Twitter/RSS feeds during your work day.

    Question via @EricWelander

    ]]>
    0 884 Thursday, July 05, 2012 - How to make peace with checking Twitter/RSS feeds during your work day. Question via @EricWelander Thursday, July 05, 2012 - How to make peace with checking Twitter/RSS feeds during your work day. Question via @EricWelander iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #60: The Path to Independence http://developingperspective.com/2012/07/02/60/ Mon, 02 Jul 2012 15:18:00 -0400 David http://developingperspective.com/?p=55560 Monday, July 02, 2012 - A discussion of the path any developer can take to move towards independence.

    Question via Mason.

    ]]>
    Monday, July 02, 2012 - A discussion of the path any developer can take to move towards independence.

    Question via Mason.

    ]]>
    0 898 Monday, July 02, 2012 - A discussion of the path any developer can take to move towards independence. Question via Mason. Monday, July 02, 2012 - A discussion of the path any developer can take to move towards independence. Question via Mason. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #59: Good and Real Reasons http://developingperspective.com/2012/06/27/59/ Wed, 27 Jun 2012 11:47:00 -0400 David http://developingperspective.com/?p=55559 Wednesday, June 27, 2012 - Using Octopress, the new Podcasts app, watching WWDC videos and why I got a Retina MacBook Pro.

    Links:

    ]]>
    Wednesday, June 27, 2012 - Using Octopress, the new Podcasts app, watching WWDC videos and why I got a Retina MacBook Pro.

    Links:

    ]]>
    0 893 Wednesday, June 27, 2012 - Using Octopress, the new Podcasts app, watching WWDC videos and why I got a Retina MacBook Pro. Links: Octopress Podcasts App WWDC Videos Retina MacBook Pro Wednesday, June 27, 2012 - Using Octopress, the new Podcasts app, watching WWDC videos and why I got a Retina MacBook Pro. Links: Octopress Podcasts App WWDC Videos Retina MacBook Pro iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #58: Managing new SDKs http://developingperspective.com/2012/06/21/58/ Thu, 21 Jun 2012 16:43:00 -0400 David http://developingperspective.com/?p=55558 Thursday, June 21, 2012 - How to manage the various SDK versions that Apple has floating around while making sure you can always ship.

    Question via @nalenb

    ]]>
    Thursday, June 21, 2012 - How to manage the various SDK versions that Apple has floating around while making sure you can always ship.

    Question via @nalenb

    ]]>
    0 761 Thursday, June 21, 2012 - How to manage the various SDK versions that Apple has floating around while making sure you can always ship. Question via @nalenb Thursday, June 21, 2012 - How to manage the various SDK versions that Apple has floating around while making sure you can always ship. Question via @nalenb iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #57: A Developer’s Machine http://developingperspective.com/2012/06/19/57/ Tue, 19 Jun 2012 16:09:00 -0400 David http://developingperspective.com/?p=55557 Tuesday, June 19, 2012 - A moment of solidarity for developers who work from home with their children. The main topic is a discussion of the current landscape of developer machines and why I think the new MacBook Pro is probably the best choice right now.

    #29: Working in an Office

    ]]>
    Tuesday, June 19, 2012 - A moment of solidarity for developers who work from home with their children. The main topic is a discussion of the current landscape of developer machines and why I think the new MacBook Pro is probably the best choice right now.

    #29: Working in an Office

    ]]>
    0 901 Tuesday, June 19, 2012 - A moment of solidarity for developers who work from home with their children. The main topic is a discussion of the current landscape of developer machines and why I think the new MacBook Pro is probably the best choice right now. #29: Working in an Office Tuesday, June 19, 2012 - A moment of solidarity for developers who work from home with their children. The main topic is a discussion of the current landscape of developer machines and why I think the new MacBook Pro is probably the best choice right now. #29: Working in an Office iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #56: Meritocracy http://developingperspective.com/2012/06/18/55-meritocracy/ Mon, 18 Jun 2012 14:02:00 -0400 David http://developingperspective.com/?p=298 Monday, June 18, 2012 — Reflections on how different this year’s WWDC was to last.

    ]]>
    Monday, June 18, 2012 — Reflections on how different this year’s WWDC was to last.

    ]]>
    0 682 Monday, June 18, 2012 — Reflections on how different this year’s WWDC was to last. Monday, June 18, 2012 — Reflections on how different this year’s WWDC was to last. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #55: Personal Connections http://developingperspective.com/2012/06/13/55-personal-connections/ Wed, 13 Jun 2012 15:04:54 -0400 David http://developingperspective.com/?p=296 I continue my WWDC shows with a discussion of my favorite features in iOS 6. The main discussion is about the value of personal connections and how great it is to meet people in person.

    ]]>
    I continue my WWDC shows with a discussion of my favorite features in iOS 6. The main discussion is about the value of personal connections and how great it is to meet people in person.

    ]]>
    0 867 I continue my WWDC shows with a discussion of my favorite features in iOS 6. The main discussion is about the value of personal connections and how great it is to meet people in person. The Value of a Handshake - Shawn Blanc I continue my WWDC shows with a discussion of my favorite features in iOS 6. The main discussion is about the value of personal connections and how great it is to meet people in person. The Value of a Handshake - Shawn Blanc iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #54: First Impressions from the WWDC Keynote http://developingperspective.com/2012/06/11/54-first-impressions-from-the-wwdc-keynote/ Mon, 11 Jun 2012 20:10:20 -0400 David http://developingperspective.com/?p=294 Recorded a few minutes after leaving the WWDC keynote I walk through my initial impressions on the announcements—the things that excite me and the things that disappointed me.

    ]]>
    Recorded a few minutes after leaving the WWDC keynote I walk through my initial impressions on the announcements—the things that excite me and the things that disappointed me.

    ]]>
    0 890 Recorded a few minutes after leaving the WWDC keynote I walk through my initial impressions on the announcements—the things that excite me and the things that disappointed me. Recorded a few minutes after leaving the WWDC keynote I walk through my initial impressions on the announcements—the things that excite me and the things that disappointed me. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #53: Please, be polite at WWDC. http://developingperspective.com/2012/06/08/53-please-be-polite-at-wwdc/ Fri, 08 Jun 2012 15:20:13 -0400 David http://developingperspective.com/?p=289 AKA: Please, don’t be a jerk at WWDC.

    • Be thankful to the Apple engineers and employees
    • Be considerate of others and your presenter during sessions
    • Make sure all your technology is on Silent (not vibrate)
    • Please, don’t noisily pack up your stuff and leave before the presenter concludes.  Wait until they are done.
    • Pick up your trash
    • Be polite in line and don’t hold spaces for unreasonable numbers of people
    • Don’t be a pushy salesman for your apps
    • Don’t overdo it.  Have Fun.  Pace yourself.
    ]]>
    AKA: Please, don’t be a jerk at WWDC.

    • Be thankful to the Apple engineers and employees
    • Be considerate of others and your presenter during sessions
    • Make sure all your technology is on Silent (not vibrate)
    • Please, don’t noisily pack up your stuff and leave before the presenter concludes.  Wait until they are done.
    • Pick up your trash
    • Be polite in line and don’t hold spaces for unreasonable numbers of people
    • Don’t be a pushy salesman for your apps
    • Don’t overdo it.  Have Fun.  Pace yourself.
    ]]>
    0 887 AKA: Please, don’t be a jerk at WWDC. Be thankful to the Apple engineers and employees Be considerate of others and your presenter during sessions Make sure all your technology is on Silent (not vibrate) Please, don’t noisily pack up your stuff and leave before the presenter concludes.  Wait until they are done. Pick up your trash Be polite in line and don’t hold spaces for unreasonable numbers of people Don’t be a pushy salesman for your apps Don’t overdo it.  Have Fun.  Pace yourself. AKA: Please, don’t be a jerk at WWDC. Be thankful to the Apple engineers and employees Be considerate of others and your presenter during sessions Make sure all your technology is on Silent (not vibrate) Please, don’t noisily pack up your stuff and leave before the presenter concludes.  Wait until they are done. Pick up your trash Be polite in line and don’t hold spaces for unreasonable numbers of people Don’t be a pushy salesman for your apps Don’t overdo it.  Have Fun.  Pace yourself. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #52: More Power http://developingperspective.com/2012/06/06/52-more-power/ Wed, 06 Jun 2012 20:32:45 -0400 David http://developingperspective.com/?p=287 The Mac Pro…can’t wait.

    ]]>
    The Mac Pro…can’t wait.

    ]]>
    0 868 The Mac Pro…can’t wait. Geekbench Scores The Mac Pro…can’t wait. Geekbench Scores iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #51: Fear the Robot http://developingperspective.com/2012/06/04/51-fear-the-robot/ Mon, 04 Jun 2012 20:28:53 -0400 David http://developingperspective.com/?p=285 Discussions on Multi-Platform Development and the new AppleTV

    ]]>
    Discussions on Multi-Platform Development and the new AppleTV

    ]]>
    0 833 Discussions on Multi-Platform Development and the new AppleTV Instapaper for Android Show 5 and Show 0.8 Discussions on Multi-Platform Development and the new AppleTV Instapaper for Android Show 5 and Show 0.8 iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #50: ‘Hacking’ the App Store http://developingperspective.com/2012/05/30/50-hacking-the-app-store/ Wed, 30 May 2012 14:03:42 -0400 David http://developingperspective.com/?p=280
  • How to effectively use the WWDC app
  • Instapaper on Kindle
  • Practical lessons from How to build an App Empire
  • ]]>
  • How to effectively use the WWDC app
  • Instapaper on Kindle
  • Practical lessons from How to build an App Empire
  • ]]>
    0 830 How to effectively use the WWDC app Instapaper on Kindle Practical lessons from How to build an App Empire How to effectively use the WWDC app Instapaper on Kindle Practical lessons from How to build an App Empire iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #49: Addressing Demand http://developingperspective.com/2012/05/23/49-addressing-demand/ Wed, 23 May 2012 14:04:01 -0400 David http://developingperspective.com/?p=277
  • Getting Crash Reports from iTunes Connect
  • Tracking user retention with update stats
  • Pricing as a way to maximize revenue
  • ]]>
  • Getting Crash Reports from iTunes Connect
  • Tracking user retention with update stats
  • Pricing as a way to maximize revenue
  • ]]>
    0 881 Getting Crash Reports from iTunes Connect Tracking user retention with update stats Pricing as a way to maximize revenue Getting Crash Reports from iTunes Connect Tracking user retention with update stats Pricing as a way to maximize revenue iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #48: All Good Things… http://developingperspective.com/2012/05/21/48-all-good-things/ Mon, 21 May 2012 14:51:33 -0400 David http://developingperspective.com/?p=270 A few thoughts about The Talk Show leaving 5by5.

    A discussion of the process of an app being featured in the App Store.

    Dan’s response to The Talk Show leaving: http://5by5.tv/specials/6

    John’s new show, The Talk Show: link

    Dan’s new show, Big Week: link

    ]]>
    A few thoughts about The Talk Show leaving 5by5.

    A discussion of the process of an app being featured in the App Store.

    Dan’s response to The Talk Show leaving: http://5by5.tv/specials/6

    John’s new show, The Talk Show: link

    Dan’s new show, Big Week: link

    ]]>
    0 881 A few thoughts about The Talk Show leaving 5by5. A discussion of the process of an app being featured in the App Store. 5by5 | The Talk Show #56: That Day Has Come Thanks @gruber and @danbenjamin Dan’s response to The Talk Show leaving: http://5by5.tv/specials/6 John’s new show, The Talk Show: link Dan’s new show, Big Week: link A few thoughts about The Talk Show leaving 5by5. A discussion of the process of an app being featured in the App Store. 5by5 | The Talk Show #56: That Day Has Come Thanks @gruber and @danbenjamin Dan’s response to The Talk Show leaving: http://5by5.tv/specials/6 John’s new show, The Talk Show: link Dan’s new show, Big Week: link iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #47: Just beyond your grasp http://developingperspective.com/2012/05/16/47-just-beyond-your-grasp/ Wed, 16 May 2012 14:05:25 -0400 David http://developingperspective.com/?p=267 Brief followup about yesterday’s launch of Audiobooks, then a thorough discussion of setting goals and how to define success for yourself.

    ]]>
    Brief followup about yesterday’s launch of Audiobooks, then a thorough discussion of setting goals and how to define success for yourself.

    ]]>
    0 894 Brief followup about yesterday’s launch of Audiobooks, then a thorough discussion of setting goals and how to define success for yourself. Brief followup about yesterday’s launch of Audiobooks, then a thorough discussion of setting goals and how to define success for yourself. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #46: On the Rocket http://developingperspective.com/2012/05/15/46-on-the-rocket/ Tue, 15 May 2012 14:02:35 -0400 David http://developingperspective.com/?p=264 A brief reminder to think of questions for WWDC, then a walkthrough of launch day.

    ]]>
    A brief reminder to think of questions for WWDC, then a walkthrough of launch day.

    ]]>
    0 863 A brief reminder to think of questions for WWDC, then a walkthrough of launch day. itcStatus Majic Rank Audiobooks A brief reminder to think of questions for WWDC, then a walkthrough of launch day. itcStatus Majic Rank Audiobooks iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #45: Failing in Success http://developingperspective.com/2012/05/11/45-failing-in-success/ Fri, 11 May 2012 23:46:50 -0400 David http://developingperspective.com/?p=259 A more personal and off-topic discussion of handling the unexpected success of being linked to.

    ]]>
    A more personal and off-topic discussion of handling the unexpected success of being linked to.

    ]]>
    0 842 A more personal and off-topic discussion of handling the unexpected success of being linked to. Back to Work #23: Failure is ALWAYS an Option Marco.org: iOS 5.1.1 upgrade stats My very first Episode: Show 0.1 My Blog: david-smith.org 5by5 Radio iOS App FiveLive: Mac Live Listening App A more personal and off-topic discussion of handling the unexpected success of being linked to. Back to Work #23: Failure is ALWAYS an Option Marco.org: iOS 5.1.1 upgrade stats My very first Episode: Show 0.1 My Blog: david-smith.org 5by5 Radio iOS App FiveLive: Mac Live Listening App iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #44: Free as in Beer http://developingperspective.com/2012/05/10/44-free-as-in-beer/ Thu, 10 May 2012 14:59:21 -0400 David http://developingperspective.com/?p=178
  • A little bit of housekeeping on the future and outlook for the show.
  • The role of free in the app store
  • How you can make user friendly iTunes affiliate links
  • Links:

    ]]>
  • A little bit of housekeeping on the future and outlook for the show.
  • The role of free in the app store
  • How you can make user friendly iTunes affiliate links
  • Links:

    ]]>
    0 878 A little bit of housekeeping on the future and outlook for the show. The role of free in the app store How you can make user friendly iTunes affiliate links Links: SimpleCasts User Friendly iTunes Affiliate Links A little bit of housekeeping on the future and outlook for the show. The role of free in the app store How you can make user friendly iTunes affiliate links Links: SimpleCasts User Friendly iTunes Affiliate Links iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #43: Dealing with Delay http://developingperspective.com/2012/05/09/43-dealing-with-delay/ Wed, 09 May 2012 15:19:50 -0400 David http://developingperspective.com/?p=176 Discussing dealing with the unpredictable nature of app development.  Starting with an example of how Audiobooks just got delayed and then hopefully giving some tips on how to handle disappointment.

    ]]>
    Discussing dealing with the unpredictable nature of app development.  Starting with an example of how Audiobooks just got delayed and then hopefully giving some tips on how to handle disappointment.

    ]]>
    0 888 Discussing dealing with the unpredictable nature of app development.  Starting with an example of how Audiobooks just got delayed and then hopefully giving some tips on how to handle disappointment. Discussing dealing with the unpredictable nature of app development.  Starting with an example of how Audiobooks just got delayed and then hopefully giving some tips on how to handle disappointment. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #42: Good money after Bad http://developingperspective.com/2012/05/08/42-good-money-after-bad/ Tue, 08 May 2012 14:28:47 -0400 David http://developingperspective.com/?p=173 Evaluating the various places you can try to pay to get your app attention and how they all fail.

    ]]>
    Evaluating the various places you can try to pay to get your app attention and how they all fail.

    ]]>
    0 814 Evaluating the various places you can try to pay to get your app attention and how they all fail. Evaluating the various places you can try to pay to get your app attention and how they all fail. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #41: Prepare for Launch http://developingperspective.com/2012/05/03/41-prepare-for-launch/ Thu, 03 May 2012 14:51:02 -0400 David http://developingperspective.com/?p=171 Discussion of the steps involved in actually shipping an app once all the coding is done:  iTunes Connect stuff, Marketing and promotion.

    ]]>
    Discussion of the steps involved in actually shipping an app once all the coding is done:  iTunes Connect stuff, Marketing and promotion.

    ]]>
    0 1190 Discussion of the steps involved in actually shipping an app once all the coding is done:  iTunes Connect stuff, Marketing and promotion. Discussion of the steps involved in actually shipping an app once all the coding is done:  iTunes Connect stuff, Marketing and promotion. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #40: Ship It http://developingperspective.com/2012/05/01/40-ship-it/ Tue, 01 May 2012 13:11:58 -0400 David http://developingperspective.com/?p=167 Discussing my process for doing a major app update.

    ]]>
    Discussing my process for doing a major app update.

    ]]>
    0 883 Discussing my process for doing a major app update. Things you should never do A lathe in use Audiobooks Discussing my process for doing a major app update. Things you should never do A lathe in use Audiobooks iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #39: The Grass is Shorter http://developingperspective.com/2012/04/30/39-the-grass-is-shorter/ Mon, 30 Apr 2012 19:11:36 -0400 David http://developingperspective.com/?p=163 A discussion of the risk, perils and benefits of growing your small, independent business.

    ]]>
    A discussion of the risk, perils and benefits of growing your small, independent business.

    ]]>
    0 917 A discussion of the risk, perils and benefits of growing your small, independent business. My Audiobooks app Build and Analyze: #75 My Twitterrific Moment A discussion of the risk, perils and benefits of growing your small, independent business. My Audiobooks app Build and Analyze: #75 My Twitterrific Moment iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #37: DubDub http://developingperspective.com/2012/04/18/37-dubdub/ Wed, 18 Apr 2012 14:22:31 -0400 David http://developingperspective.com/?p=160 A few thoughts on WWDC, the annual Apple Developers Conference.

    ]]>
    A few thoughts on WWDC, the annual Apple Developers Conference.

    ]]>
    0 917 A few thoughts on WWDC, the annual Apple Developers Conference. A few thoughts on WWDC, the annual Apple Developers Conference. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #36: Headline News http://developingperspective.com/2012/03/07/36-headline-news/ Wed, 07 Mar 2012 14:47:52 -0500 David http://developingperspective.com/?p=157 Some thoughts on the impending Apple Event.

    Recorded just prior to the announcement on March 7th.

    ]]>
    Some thoughts on the impending Apple Event.

    Recorded just prior to the announcement on March 7th.

    ]]>
    0 690 Some thoughts on the impending Apple Event. Recorded just prior to the announcement on March 7th. Some thoughts on the impending Apple Event. Recorded just prior to the announcement on March 7th. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #35: IcönFactory http://developingperspective.com/2012/02/16/35-iconfactory/ Thu, 16 Feb 2012 16:59:32 -0500 David http://developingperspective.com/?p=155 Discussion of securing iOS Address Book, iTunes Connect users, and OS X Mountain Lion.

    ]]>
    Discussion of securing iOS Address Book, iTunes Connect users, and OS X Mountain Lion.

    ]]>
    0 700 Discussion of securing iOS Address Book, iTunes Connect users, and OS X Mountain Lion. HashContacts: an iOS Address Book Wrapper OS X Mountain Lion Discussion of securing iOS Address Book, iTunes Connect users, and OS X Mountain Lion. HashContacts: an iOS Address Book Wrapper OS X Mountain Lion iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #34: Clear http://developingperspective.com/2012/02/15/34-clear/ Wed, 15 Feb 2012 14:17:46 -0500 David http://developingperspective.com/?p=152 Brief discussion of Clear, the new todo manager for iPhone and how its success should encourage indies.

    Developing Perspective is a podcast discussing news of note in iOS, Apple and the like.

    Never longer than 15 minutes.

    ]]>
    Brief discussion of Clear, the new todo manager for iPhone and how its success should encourage indies.

    Developing Perspective is a podcast discussing news of note in iOS, Apple and the like.

    Never longer than 15 minutes.

    ]]>
    0 519 Brief discussion of Clear, the new todo manager for iPhone and how its success should encourage indies. Clear Developing Perspective is a podcast discussing news of note in iOS, Apple and the like. Never longer than 15 minutes. Brief discussion of Clear, the new todo manager for iPhone and how its success should encourage indies. Clear Developing Perspective is a podcast discussing news of note in iOS, Apple and the like. Never longer than 15 minutes. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #33: Hosting for Indies http://developingperspective.com/2012/02/14/33-hosting-for-indies/ Tue, 14 Feb 2012 16:11:42 -0500 David http://developingperspective.com/?p=149 Discussion of the various hosting options for small, indie developers.

    ]]>
    Discussion of the various hosting options for small, indie developers.

    ]]>
    0 826 Discussion of the various hosting options for small, indie developers. Linode Engine Yard Discussion of the various hosting options for small, indie developers. Linode Engine Yard iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #32 - Cycles of Attention http://developingperspective.com/2012/02/10/32-cycles-of-attention/ Fri, 10 Feb 2012 14:33:38 -0500 David http://developingperspective.com/?p=146 Discussing how my attention and focus shifts between consulting and personal projects.

    ]]>
    Discussing how my attention and focus shifts between consulting and personal projects.

    ]]>
    0 768 Discussing how my attention and focus shifts between consulting and personal projects. Build and Analyze: #6: Cycles of Motivation Discussing how my attention and focus shifts between consulting and personal projects. Build and Analyze: #6: Cycles of Motivation iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #31 - Temple Space Verb http://developingperspective.com/2012/02/03/30-temple-space-verb/ Fri, 03 Feb 2012 14:46:56 -0500 David http://developingperspective.com/?p=141 A discussion of low quality apps that rip off great apps in the App Store.

    ]]>
    A discussion of low quality apps that rip off great apps in the App Store.

    ]]>
    0 864 A discussion of low quality apps that rip off great apps in the App Store. Temple Run Indiana Jones: Raiders of the Lost Ark A discussion of low quality apps that rip off great apps in the App Store. Temple Run Indiana Jones: Raiders of the Lost Ark iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #30: iOS Networking Stacks http://developingperspective.com/2012/02/02/30-ios-networking-stacks/ Thu, 02 Feb 2012 16:02:54 -0500 David http://developingperspective.com/?p=139
  • AFNetworking

  • MKNetworkKit

  • asi-http-request

  • NSURLConnection

  • Network Link Conditioner

  • ]]>
  • AFNetworking

  • MKNetworkKit

  • asi-http-request

  • NSURLConnection

  • Network Link Conditioner

  • ]]>
    0 768 AFNetworking MKNetworkKit asi-http-request NSURLConnection Network Link Conditioner AFNetworking MKNetworkKit asi-http-request NSURLConnection Network Link Conditioner iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #29: Working in an Office http://developingperspective.com/2012/01/26/29-working-in-an-office/ Thu, 26 Jan 2012 15:49:46 -0500 David http://developingperspective.com/?p=136 Discussion of why I work from an office, rather than from home.

    ]]>
    Discussion of why I work from an office, rather than from home.

    ]]>
    0 673 Discussion of why I work from an office, rather than from home. Regus Discussion of why I work from an office, rather than from home. Regus iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #28: Quiet and Authorship http://developingperspective.com/2012/01/20/28-quiet-and-authorship/ Fri, 20 Jan 2012 21:57:44 -0500 David http://developingperspective.com/?p=132
  • Forcing Quiet into my Day

  • Instapaper on the Kindle

  • Truly Unprecedented in iBooks 2

  • ]]>
  • Forcing Quiet into my Day

  • Instapaper on the Kindle

  • Truly Unprecedented in iBooks 2

  • ]]>
    0 890 Forcing Quiet into my Day Instapaper on the Kindle Truly Unprecedented in iBooks 2 Forcing Quiet into my Day Instapaper on the Kindle Truly Unprecedented in iBooks 2 iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #27: 53 Weeks In The App Store http://developingperspective.com/2011/12/28/27-53-weeks-in-the-app-store/ Wed, 28 Dec 2011 21:51:03 -0500 David http://developingperspective.com/?p=129 December 28, 2011

    The App Store Christmas Bump

    User Friendly iTunes Affiliate Links

    ]]>
    December 28, 2011

    The App Store Christmas Bump

    User Friendly iTunes Affiliate Links

    ]]>
    0 847 December 28, 2011 The App Store Christmas Bump User Friendly iTunes Affiliate Links December 28, 2011 The App Store Christmas Bump User Friendly iTunes Affiliate Links iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #26 - Remembering Steve. http://developingperspective.com/2011/10/07/26-remembering-steve/ Fri, 07 Oct 2011 15:00:05 -0400 David http://developingperspective.com/?p=126 Rambling thoughts from an Apple Fanboi.

    ]]>
    Rambling thoughts from an Apple Fanboi.

    ]]>
    0 826 Rambling thoughts from an Apple Fanboi. Rambling thoughts from an Apple Fanboi. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #25 - Secrets are Fun. http://developingperspective.com/2011/09/27/25-secrets-are-fun/ Tue, 27 Sep 2011 13:44:20 -0400 David http://developingperspective.com/?p=121 Tuesday, September 27, 2011

    ]]>
    Tuesday, September 27, 2011

    ]]>
    0 609 Tuesday, September 27, 2011 Git Is Simpler Than You Think A better introduction to Objective-C How to clean Apple products Developing in secret. On Wednesday, Amazon Will Unveil The “Kindle Fire” | TechCrunch Tuesday, September 27, 2011 Git Is Simpler Than You Think A better introduction to Objective-C How to clean Apple products Developing in secret. On Wednesday, Amazon Will Unveil The “Kindle Fire” | TechCrunch iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #24 - Staying focused. http://developingperspective.com/2011/09/16/24-staying-focused/ Fri, 16 Sep 2011 13:46:55 -0400 David http://developingperspective.com/?p=119 Friday, September 16, 2011

    ]]>
    Friday, September 16, 2011

    ]]>
    0 792 Friday, September 16, 2011 P versus NP ~/.osx — a collection of sensible defaults for OS X Lion Twenty-Five Pieces of Basic Sartorial Knowledge So You Don’t Look Dumb Bootstrapping a $30k profit/month company from our internship earnings Staying focused. Eight Traits of Great Metro Apps Friday, September 16, 2011 P versus NP ~/.osx — a collection of sensible defaults for OS X Lion Twenty-Five Pieces of Basic Sartorial Knowledge So You Don’t Look Dumb Bootstrapping a $30k profit/month company from our internship earnings Staying focused. Eight Traits of Great Metro Apps iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #23 - New iPhones http://developingperspective.com/2011/09/08/23-new-iphones/ Thu, 08 Sep 2011 15:27:48 -0400 David http://developingperspective.com/?p=116 Thursday, September 8, 2011

    ]]>
    Thursday, September 8, 2011

    ]]>
    0 651 Thursday, September 8, 2011 Lessons from Valve – How to build a designer’s paradise What’s Your Start-up’s “Bus Count”? 7 Myths of Entrepreneurship and Programming The London Tube Map, Redesigned For A Multiscreen World Pomodoro Technique Illustrated - by Staffan Nöteberg The new iPhone Thursday, September 8, 2011 Lessons from Valve – How to build a designer’s paradise What’s Your Start-up’s “Bus Count”? 7 Myths of Entrepreneurship and Programming The London Tube Map, Redesigned For A Multiscreen World Pomodoro Technique Illustrated - by Staffan Nöteberg The new iPhone iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #22 - After the Launch http://developingperspective.com/2011/09/06/22-after-the-launch/ Tue, 06 Sep 2011 13:26:45 -0400 David http://developingperspective.com/?p=114 Tuesday, September 6, 2011

    ]]>
    Tuesday, September 6, 2011

    ]]>
    0 828 Tuesday, September 6, 2011 GOLD3N RATIO Six Stages of Debugging xdissent/ievms - GitHub Amazon’s Kindle Tablet Is Very Real. I’ve Seen It, Played With It. | TechCrunch After the launch 148Apps.biz | Apple iTunes App Store Metrics, Statistics and Numbers for iPhone Apps Tuesday, September 6, 2011 GOLD3N RATIO Six Stages of Debugging xdissent/ievms - GitHub Amazon’s Kindle Tablet Is Very Real. I’ve Seen It, Played With It. | TechCrunch After the launch 148Apps.biz | Apple iTunes App Store Metrics, Statistics and Numbers for iPhone Apps iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #21 - Submitting to the App Store http://developingperspective.com/2011/09/02/21-submitting-to-the-app-store/ Fri, 02 Sep 2011 21:15:01 -0400 David http://developingperspective.com/?p=111 Friday, September 2, 2011

    ]]>
    Friday, September 2, 2011

    ]]>
    0 828 Friday, September 2, 2011 Linode Reduces Transfer Pricing (Incoming Data is now Free) Texture Tutorial on Vimeo The Price of (Dev) Happiness: Part Two Submitting to the App Store iTunes Connect Friday, September 2, 2011 Linode Reduces Transfer Pricing (Incoming Data is now Free) Texture Tutorial on Vimeo The Price of (Dev) Happiness: Part Two Submitting to the App Store iTunes Connect iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #20 - Parkinson’s Law http://developingperspective.com/2011/09/01/20-parkinsons-law/ Thu, 01 Sep 2011 13:48:50 -0400 David http://developingperspective.com/?p=108 Thursday, September 1, 2011

    ]]>
    Thursday, September 1, 2011

    ]]>
    0 786 Thursday, September 1, 2011 Why Markdown? A two-minute explanation Spotify inside your iOS app GitHub Flow How Steve Jobs handles trolls (WWDC 1997) 5% off everything. Avoiding Parkinson’s Law Parkinson’s Law Thursday, September 1, 2011 Why Markdown? A two-minute explanation Spotify inside your iOS app GitHub Flow How Steve Jobs handles trolls (WWDC 1997) 5% off everything. Avoiding Parkinson’s Law Parkinson’s Law iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #19 - Setting up for the App Store http://developingperspective.com/2011/08/31/19-setting-up-for-the-app-store/ Wed, 31 Aug 2011 14:04:44 -0400 David http://developingperspective.com/?p=105 Wednesday, August 31, 2011

    ]]>
    Wednesday, August 31, 2011

    ]]>
    0 896 Wednesday, August 31, 2011 Learn Vim Progressively XPCKit Importing and displaying large data sets in Core Data A simple way to create custom Rounded Rect Buttons The Apple Logo Getting setup for submitting an app Developer Portal Wednesday, August 31, 2011 Learn Vim Progressively XPCKit Importing and displaying large data sets in Core Data A simple way to create custom Rounded Rect Buttons The Apple Logo Getting setup for submitting an app Developer Portal iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #18 - Books and Learning http://developingperspective.com/2011/08/30/18-books-and-learning/ Tue, 30 Aug 2011 13:26:10 -0400 David http://developingperspective.com/?p=99 Monday, August 19, 2011

    ]]>
    Monday, August 19, 2011

    ]]>
    0 747 Monday, August 19, 2011 A Tribute to Steve: 21KM Apple Logo Objective-C - GitHub What’s New for Developers in Mac OS X Lion (Part 3) Exporting from Photoshop How I learn new languages. The Pragmatic Studio | Top Developer Training Monday, August 19, 2011 A Tribute to Steve: 21KM Apple Logo Objective-C - GitHub What’s New for Developers in Mac OS X Lion (Part 3) Exporting from Photoshop How I learn new languages. The Pragmatic Studio | Top Developer Training iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #17 - Aligning Incentives http://developingperspective.com/2011/08/26/17-aligning-incentives/ Fri, 26 Aug 2011 14:41:08 -0400 David http://developingperspective.com/?p=97 Friday, August 26, 2011

    ]]>
    Friday, August 26, 2011

    ]]>
    0 893 Friday, August 26, 2011 thoughtbot playbook What’s New for Developers in Mac OS X Lion (Part 2) Rob “CmdrTaco” Malda Resigns From Slashdot How we found the file that was used to Hack RSA If I Launched a Startup | Startup Lawyer My hourly billing system Why I prefer fixed price over hourly contracts Friday, August 26, 2011 thoughtbot playbook What’s New for Developers in Mac OS X Lion (Part 2) Rob “CmdrTaco” Malda Resigns From Slashdot How we found the file that was used to Hack RSA If I Launched a Startup | Startup Lawyer My hourly billing system Why I prefer fixed price over hourly contracts iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #16 - Thank You Steve http://developingperspective.com/2011/08/25/16-thank-you-steve/ Thu, 25 Aug 2011 15:18:33 -0400 David http://developingperspective.com/?p=95 Thursday, August 25, 2011

    Thoughts on Steve’s transition to Chairman of the Board.

    ]]>
    Thursday, August 25, 2011

    Thoughts on Steve’s transition to Chairman of the Board.

    ]]>
    0 689 Thursday, August 25, 2011 Letter from Steve Jobs Thoughts on Steve’s transition to Chairman of the Board. Thursday, August 25, 2011 Letter from Steve Jobs Thoughts on Steve’s transition to Chairman of the Board. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #15 - Counting your Time http://developingperspective.com/2011/08/24/15-counting-your-time/ Wed, 24 Aug 2011 13:45:36 -0400 David http://developingperspective.com/?p=91 Wednesday, August 24, 2011

    ]]>
    Wednesday, August 24, 2011

    ]]>
    0 887 Wednesday, August 24, 2011 Plausible Labs » A software… cooperative? Creating web apps for iOS How to Get $12 Billion of Gold to Venezuela ∞ Mac Pro Fast How to measure your time American Bar Association Guidelines Wednesday, August 24, 2011 Plausible Labs » A software… cooperative? Creating web apps for iOS How to Get $12 Billion of Gold to Venezuela ∞ Mac Pro Fast How to measure your time American Bar Association Guidelines iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #14 - My Setup http://developingperspective.com/2011/08/23/14-my-setup/ Tue, 23 Aug 2011 18:50:23 -0400 David http://developingperspective.com/?p=89 Tuesday, August 23, 2011

    ]]>
    Tuesday, August 23, 2011

    ]]>
    0 888 Tuesday, August 23, 2011 Irradiated Software - SizeUp github/gitignore at master A letter from _why Recent / iOS UI Patterns (beta) My Setup Tuesday, August 23, 2011 Irradiated Software - SizeUp github/gitignore at master A letter from _why Recent / iOS UI Patterns (beta) My Setup iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #13 - Perspective http://developingperspective.com/2011/08/22/13-perspective/ Mon, 22 Aug 2011 15:14:35 -0400 David http://developingperspective.com/?p=86 Monday, August 22, 2011

    Importance of Perspective

    ]]>
    Monday, August 22, 2011

    Importance of Perspective

    ]]>
    0 572 Monday, August 22, 2011 on_the_path_gitflow Learn Ruby The Hard Way The Macalope Weekly: Gotta know when to hold ‘em, know when to fold ‘em Importance of Perspective Monday, August 22, 2011 on_the_path_gitflow Learn Ruby The Hard Way The Macalope Weekly: Gotta know when to hold ‘em, know when to fold ‘em Importance of Perspective iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #12 - Going on Vacation http://developingperspective.com/2011/08/12/12-going-on-vacation/ Fri, 12 Aug 2011 16:39:54 -0400 David http://developingperspective.com/?p=83 Friday, August 12, 2011

    I’m heading out for vacation until August 22nd.  In the meantime enjoy the archives.

    ]]>
    Friday, August 12, 2011

    I’m heading out for vacation until August 22nd.  In the meantime enjoy the archives.

    ]]>
    0 735 Friday, August 12, 2011 Camels and Rubber Duckies Polyglot Platform Personal Style carlbrown/PDKeychainBindingsController Less Code, less effort. Discussion on taking vacation and rest as an independent. I’m heading out for vacation until August 22nd.  In the meantime enjoy the archives. Friday, August 12, 2011 Camels and Rubber Duckies Polyglot Platform Personal Style carlbrown/PDKeychainBindingsController Less Code, less effort. Discussion on taking vacation and rest as an independent. I’m heading out for vacation until August 22nd.  In the meantime enjoy the archives. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #11 - My Workflow http://developingperspective.com/2011/08/11/11-my-workflow/ Thu, 11 Aug 2011 14:45:10 -0400 David http://developingperspective.com/?p=81 Thursday, August 11, 2011

    ]]>
    Thursday, August 11, 2011

    ]]>
    0 897 Thursday, August 11, 2011 The Price of (Dev) Happiness: Part One Adam Lisagor Is The Quietest Pitchman Sandwich Video Giving up on giving up TextMate Amazon Kindle Cloud Reader Kindle Cloud. Almost but not quite. My workflow Instapaper Rode Podcaster Audacity Transmit Thursday, August 11, 2011 The Price of (Dev) Happiness: Part One Adam Lisagor Is The Quietest Pitchman Sandwich Video Giving up on giving up TextMate Amazon Kindle Cloud Reader Kindle Cloud. Almost but not quite. My workflow Instapaper Rode Podcaster Audacity Transmit iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #10 - A Digital Diet http://developingperspective.com/2011/08/10/10-a-digital-diet/ Wed, 10 Aug 2011 17:13:40 -0400 David http://developingperspective.com/?p=79 Wednesday, August 10, 2011

    ]]>
    Wednesday, August 10, 2011

    ]]>
    0 879 Wednesday, August 10, 2011 The Growing User and the Perennial Beginner Apple - Recycling Program Lion Recovery Disk Assistant Automatic Reference Counting for Some Files Bash prompt, five examples to set your own A discussion of avoiding becoming addicted to digital information and more conscious about your time and attention. Wednesday, August 10, 2011 The Growing User and the Perennial Beginner Apple - Recycling Program Lion Recovery Disk Assistant Automatic Reference Counting for Some Files Bash prompt, five examples to set your own A discussion of avoiding becoming addicted to digital information and more conscious about your time and attention. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #9 - Just Getting Started http://developingperspective.com/2011/08/09/9-just-getting-started/ Tue, 09 Aug 2011 13:41:03 -0400 David http://developingperspective.com/?p=77 Tuesday, August 9, 2011

    ]]>
    Tuesday, August 9, 2011

    ]]>
    0 868 Tuesday, August 9, 2011 Lion Adoption Agile Week 2011: 40% off The Definitive Guide To Forms based Website Authentication The Trivialities and Transcendence of Kickstarter Talking Stocks What does “organic” really mean? Getting started and celebrations for my 20th episode Back to Work #23: Failure is ALWAYS an Option Tuesday, August 9, 2011 Lion Adoption Agile Week 2011: 40% off The Definitive Guide To Forms based Website Authentication The Trivialities and Transcendence of Kickstarter Talking Stocks What does “organic” really mean? Getting started and celebrations for my 20th episode Back to Work #23: Failure is ALWAYS an Option iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #8 - Living the ‘Lifestyle’ http://developingperspective.com/2011/08/08/8-living-the-lifestyle/ Mon, 08 Aug 2011 13:41:46 -0400 David http://developingperspective.com/?p=71 Monday, August 8, 2011

    ]]>
    Monday, August 8, 2011

    ]]>
    0 758 Monday, August 8, 2011 Show TODO’s And FIXME’s As Warnings In Xcode 4 - Deallocated Objects by Jake Marsh Network Link Conditioner in Lion » Matt Legend Gemmell CodeKata: Code Kata Musing on having a ‘lifestyle’ business The Blogfather Monday, August 8, 2011 Show TODO’s And FIXME’s As Warnings In Xcode 4 - Deallocated Objects by Jake Marsh Network Link Conditioner in Lion » Matt Legend Gemmell CodeKata: Code Kata Musing on having a ‘lifestyle’ business The Blogfather iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    #7 - Healthcare for Indies http://developingperspective.com/2011/08/05/7-healthcare-for-indies/ Fri, 05 Aug 2011 13:51:02 -0400 David http://developingperspective.com/?p=68 Friday, August 5, 2011

    ]]>
    Friday, August 5, 2011

    ]]>
    0 874 Friday, August 5, 2011 Learn Ruby The Hard Way Why “Coupon Code” Should Not be a Field on Your Payment Form Mac OS X 10.7 Lion Automation Release Notes Free icons for any object in the world Why wireless networks are slow Build and Analyze #36: Jobs (Not The Steve Kind) Friday, August 5, 2011 Learn Ruby The Hard Way Why “Coupon Code” Should Not be a Field on Your Payment Form Mac OS X 10.7 Lion Automation Release Notes Free icons for any object in the world Why wireless networks are slow Build and Analyze #36: Jobs (Not The Steve Kind) iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 6 http://developingperspective.com/2011/08/04/show-6/ Thu, 04 Aug 2011 14:45:22 -0400 David http://developingperspective.com/?p=64 Thursday, August 4, 2011

    ]]>
    Thursday, August 4, 2011

    ]]>
    0 876 Thursday, August 4, 2011 By The Numbers: What Can An OWC 6G SSD Do For Your 2011 Mac mini? Meet Comex, The 19-Year-Old iPhone Uber-Hacker Who Keeps Outsmarting Apple Tweetbot 1.4.3 The Making of Drunkify The Problem with All-Star Teams ★ Google: Patently Absurd Handling Interruptions and Focus ∞ Digital Interruptions Pomodoro Technique Illustrated Thursday, August 4, 2011 By The Numbers: What Can An OWC 6G SSD Do For Your 2011 Mac mini? Meet Comex, The 19-Year-Old iPhone Uber-Hacker Who Keeps Outsmarting Apple Tweetbot 1.4.3 The Making of Drunkify The Problem with All-Star Teams ★ Google: Patently Absurd Handling Interruptions and Focus ∞ Digital Interruptions Pomodoro Technique Illustrated iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 5 http://developingperspective.com/2011/08/03/show-5/ Wed, 03 Aug 2011 14:46:27 -0400 David http://developingperspective.com/?p=62 Wednesday, August 3, 2011

    ]]>
    Wednesday, August 3, 2011

    ]]>
    0 678 Wednesday, August 3, 2011 Essential TextMate Shortcuts, Tips and Techniques Streamline your git workflow with aliases Core i5 MacBook Airs approach perfection Review An iOS Developer Takes on Android Faceplanting: an app launch horror story with a twist Amazon Appstore Amazon Free App of the Day A Tale of Three App Stores Wednesday, August 3, 2011 Essential TextMate Shortcuts, Tips and Techniques Streamline your git workflow with aliases Core i5 MacBook Airs approach perfection Review An iOS Developer Takes on Android Faceplanting: an app launch horror story with a twist Amazon Appstore Amazon Free App of the Day A Tale of Three App Stores iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 4 http://developingperspective.com/2011/08/02/show-4/ Tue, 02 Aug 2011 13:28:12 -0400 David http://developingperspective.com/?p=59 Tuesday, August 2, 2011

    ]]>
    Tuesday, August 2, 2011

    ]]>
    0 874 Tuesday, August 2, 2011 Apple - iCloud stores your content and pushes it to your devices. Method and Apparatus for Kicking Ass Invisible Scrollbars iOS and Mac Development Link Roundup: July 2011 Understanding the Git Workflow Backups RAID is not Backup Tuesday, August 2, 2011 Apple - iCloud stores your content and pushes it to your devices. Method and Apparatus for Kicking Ass Invisible Scrollbars iOS and Mac Development Link Roundup: July 2011 Understanding the Git Workflow Backups RAID is not Backup iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 3 http://developingperspective.com/2011/08/01/show-3/ Mon, 01 Aug 2011 18:23:58 -0400 David http://developingperspective.com/?p=56 Monday, August 1, 2011

    ]]>
    Monday, August 1, 2011

    ]]>
    0 864 Monday, August 1, 2011 Marketing Hacks for iOS: How we got 250k downloads in 4 days. Making Lion Work Right For Me A few days of programming on iOS and Android illustrates a vast difference The Future of the Mac After Lion What tiny thing in Lion makes you smile or has caught you off guard? Discussing tools and their role in successful development Enjoyment of one’s tools — The Endeavour Monday, August 1, 2011 Marketing Hacks for iOS: How we got 250k downloads in 4 days. Making Lion Work Right For Me A few days of programming on iOS and Android illustrates a vast difference The Future of the Mac After Lion What tiny thing in Lion makes you smile or has caught you off guard? Discussing tools and their role in successful development Enjoyment of one’s tools — The Endeavour iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 2 http://developingperspective.com/2011/07/29/show-2/ Fri, 29 Jul 2011 13:40:33 -0400 David http://developingperspective.com/?p=51 Friday, July 29, 2011

    ]]>
    Friday, July 29, 2011

    ]]>
    0 723 Friday, July 29, 2011 Articles about the App Store, design and Bjango Apple captured two thirds of available mobile phone profits in Q2 Secrets myell0w/MTStatusBarOverlay Using 3rd party code in your app Friday, July 29, 2011 Articles about the App Store, design and Bjango Apple captured two thirds of available mobile phone profits in Q2 Secrets myell0w/MTStatusBarOverlay Using 3rd party code in your app iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 1.0 http://developingperspective.com/2011/07/28/show-1-0/ Thu, 28 Jul 2011 19:33:00 -0400 David http://developingperspective.com/?p=49 Thursday, July 28, 2011

    ]]>
    Thursday, July 28, 2011

    ]]>
    0 651 Thursday, July 28, 2011 Is Compilation CPU Bound? Invest In Yourself Wanted: Technical Writer / Tinkerer ∞ How I Evaluate and Decide to Purchase New iOS Apps App Store Sales Volatility Writing without version 1.1 Thursday, July 28, 2011 Is Compilation CPU Bound? Invest In Yourself Wanted: Technical Writer / Tinkerer ∞ How I Evaluate and Decide to Purchase New iOS Apps App Store Sales Volatility Writing without version 1.1 iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.11 http://developingperspective.com/2011/07/27/show-0-11/ Wed, 27 Jul 2011 14:41:41 -0400 David http://developingperspective.com/?p=47 Wednesday, July 27, 2011

    ]]>
    Wednesday, July 27, 2011

    ]]>
    0 572 Wednesday, July 27, 2011 mattt/FormatterKit Rails Ultimate Install Guide on OS X Lion Defining quality Read It Later Raises $2.5 Million, Wants To Become The Dropbox Of Content Mac Value Analysis Wednesday, July 27, 2011 mattt/FormatterKit Rails Ultimate Install Guide on OS X Lion Defining quality Read It Later Raises $2.5 Million, Wants To Become The Dropbox Of Content Mac Value Analysis iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.10 http://developingperspective.com/2011/07/26/show-0-10/ Tue, 26 Jul 2011 15:09:40 -0400 David http://developingperspective.com/?p=44 Tuesday, July 26, 2011

    ]]>
    Tuesday, July 26, 2011

    ]]>
    0 696 Tuesday, July 26, 2011 Pilky.me - The Xcode 4.1 Review iOS reading apps begin ditching outside store links in droves 1Click Bookmarks | 1Password 3 User Guide Text files and me IV - BBEdit and TextMate Subtle Patterns Free High Resolution Textures Founders and Indies Tuesday, July 26, 2011 Pilky.me - The Xcode 4.1 Review iOS reading apps begin ditching outside store links in droves 1Click Bookmarks | 1Password 3 User Guide Text files and me IV - BBEdit and TextMate Subtle Patterns Free High Resolution Textures Founders and Indies iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.9 http://developingperspective.com/2011/07/25/show-0-9/ Mon, 25 Jul 2011 14:04:13 -0400 David http://developingperspective.com/?p=41 Monday, July 25, 2011

    ]]>
    Monday, July 25, 2011

    ]]>
    0 612 Monday, July 25, 2011 A robot that flies like a bird Mac mini Hosting Intellectual Ventures And The War Over Software Patents When Patents Atack On Succeeding Steve Jobs mogenerator 1.23 Whole Disk Encryption Benchmarks iOS 5 Over-the-Air Update Monday, July 25, 2011 A robot that flies like a bird Mac mini Hosting Intellectual Ventures And The War Over Software Patents When Patents Atack On Succeeding Steve Jobs mogenerator 1.23 Whole Disk Encryption Benchmarks iOS 5 Over-the-Air Update iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.8 http://developingperspective.com/2011/07/22/show-0-8/ Fri, 22 Jul 2011 15:04:14 -0400 David http://developingperspective.com/?p=29
  • Lodsys sues Rovio over Angry Birds for iPhone and Android

  • The iPad’s Dominance of the Tablet Market

  • Multiple APK Support in Android Market

  • Troubleshooting / Lion — TextMate Wiki

  • MacBook Air 13” Mid 2011 Teardown

  • Mac Mini Mid 2011 Teardown

  • iAd for Developers

  • ]]>
  • Lodsys sues Rovio over Angry Birds for iPhone and Android

  • The iPad’s Dominance of the Tablet Market

  • Multiple APK Support in Android Market

  • Troubleshooting / Lion — TextMate Wiki

  • MacBook Air 13” Mid 2011 Teardown

  • Mac Mini Mid 2011 Teardown

  • iAd for Developers

  • ]]>
    0 618 Lodsys sues Rovio over Angry Birds for iPhone and Android The iPad’s Dominance of the Tablet Market Multiple APK Support in Android Market Troubleshooting / Lion — TextMate Wiki MacBook Air 13” Mid 2011 Teardown Mac Mini Mid 2011 Teardown iAd for Developers Lodsys sues Rovio over Angry Birds for iPhone and Android The iPad’s Dominance of the Tablet Market Multiple APK Support in Android Market Troubleshooting / Lion — TextMate Wiki MacBook Air 13” Mid 2011 Teardown Mac Mini Mid 2011 Teardown iAd for Developers iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.7 http://developingperspective.com/2011/07/21/show-0-7/ Thu, 21 Jul 2011 14:54:16 -0400 David http://developingperspective.com/?p=26
  • Cloud Sync Beta

  • Introducing Lion Recovery

  • Lion’s Whole-Disk Encryption

  • Petabytes on a Budget v2.0:Revealing More Secrets

  • Developer Machine Landscape

  • ]]>
  • Cloud Sync Beta

  • Introducing Lion Recovery

  • Lion’s Whole-Disk Encryption

  • Petabytes on a Budget v2.0:Revealing More Secrets

  • Developer Machine Landscape

  • ]]>
    0 871 Cloud Sync Beta Introducing Lion Recovery Lion’s Whole-Disk Encryption Petabytes on a Budget v2.0:Revealing More Secrets Developer Machine Landscape Cloud Sync Beta Introducing Lion Recovery Lion’s Whole-Disk Encryption Petabytes on a Budget v2.0:Revealing More Secrets Developer Machine Landscape iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.6 http://developingperspective.com/2011/07/20/show-0-6/ Wed, 20 Jul 2011 17:02:30 -0400 David http://developingperspective.com/?p=24
  • BBEdit 10 is here!

  • Google: The Beginning

  • Why doesn’t every company buy developers the best hardware?

  • Seven under-the-radar Lion features you might have missed

  • Apple - Press Info - Apple Reports Third Quarter Results

  • Mac OS X 10.7 Lion: the Ars Technica review

  • ]]>
  • BBEdit 10 is here!

  • Google: The Beginning

  • Why doesn’t every company buy developers the best hardware?

  • Seven under-the-radar Lion features you might have missed

  • Apple - Press Info - Apple Reports Third Quarter Results

  • Mac OS X 10.7 Lion: the Ars Technica review

  • ]]>
    0 610 BBEdit 10 is here! Google: The Beginning Why doesn’t every company buy developers the best hardware? Seven under-the-radar Lion features you might have missed Apple - Press Info - Apple Reports Third Quarter Results Mac OS X 10.7 Lion: the Ars Technica review BBEdit 10 is here! Google: The Beginning Why doesn’t every company buy developers the best hardware? Seven under-the-radar Lion features you might have missed Apple - Press Info - Apple Reports Third Quarter Results Mac OS X 10.7 Lion: the Ars Technica review iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.5 http://developingperspective.com/2011/07/19/show-0-5/ Tue, 19 Jul 2011 13:38:32 -0400 David http://developingperspective.com/?p=21
  • Reading on the iPad

  • iPad 2 and Verizon iPhone Take Some Wind Out of Android’s Sail

  • Designing GitHub for Mac

  • What Google’s Famous Cafeterias Can Teach Us About Health

  • The iPhone’s Home Button

  • The Back Button Dilemma

  • Rumors.

  • ]]>
  • Reading on the iPad

  • iPad 2 and Verizon iPhone Take Some Wind Out of Android’s Sail

  • Designing GitHub for Mac

  • What Google’s Famous Cafeterias Can Teach Us About Health

  • The iPhone’s Home Button

  • The Back Button Dilemma

  • Rumors.

  • ]]>
    0 626 Reading on the iPad iPad 2 and Verizon iPhone Take Some Wind Out of Android’s Sail Designing GitHub for Mac What Google’s Famous Cafeterias Can Teach Us About Health The iPhone’s Home Button The Back Button Dilemma Rumors. Reading on the iPad iPad 2 and Verizon iPhone Take Some Wind Out of Android’s Sail Designing GitHub for Mac What Google’s Famous Cafeterias Can Teach Us About Health The iPhone’s Home Button The Back Button Dilemma Rumors. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.4 http://developingperspective.com/2011/07/18/show-0-4/ Mon, 18 Jul 2011 14:53:13 -0400 David http://developingperspective.com/?p=19
  • Michael Gartenberg: ‘Why Apple Dares to Change Your Apps’

  • Yes to Lion, no to cruft: get a clean start with manual Mac migration

  • Auto-Incrementing Build Numbers for Release Builds in Xcode

  • Founder Stories Volume 01: Slicehost

  • iOS Integration Testing

  • God in a Cup

  • ]]>
  • Michael Gartenberg: ‘Why Apple Dares to Change Your Apps’

  • Yes to Lion, no to cruft: get a clean start with manual Mac migration

  • Auto-Incrementing Build Numbers for Release Builds in Xcode

  • Founder Stories Volume 01: Slicehost

  • iOS Integration Testing

  • God in a Cup

  • ]]>
    0 706 Michael Gartenberg: ‘Why Apple Dares to Change Your Apps’ Yes to Lion, no to cruft: get a clean start with manual Mac migration Auto-Incrementing Build Numbers for Release Builds in Xcode Founder Stories Volume 01: Slicehost iOS Integration Testing God in a Cup Michael Gartenberg: ‘Why Apple Dares to Change Your Apps’ Yes to Lion, no to cruft: get a clean start with manual Mac migration Auto-Incrementing Build Numbers for Release Builds in Xcode Founder Stories Volume 01: Slicehost iOS Integration Testing God in a Cup iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.3 http://developingperspective.com/2011/07/15/show-0-3/ Fri, 15 Jul 2011 14:19:00 -0400 David http://developingperspective.com/?p=15
  • An Analysis Of Apple’s Adjustment Of International App Store Prices

  • Ready, Set, Whoops.

  • Showbot

  • Rapid DHCP: Or, how do Macs get on the network so fast?

  • Moving Back to BBEdit from TextMate

  • iAd isn’t dead.

  • ]]>
  • An Analysis Of Apple’s Adjustment Of International App Store Prices

  • Ready, Set, Whoops.

  • Showbot

  • Rapid DHCP: Or, how do Macs get on the network so fast?

  • Moving Back to BBEdit from TextMate

  • iAd isn’t dead.

  • ]]>
    0 877 An Analysis Of Apple’s Adjustment Of International App Store Prices Ready, Set, Whoops. Showbot Rapid DHCP: Or, how do Macs get on the network so fast? Moving Back to BBEdit from TextMate iAd isn’t dead. An Analysis Of Apple’s Adjustment Of International App Store Prices Ready, Set, Whoops. Showbot Rapid DHCP: Or, how do Macs get on the network so fast? Moving Back to BBEdit from TextMate iAd isn’t dead. iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.2 http://developingperspective.com/2011/07/14/10/ Thu, 14 Jul 2011 14:22:59 -0400 David http://developingperspective.com/?p=10
  • Details on Apple Rebalancing international App Store prices
  • Push Notifications, Push Notifications, Push Notifications!
  • How to use the Home Button
  • The Rise and Fall of the Independent Developer
  • Google’s patent problems
  • The Life
  • ]]>
  • Details on Apple Rebalancing international App Store prices
  • Push Notifications, Push Notifications, Push Notifications!
  • How to use the Home Button
  • The Rise and Fall of the Independent Developer
  • Google’s patent problems
  • The Life
  • ]]>
    0 855 Details on Apple Rebalancing international App Store prices Push Notifications, Push Notifications, Push Notifications! How to use the Home Button The Rise and Fall of the Independent Developer Google’s patent problems The Life Details on Apple Rebalancing international App Store prices Push Notifications, Push Notifications, Push Notifications! How to use the Home Button The Rise and Fall of the Independent Developer Google’s patent problems The Life iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no
    Show 0.1 http://developingperspective.com/2011/07/13/0-1/ Wed, 13 Jul 2011 17:34:39 -0400 David http://developingperspective.com/?p=5
  • Back to Work: #24
  • Tweetbot Tips and Tricks
  • A Tale of Three App Stores
  • ]]>
  • Back to Work: #24
  • Tweetbot Tips and Tricks
  • A Tale of Three App Stores
  • ]]>
    0 895 Back to Work: #24 Tweetbot Tips and Tricks A Tale of Three App Stores Back to Work: #24 Tweetbot Tips and Tricks A Tale of Three App Stores iOS, apple, mac, geek, development, programmer, cocoa, coffee David Smith no no