TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    Developing Perspective

    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.

    Advertise
    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    #187: Explorers Jun 13, 2014
    Show notes

    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!


    #186: Dropping Bombs Jun 02, 2014
    Show notes

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


    #185: Pick up your Kite. May 27, 2014
    Show notes

    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.


    #184: The Middle Path? May 16, 2014
    Show notes

    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?


    #183: Anxiety and Inertia May 02, 2014
    Show notes

    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.


    #182: Unconventional Wisdom, Listen to Spock. Apr 25, 2014
    Show notes

    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.


    #181: Unconventional wisdom, pricing. Apr 18, 2014
    Show notes

    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.


    #180: Enduring Features. Apr 11, 2014
    Show notes

    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.


    #179: Avoiding the Stampede. Apr 03, 2014
    Show notes

    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

    #178: Customer Escape Hatches Mar 27, 2014
    Show notes

    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.


    Previous 1 3 4 5 6 7 23 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights