Manton Reece
About Photos Archive 30 days 88 parks Replies Reading Search Also on Micro.blog
  • Discovery of this random app

    Curtis Herbert is back with another Slopes Diaries post, making the argument that Apple’s 30% cut is worth it, but that external payment links will also open new opportunities.

    I think the perspective on this topic varies between developers partly based on whether you expect users to randomly discover your app in the App Store, or whether you’re building a service outside the store and the mobile app is just a companion to that. Much of Curtis’s framing is around discovery in the App Store:

    Remember, your goal when trying to convert a sale is to try to cause as little friction as possible. Make the user think as little as possible. “Enter your credit card information for this random app to start your free trial” is hardly frictionless compared to IAPs.

    There are many advantages to Stripe other than the lower fees. There’s more control and flexibility across the board. Also you get paid daily instead of waiting over a month for Apple to cut a virtual check, as if developers are kids waiting for their monthly allowance.

    Apple’s in-app purchase works really well for Slopes. That’s great. For Micro.blog, I’m not convinced there’s much of an advantage. Very few people want to start a new blog and think, “First I’ll search the App Store.”

    Developers are in the best position to know what marketing and payment options will work for their app. The whole point of these changes — from the EU’s Digital Markets Act to the judge’s ruling in the Epic trial — is to put the decision back in the hands of developers where it belongs.

    → 9:54 AM, May 16
    Also on Bluesky
  • Huge new ruling by the judge in the Epic Games case. Hope to take advantage of this as soon as possible in Micro.blog to let people subscribe from the iOS app. Finally a clear voice of reason in the App Store.

    → 8:56 PM, Apr 30
    Also on Bluesky
  • Apple antagonism

    I wanted to see a transcript before blogging about it but this AP story probably has enough of Phil Schiller’s testimony on the App Store:

    “What happens if a developer doesn’t pay and what is the process for that?” Schiller recalled about his initial reservations about requiring fees on alternative payment options. He also said he was worried about Apple’s collection demands creating an antagonistic relationship with app developers that have traditionally been the company’s allies.

    Exactly. And:

    Schiller also confirmed that Cook pushed for a warning screen informing consumers the potential security threats posed by alternative payment options.

    We’ve been getting a clearer picture over the last year that the problem with the App Store is Tim Cook. He has led Apple to great success but it’s time for new leadership, someone users and developers can trust to be on our side. It may already be too late to repair the damage.

    → 8:47 PM, Feb 24
    Also on Bluesky
  • John Gruber on the implications for sideloading if TikTok remains unavailable in the App Store:

    If I’m wrong and TikTok remains in this half-zombie state in the US — unavailable in the App Store or Play Store, but operational if you have the app installed on your phone — it’ll be interesting if TikTok is the app that makes the mass market actually care about the lack of sideloading on iOS. It’ll be interesting too if sideloading on Android goes mainstream because of this.

    TikTok should make an iOS marketplace app in the EU to demonstrate to US customers what they’re missing.

    → 7:08 PM, Feb 8
    Also on Bluesky
  • Micro.blog iOS folks on the TestFlight beta, the latest build fixes an issue editing longer blog posts. If anyone sees any new problems, please let me know. We’ll do the App Store release this week.

    → 8:00 AM, Feb 2
    Also on Bluesky
  • In the context of Apple services revenue, I want to mention something I noticed yesterday. I opened the App Store to check something, and staring me in the face right on the home page was an ad for Truth Social. Between that and search ads clutter, ads only make the App Store worse. 💰

    → 7:04 AM, Jan 31
    Also on Bluesky
  • Skimming Steve Troughton-Smith’s thread and commentary on the EU’s requirements for Apple. Even though I’ve been frustrated by the App Store and calling for sideloading longer than most developers, I’m feeling burned out on the drama. Huge computing platforms need to be more open. We’ll get there.

    → 10:35 AM, Dec 19
    Also on Bluesky
  • Mammoth is shutting down:

    Sadly, we’re no longer able to reliably update Mammoth or operate moth.social at the level we want. Therefore we will be removing Mammoth from sale on the App Store. By the end of the January, we will also shut down Moth.social along with our other project, sub.club.

    When it launched a couple years ago, I thought they were on to a good idea: pairing a new Mastodon client with its own server to make signing up easy. They had some funding from Mozilla, and they pivoted to try Sub.club for monetization, but subscriber revenue is tough when most servers are free.

    → 11:30 AM, Dec 13
    Also on Bluesky
  • Going to restart the public beta for Micro.blog on iOS. Just waiting for Apple to approve the beta, because Micro.blog has only been around for 7 years with dozens of public releases, so we must be devious hackers trying to exploit the App Store. So tired of Apple as a babysitter.

    → 7:30 AM, Sep 24
    Also on Bluesky
  • Posted a new Core Intuition, this week covering the latest App Store news with new linking entitlement rules and in-app purchase in Patreon. We also talk about my upcoming Markdown text editor change in Micro.blog.

    → 8:20 AM, Aug 17
    Also on Bluesky
  • Good post from Jason Snell about Apple services:

    Apple is building an enormous business that’s based on Apple customers giving the company their credit cards and charging them regularly. And that business is incredibly profitable and is expected to continue growing at double-digit percentages.

    Another thing that struck me about Tim Cook’s comments on the earnings call: no mention that I noticed of App Store revenue. And yet that is a huge part of services. As a developer, it feels like Apple doesn’t want us to think about how profitable they are based on third-party apps.

    → 1:28 PM, Aug 2
  • More DMA, more rejections, more exhaustion

    Nick Heer on the latest DMA news and UTM rejection:

    Perhaps there are legitimate security concerns in the UTM emulator. The burden of proof for that claim rests on Apple, however, and its ability to be a reliable narrator is sometimes questionable. Consider the possible conflicts of interest in App Tracking Transparency rules raised by German competition authorities.

    Apple’s handling of the App Store is getting so old. It’s exhausting that there is always drama, always bad faith efforts, always two steps forward, one step back. Here’s what I blogged 13 years ago:

    Apple, want to charge 30%? Go for it. Want to make the submission rules more strict? Fine. Want to adjust how you run the App Store to reflect what’s happening in the market? No problem. Just give developers an out. We are going to be back here year after year with the latest controversy until exclusive app distribution is fixed.

    Maybe nothing I’ve written in 20 years of blogging has proven more true than that statement. Enough already! Just let us build apps that customers want and distribute them outside the store without gimmicks. That’s what the DMA is about and Apple knows it.

    → 7:29 AM, Jun 26
    Also on Bluesky
  • It’s bizarre to see developers effectively siding with Apple over the DMA. The EU is trying to make things better for developers. We can nitpick whether the DMA is well-written, too broad, etc. But there are specific sections that address real problems with the App Store that Apple won’t fix on their own.

    → 6:30 AM, Jun 24
  • European Commission preliminary findings that the App Store is in breach of the DMA. Even if there’s some compromise, this should lead to improved rules for developers. Still unresolved is whether the CTF is valid, and how much Apple is going to fight to keep it.

    → 6:23 AM, Jun 24
  • Working with the Threads API reminds me of how frustrating it was to work with Facebook’s main app API years ago, and any silo API that requires manual approval like the App Store. The bureaucracy is at odds with Meta’s claim of supporting the open web and fediverse.

    → 10:19 AM, Jun 20
    Also on Bluesky
  • On this day 16 years ago, Daniel and I released the first episode of Core Intuition. So many things have changed since then. Listening to episode 1 is like going back in a time machine, to weeks before WWDC, on the verge of the App Store launching, a snapshot of the Mac developer community. 🎂

    → 8:28 AM, May 29
  • AltStore PAL launches in the EU. Riley Testut blogs about the release, including what types of apps are the best fit for AltStore:

    All apps are welcome, but I believe AltStore makes the most sense for smaller, indie apps that otherwise couldn’t exist due to App Store rules. There are countless examples of these that aren’t allowed in the App Store for one reason or another; we just don’t know about them because there’s never been a distribution option for these poor apps.

    It’s €1.50/year to cover Apple’s Core Technology Fee. Still hoping the EU decides the CTF is illegal.

    → 10:22 AM, Apr 17
  • Great article from Ben Thompson today on the Apple antitrust case:

    …the Epic case may have shown that Apple’s policies around the App Store were (mostly) legal, but that didn’t mean they were right; now the DOJ, looking for another point of vulnerability, is trying to make the case that Apple’s right approach in delivering an integrated experience is in fact illegal.

    He ties things together really well, especially: while the case isn’t about the App Store, the frustrations with the App Store contributed to the environment in which legal action against Apple more broadly was necessary.

    → 8:41 AM, Mar 25
    Also on Bluesky
  • John Voorhees has a good section in his article about the Apple antitrust lawsuit and relevant market. I wish the case was more focused on the App Store, because from a dev perspective the market is really people who buy phones and apps. Apple dominates that.

    → 7:30 AM, Mar 25
    Also on Bluesky
  • Early thoughts on United States vs. Apple

    I’m reading through the lawsuit document intro and skimming the rest. I only have strong opinions about the App Store and developer aspects of the case. Some of the arguments in the case about messaging apps and watches seem more flimsy to me, but perhaps good things will come from the broader scope.

    Here’s a small section about the App Store:

    Rather than respond to competitive threats by offering lower smartphone prices to consumers or better monetization for developers, Apple would meet competitive threats by imposing a series of shapeshifting rules and restrictions in its App Store guidelines and developer agreements that would allow Apple to extract higher fees, thwart innovation, offer a less secure or degraded user experience, and throttle competitive alternatives.

    This is basically true. I don’t think Apple is obligated to make iPhones less expensive, of course, but switching costs away from iOS are significant, for developers and users, helping maintain the status quo. Competition across iOS and Android platforms is important, but competition just within iOS is important too. My complaints have always been about Apple’s exclusive control over app distribution, regardless of Android.

    An antitrust lawsuit is about size. The government isn’t suing game console makers even though they control game distribution (and charge too much to developers) because game consoles are not general-purpose computers, and they sell in a small fraction of the numbers that Apple sells smartphones. For many people, an iPhone is their best computer. The scale and impact to society is on a completely different level.

    Even though there is a smartphone duopoly with iOS and Android, iOS alone reaches so many hundreds of millions of people that it is effectively a market on its own. If you want to build and distribute for the most commercially viable smartphone platform, you have no choice but to follow Apple’s rules. Until Apple lets developers route around that monopoly through external payments and sideloading, there will be pushback.

    Apple leadership might still see the company as the upstart, but the rest of the world sees size and power. Apple should settle the lawsuit, accept App Store changes similar to those required by the Digital Markets Act, and move on. There is no winning this once the tide has turned against you.

    → 11:29 AM, Mar 21
    Also on Bluesky
  • Rollercoaster week for the App Store. Spotify ruling, Epic banned, EU getting involved, Epic now un-banned. Whew! We recorded a @coreint in the middle of it and we’re gonna try to add an update before it’s published.

    → 11:22 AM, Mar 8
    Also on Bluesky
  • I usually try to avoid quoting just the end of an essay (spoilers!) but the closing lines in today’s Stratechery update are great:

    …once upon a time — back when “There’s an app for that” was about developers’ contribution to the iPhone — Apple valued developers; today, when “There’s an app for that” is about Apple’s supposed sacrifice in building developer tools and SDKs, Apple resents them. A legal argument about IP monetization has become a righteous tenet, and Apple is defending said tenet with the fervor and blinders of the true believer.

    Apple has lost their way with the App Store.

    → 7:25 AM, Mar 7
    Also on Bluesky
  • Still love developing Mac apps. It’s such a nice feeling to know I can continue to work on little improvements and bug fixes right up until the moment of release, because I don’t use the App Store.

    → 8:43 AM, Feb 11
    Also on Bluesky
  • My first thought on hearing about the Epic and Disney partnership is that this is how Fortnite eventually gets back into the App Store. Apple is going to need games and content for the Vision Pro.

    → 8:52 PM, Feb 7
    Also on Bluesky
  • Apple has approved our new app and I’m sort of almost shocked, but happy. You never know! It’s a big relief to know that we can continue to plan for a new thing. Plenty of other things to work on before it’s enabled in the App Store, though.

    → 9:40 AM, Feb 7
    Also on Bluesky
  • Submitted a new 1.0 app to Apple! Requires a Micro.blog account, so who knows whether it will go through app review smoothly. A recurring conflict with the App Store: Apple wants an app that anyone can download and I just want to build something useful for my existing customers.

    → 6:03 PM, Feb 5
    Also on Bluesky
  • If Mark Zuckerberg says it’s very difficult to use the new App Store EU rules — and Meta just announced their quarterly results of $40 billion in revenue — then there is no chance the rest of us can make it work. Sideloading and marketplaces are like a mirage.

    → 8:42 PM, Feb 1
    Also on Bluesky
  • MacStories has also published their write-up on the App Store changes for the Digital Markets Act. The more I think through the system Apple is attempting, the more it becomes clear the Core Technology Fee is not compliant with the DMA. Marketplaces simply cannot work with the CTF in place.

    → 3:29 PM, Jan 28
    Also on Bluesky
  • With all the App Store EU changes, briefly considered that maybe my iPhone 14 Pro will be my last iPhone. It is a great phone, but I’m not currently inspired to drop $1k in Apple’s lap every couple years. Think I’ll keep it a while.

    → 11:56 AM, Jan 28
    Also on Bluesky
  • Fixing the App Store, part 2

    In a blog post from 2020, I suggested four changes to fix the App Store for developers: 1) allow sideloading; 2) don’t require in-app purchase; 3) keep curating the App Store; and 4) lower the cut to 15%. I described each of these in more detail in that post, so I won’t repeat the reasoning here.

    With this week’s App Store changes for the EU’s Digital Markets Act, let’s revisit how Apple is doing with those four points:

    • Allow sideloading? Not really. Instead, there is a new type of marketplace app that can install other apps. There are hurdles to jump through to become a marketplace app. For Micro.blog, I was imagining that I could have a marketplace app just for our suite of iOS apps, thus bypassing app review going forward, but this doesn’t seem like it is going to work in practice. Furthermore, there is a new Core Technology Fee that would still apply.
    • Don’t require in-app purchase? Sort of. If you opt-in to the new rules, you can use your own payment system, or link to external payments on the web. The problem is Apple still wants 10% (for small developers), so there is little to no savings, and it creates new bookkeeping problems. The only way to avoid the fee is to have an app on a third-party marketplace. Even then, you’re still subjected to the Core Technology Fee.
    • Keep curating the App Store? Yes. Isn’t very relevant here, though, and Apple is no closer to adopting my vision for how to run the App Store.
    • Lower the cut to 15%? Yes. It can be as low as 13% now. But again, there’s the Core Technology Fee to offset any savings if you have more than a million installs.

    This is all pretty disappointing. I have been bitter about the App Store for years, but yesterday I tried to keep an open mind. I was initially excited about the potential for marketplaces. I blogged that it seemed like a good-faith effort to comply with the DMA. Apple had put a bunch of work into this, in documentation and new APIs. The more I understood it, though, the less compelling it became. In some cases it will be worse than what we had before.

    My opinion from way back in 2011 hasn’t changed. The problem is Apple’s total control over app distribution, and so the only permanent fix for the App Store is removing that control with true sideloading:

    Apple, want to charge 30%? Go for it. Want to make the submission rules more strict? Fine. Want to adjust how you run the App Store to reflect what’s happening in the market? No problem. Just give developers an out. We are going to be back here year after year with the latest controversy until exclusive app distribution is fixed.

    I wrote that thirteen years ago and it has proven correct every single year since. The DMA attempted to address this, but Apple’s response comes up short. Instead of fixing the root problem, Apple has added an even more complex set of bandaids to preserve their control over the store.

    (As an aside, see that quote from Steve Jobs about free apps in my blog post? The Core Technology Fee is a major departure from Steve’s framing. Apple now wants to charge free apps for the first time based on installs alone.)

    So, is Apple actually in compliance with the DMA? Rick VanMeter, from the Coalition for App Fairness, says no. There’s also a thorough post by Damien Geradin on The Platform Law Blog that reaches the same conclusion:

    As to whether the reduced commissions comply with FRAND. The answer is an unequivocal no. These commissions are not fair and reasonable for the reasons described in the preceding paragraph. But they are also discriminatory. The reason is that app developers whose apps sell digital goods and services and those whose apps don’t, effectively use the same app store services, but are treated differently.

    I don’t know where we go from here. It always feels like two steps forward, then back. The EU must stand firm. I’m tired of ending up in the same place, over and over.

    → 11:02 AM, Jan 26
    Also on Bluesky
  • Follow-ups from @coreint yesterday about the DMA… We glossed over the Core Tech Fee. I have a better understanding of how the fees add up now, and where they apply. App Store + external payments: 10% (for small devs). Only way to avoid paying Apple: a marketplace and less than 1 million installs.

    → 9:26 AM, Jan 26
    Also on Bluesky
  • Core Intuition episode 584 is up now with our reaction to the just-announced App Store changes for the EU. Recorded shortly after all the news dropped today, so there’s a lot to unpack and follow up on.

    → 4:01 PM, Jan 25
    Also on Bluesky
  • Still sorting out Apple’s changes for the EU, coming in March. On first reading, it’s totally different (and better) than the external linking rules from just last week. Feel like I’m on a roller coaster.

    → 11:50 AM, Jan 25
    Also on Bluesky
  • The Wall Street Journal has an article today about Apple’s plans for sideloading in the EU:

    Apple’s approach to the EU law will help ensure the company maintains close oversight of apps downloaded outside the App Store, a process known as sideloading. The company will give itself the ability to review each app downloaded outside of its App Store. Apple also plans to collect fees from developers that offer downloads outside of the App Store, said people familiar with the company’s plans.

    No good. Reviewing apps distributed outside the store defeats the purpose of sideloading.

    → 9:02 AM, Jan 24
    Also on Bluesky
  • Apple can be frustrating with the App Store because they will have policies that are plainly wrong, morally if not legally, and still try to convince you that you’re the crazy one. Increasingly this is what I hear from Apple: “I’ll only be a dictator on day one.” Hubris + total control is dangerous.

    → 8:11 AM, Jan 18
    Also on Bluesky
  • Tim Sweeney reacts to Apple’s new linking rules (Twitter X):

    Epic will contest Apple’s bad-faith compliance plan in District Court.

    I’ve said before that for devs who want to see the App Store’s payment rules change, Epic was an imperfect champion, but they’re who we’ve got. Glad to see Tim keep pressing this.

    → 9:52 PM, Jan 16
    Also on Bluesky
  • My track record of blog posts that go a little against the grain (but which are later proven right) is pretty good. Early essays about Twitter and the App Store. But I’m wrong sometimes! I was wrong about AI. Ignored it for months, thinking it was a distraction. Maybe I’ll be wrong about Vision Pro.

    → 3:11 PM, Jan 16
    Also on Bluesky
  • Mark Gurman on Apple’s EU plans, although it’s not clear whether this is his speculation or actual plans:

    Apple will need to split the profit-generating App Store in two: a version for the EU and a version for everywhere else. Those living in the EU will get to install apps from outside the store, use outside payment processors to pay for services and get better integration between first- and third-party apps and features.

    Maybe time to relocate Micro.blog HQ to Europe.

    → 9:56 AM, Jan 16
    Also on Bluesky
  • Missed this Patreon blog post from last month on accounting for Apple’s 30% cut:

    Apple is requiring us to start using their in-app payment system in order for Patreon to remain available in the App Store, which means purchases made from our iOS app will be subject to Apple’s 30% App Store fee.

    The default setting will be that users on iOS will have to pay more than on the web to cover this fee. And last week we had the Hey Calendar rejection. Strange that Apple is tightening the screws with the EU’s Digital Markers Act waiting in the wings.

    → 9:57 AM, Jan 11
    Also on Bluesky
  • From a post-trial interview with Tim Sweeney, he reiterates why settlement talks with Google didn’t go anywhere:

    We were rather far apart, let’s say, because what Epic wants ultimately is free competition and fair competition for everybody, and the removal of the payments tie and removal of the anticompetitive measures, which obviously leads to far better deals for consumers and developers.

    Epic remains an imperfect messenger for App Store reform but they really do have this part right. It’s about the overall market for decades to come, not Epic or any other single company.

    → 8:31 AM, Dec 14
    Also on Bluesky
  • Apple’s sending emails about getting apps ready for the Vision Pro App Store. Folks in the Apple dev community won’t like this, but I think Vision Pro will be a bust in the short term. Only develop for it for fun, not for a market. I’ll revisit it in 10 years when the tech catches up to the dream.

    → 7:17 AM, Sep 7
    Also on Bluesky
  • Great article by Christina Warren on the history of the App Store and why we’re due for some kind of change, likely helped along by the EU’s Digital Markers Act. Apple taking a cut of all developer revenue is not sustainable forever.

    → 6:18 AM, Aug 9
    Also on Bluesky
  • Congrats @playdate@panic.com on the Catalog release! I’m updating my Playdate now. It’s the model that I still hope we’ll get for the iOS App Store one day: a curated store + side-loading for everything else.

    → 3:27 PM, Mar 7
  • New Micro.blog 3.0 beta going out to TestFlight folks now, adding username auto-complete. Still has a couple glitches but should be a nice improvement when you @-mention people. We are steadily working through re-implementing the features from 2.3 so we can ship 3.0 to the App Store.

    → 9:15 AM, Mar 7
  • John Gruber writing about the App Store / Twitter apps refund problem:

    Consider the gut punch of losing your job — you stop earning income. It’s brutal. Now imagine that the way it worked when you get fired or laid off is that you’re also suddenly on the hook to pay back the last, say, 6 months of your income. That’s where Tapbots and The Iconfactory are.

    → 10:52 AM, Mar 2
  • Pushed another update to the beta Micro.blog iOS app (TestFlight link). Still planning to ship early-ish next year, but I use it as my default now. If it’s missing anything you need, just re-install the official release from the App Store.

    → 7:15 AM, Dec 22
  • No question Elon has gone way beyond our worst predictions for Twitter, but his “decisions by tweet” have added to the narrative that the company is chaotic and off course. Imagine App Store policies the same but Tim Cook firing off random edicts about side-loading or linking.

    → 7:03 AM, Dec 19
  • On the latest Core Int, @danielpunkass and I talk about the App Store settlement and then follow up again about Twitter, Micro.blog, and Mastodon. Also: not being allowed to pump your own gas.

    → 2:53 PM, Dec 2
  • Epilogue 1.4 for iOS is now available on the App Store. Check out the blog post on the Epilogue microblog for screenshots of the new Goals tab.

    → 5:15 AM, Sep 1
  • New version of Epilogue! From @news:

    Epilogue 1.3 for iOS has been released in the App Store! This version adds a new Discover tab for finding books that people are blogging about. Tap and hold on a book cover to quickly add it to one of your bookshelves.

    → 9:43 AM, Aug 23
  • I wonder if the way Apple forces developers to agree to updated terms of service is actually legal. Agree to terms, ship app. Then later, we can’t even update our existing apps outside of the App Store (using Gatekeeper) until agreeing to the latest terms. Apps held hostage.

    → 8:41 AM, Jul 2
  • I didn’t exactly mean to ship Epilogue 1.1 yet, but… it’s out for iOS already! Check out the new version in the App Store. Epilogue is our companion app for books you’re reading. More updates soon.

    → 2:27 PM, Feb 17
  • Posted episode 501 of @coreint. We talk about Apple’s new App Store rules for the Netherlands, and @danielpunkass moving from Mercurial to Git.

    → 1:02 PM, Feb 13
  • Micro.blog 2.3 for iOS

    Micro.blog 2.3 is now available in the App Store, including these changes:

    • Added syntax highlighting for HTML when creating or editing posts.
    • Fixed compatibility with some Micropub servers.

    We’ve supported color highlighting in Markdown for a while, and now this release adds HTML too. I’ve found this most helpful when editing a blog post that includes images, where the img tag was probably added by Micro.blog:

    Micro.blog iOS screenshot

    I also fixed a bug with Micropub servers, no longer requiring the me parameter from some IndieAuth API calls. There has been some related housekeeping of the IndieAuth spec recently, and I want to make sure Micro.blog can post to as many non-Micro.blog servers as possible.

    → 7:16 AM, Feb 7
  • On the latest Core Intuition, we talk about the App Store and Apple’s response to government regulation, especially recent news from South Korea.

    → 5:39 PM, Jan 22
  • Apple's response to South Korea untenable

    I’m as tired of debating the App Store as anyone. I’ve been making essentially the same arguments for 10 years, on this blog and on the podcast. But the news from South Korea adds a new wrinkle that is worth highlighting.

    The spirit of any law forcing Apple to allow external payments for apps is clearly twofold: give developers more control over interacting with customers, and let developers avoid paying the 15% or 30% on transactions by handling payments outside the store. Apple and Google are trying to follow the letter of the law while missing the larger point completely:

    Apple said it plans to provide an alternative payment system at a reduced service charge compared with the current 30 percent charge, as the tech giant turned in its compliance plans to the Korea Communications Commission (KCC).

    Ignore for the moment whether this response is legal or fair. Let’s think through how this would work in practice. Apple is developing APIs so that when using an external payment, Apple is still notified about the external transaction so they can collect their “reduced” service charge.

    But iOS developers are used to paying Apple $99/year, and then getting a check from Apple once a month with 70% of the sales through the App Store. The 30% (or 15%) is taken out automatically, just like 3% is taken out for Stripe transactions. Developers don’t have to think about it.

    In this new world Apple imagines, developers will be collecting all of the sales into their own bank account, and then paying Apple the 11% or whatever Apple ends up demanding. There is a huge psychological difference between these approaches, just as there’s a difference between getting taxes taken out of your paycheck automatically and having to write a big check to the government.

    If this goes through, it will only underscore how ridiculous the App Store tax is. Why do developers have to pay Apple a platform fee when we’ve never had to do that for macOS? What is the point of the $99/year program?

    Apple wants iOS, the App Store, and their App Review team to be inseparable as a single platform. That’s not a technical reality. If they keep pushing this approach, they’ll only run up against more regulation and more distrust from the developer community.

    → 8:11 AM, Jan 19
  • After a whole bunch of App Store rejections — mostly confusion with using Micro.blog accounts and probably (though left unsaid) Apple wondering if they needed a cut of subscriptions — Epilogue for iOS is approved. I’ve updated the Epilogue blog with a link in the latest post.

    → 6:43 PM, Nov 17
  • Going through a series of App Store rejections. I think the biggest disconnect between Apple and indie developers is that Apple thinks everyone will discover apps for the first time in the App Store. I’m happy if most users discover the apps through blog posts and web searches.

    → 7:36 AM, Nov 9
  • Sunlit 3.4.1 is now available in the App Store! This update adds sharing from the Glass iOS app and fixes several timeline problems, including crashes and refresh issues.

    → 7:42 AM, Oct 20
  • Sunlit 3.4

    Sunlit 3.4 is now available in the App Store. For this update, we focused on improving the timeline experience, cleaning it up so that it better focuses on photos and viewing conversations. There are a bunch of little changes that together make the app feel much more responsive and easier to use:

    • Streamlined the timeline user experience, with single tap to view conversations and moved some buttons to secondary screens.
    • Improved performance and added placeholder blurred backgrounds while photos load.
    • Fixed bugs, updated toolbar with translucency, and other design tweaks.

    The blurred photo placeholders are done with BlurHash. Whenever you post a photo, Micro.blog calculates the BlurHash for it and includes that value in the /posts/media JSON Feed so apps like Sunlit can use it.

    Remember that the Micro.blog iOS app also supports sharing photos from Glass, and those photos will show up in Sunlit. I’ve been using Glass in addition to posting to my own blog for my murals photoblog series this month, and some of these improvements in Sunlit 3.4 are partially inspired by the UI polish in Glass. This is the best version of Sunlit yet.

    → 7:05 AM, Sep 13
  • Enjoyed talking with @danielpunkass about the latest App Store controversies on Core Int. Here’s a clip near the end of the show where Daniel digs up an old blog post of mine predicting the never-ending approval problems as long as Apple completely controls app distribution.

    → 8:36 AM, Sep 4
  • Just posted Core Int 478: MarsEdit 4.5 and all the latest App Store settlement news.

    → 8:18 PM, Sep 3
  • We’ve updated our Instagram-like photoblogging app Sunlit with a couple bug fixes. If you ever had any slow photo uploads or timeouts, I think we finally solved that! Grab it on the App Store.

    → 8:38 AM, Aug 6
  • First new blog post from @marco in a while is a great one:

    It isn’t the App Store that has enabled all of the commerce on iOS — it’s the entire world of computing and modern society, created by a symbiotic ecosystem in which Apple played one part alongside many others.

    → 5:44 AM, Jun 4
  • Enjoyed this write-up at The Verge of Phil Schiller’s testimony:

    presenting one of the most ruthlessly efficient cash machines in tech as a helpful friend of small developers is kind of like painting a whale shark orange and calling it a goldfish who feeds other goldfish

    → 10:04 AM, May 18
  • Wavelength 1.1 and podcasting trial

    We updated our iOS companion app Wavelength today. The new version adds Dark Mode support, now uses the system font, and takes care of some other housekeeping after going so long without an update.

    We are also open-sourcing the app! It is available here on GitHub. Just like our other app Sunlit, this was developed with Jon Hays and as we wanted to open source more pieces of Micro.blog, Wavelength felt like a perfect next step.

    To celebrate the launch of version 1.1, we’re enabling podcast hosting for all paid Micro.blog accounts for the next 2 weeks. You can publish a podcast episode to your blog via Wavelength, or upload an MP3 directly on the web. We take care of generating a podcast feed and all the other details. If you want to continue with podcast hosting after that, it’s included in Micro.blog Premium for $10/month.

    Download Wavelength from the App Store, or learn more in the Help Center.

    → 8:22 AM, May 10
  • I used to blog a lot about the App Store, and it often felt like I was one of only a handful of people who were on the same page about the 30% and exclusive distribution. Now that opinion is effectively mainstream. No need to blog much about it because it is well-covered.

    → 12:55 PM, May 3
  • So Apple will take 30% of subscription audio revenue. Not great, but unlike the App Store, podcasts are open and we can still publish podcasts wherever we want without Apple’s approval.

    → 12:09 PM, Apr 20
  • 15%… 30%… 5%? @danielpunkass and I talk everything App Store fees and why it’s inevitably going to simplify in developers’ favor, on the latest Core Intuition.

    → 5:32 PM, Mar 18
  • Just posted another episode of Core Intuition, talking with @danielpunkass about his return to full-time Red Sweater indie life, freemium business models, and the potential for the Arizona bill about the App Store.

    → 1:31 PM, Mar 5
  • We posted a new episode of Core Intuition over the weekend, talking about Apple’s new Small Business program, the App Store, and M1-based Macs.

    → 9:18 AM, Nov 23
  • Great article from RevenueCat that sheds light on how subscriptions are working for the App Store. 13% churn is not good. If apps use subscriptions when it’s a bad fit, that contributes to subscription fatigue and will hurt apps that do need subscriptions.

    → 6:19 AM, Oct 30
  • Sunlit 3.0.2 is now available in the App Store with a bunch of fixes. Because it’s open source, we’re also starting to get some contributions from other folks! Very cool to see that happen.

    → 7:18 AM, Sep 15
  • Puzzled about last week’s App Store guideline tweaks. By bundling so many changes in one update, most people are talking about the video game guidelines and not the (slight) loosening of in-app purchase rules. So it hardly did anything to fix Apple’s reputation with developers.

    → 8:43 AM, Sep 14
  • Almost switched to Android

    With my iPhone X glass broken, I needed a replacement phone quickly. The timing is not great because Apple has an event tomorrow, likely for the iPad and Apple Watch, with an announcement for new iPhones to follow within a few weeks. On the other hand, it has been nearly 3 years since I bought my iPhone X, so I don’t feel bad upgrading even to last year’s iPhone.

    Meanwhile, there’s Android. As Daniel and I have been discussing on Core Intuition, I’ve been increasingly frustrated with how Apple manages the App Store. It would be good for me to have more experience with Android, eventually developing an Android version of Micro.blog.

    Last year I bought a cheap Android tablet (Galaxy Tab A) to use for testing. I’ve been using it much more often, and it has become my “catching up on email, surfing the web, and Slack-ing while in the living room” device. The hardware is slow, but it runs Android 10, and already it has been useful for seeing how Android users experience Micro.blog.

    iMessage lock-in remains the biggest problem with Android for me. I tried AirMessage, which Ben Thompson had good things to say about on Dithering. AirMessage runs on your Mac and essentially forwards messages back and forth to Android. It’s clever, but because I use a MacBook Pro exclusively, AirMessage will stop working if I close the laptop or take it somewhere else.

    One option I seriously considered is getting a Pixel 4a and using an old iPhone (or ordering a new iPod Touch) just to run iMessage, Micro.blog, and anything else that I needed iOS for. It doesn’t make sense to go all-in on Android while I’m in the middle of wrapping up a major iOS upgrade to Micro.blog 2.0. Having 2 inexpensive devices would force me to live in the Android world while also keeping iMessage and everyday testing for Micro.blog 2.0. It looked like I couldn’t get a Pixel 4a shipped very quickly, though.

    In the end, I’ve decided to upgrade to the iPhone 11 Pro. It arrives tomorrow. It’s the 3rd version of the iPhone X-style phone, so I know it’s a stable, better version of what I already have. I don’t know what the iPhone 12 is going to look like, whether the quality will be rushed because of COVID, or what features they’ll stick in that I don’t need. I’ll continue to tinker with Android, and maybe that will be my next phone, but it felt a little too early for such a disruptive change.

    → 7:05 AM, Sep 14
  • Sunlit 3.0 for iOS is now available in the App Store! It’s built on the foundation of Micro.blog, but just for photos, and it can also publish to WordPress or IndieWeb blogs. Kind of like Instagram except no ads, no algorithms, and no Facebook.

    → 1:33 PM, Sep 1
  • Countdown to Sunlit 3.0: Tumblr blogs

    Sunlit 3.0 will ship tomorrow. For the last post in this blog post series to highlight Sunlit features, I want to mention a convenient way to follow Tumblr photoblogs.

    Micro.blog is based on blogs and IndieWeb standards so that it can integrate well with the rest of the web, not be walled off like a silo. One aspect of this is that you can follow many blogs in Micro.blog even if the author of the blog hasn’t registered on Micro.blog yet, similar to how you can subscribe to blogs in a feed reader like NetNewsWire or Feedbin.

    For Sunlit, there’s special support for searching for Tumblr blogs so that they are easy to follow directly from within Sunlit. Use the search under the Discover tab to enter the domain name to follow, as shown in this series of screenshots:

    Search screenshot   Tumblr result   Tumblr profile

    There is expanded support for following other blogs and even Mastodon users in Micro.blog itself. You can always use Micro.blog to find a blog to follow, then go back to Sunlit and those posts will appear in the Sunlit timeline.

    Tomorrow we’ll update the App Store for the Sunlit 3.0 release. I hope you like it!

    → 9:44 AM, Aug 31
  • Yesterday on Timetable, I was worried about App Store rejections. On today’s episode, I talk about starting to make tentative plans for the Sunlit 3.0 release.

    → 9:03 AM, Aug 27
  • I recorded a new episode of Timetable today, talking about submitting Sunlit 3.0 to the App Store and the new uncertainty around Apple reviewing apps. It’s about 4 minutes long.

    → 10:59 AM, Aug 26
  • Today’s article on Stratechery is excellent, providing a unique framework for fixing the App Store for developers. While I want even more significant changes, if Apple adopted Ben’s proposal it would be a big improvement and help rebuild developer trust.

    → 8:23 AM, Aug 25
  • Jason Fried on TWiST about Hey vs. Apple

    I was listening to Jason Fried on This Week in Startups today while out taking a walk, and Jason said something so extraordinary it kind of stopped me in my tracks. On the Hey vs. Apple controversy:

    If the Apple decision would have gone the other way, I was considered quitting, and basically retiring. […] Here’s why: I didn’t get into business — I didn’t start a business — to be told what to do by another business. […] We’re self-funded. We do everything our own way so that we can do it our own way. And to be in an industry where if Apple forced us to have to give them 30% of our business and not be able to interface with our customers the way we want, I don’t want to be in that industry.

    The segment starts about 60 minutes in. Here’s an Overcast link to the spot in the podcast.

    Even more than the latest case with Epic Games, or WordPress iOS rejected for weeks, that quote from Jason highlights what this is all about. Apple’s total control over iPhone app distribution and payment is preventing developers from doing their best work. The App Store started with good intentions, to help users, but the rules have become twisted, corrupted as Apple gains power. It’s not right.

    → 8:34 PM, Aug 22
  • On this week’s Core Intuition, @danielpunkass and I talk all about Epic Games and the App Store.

    → 2:05 PM, Aug 14
  • This was one of the best WWDC keynotes in years. Start of ARM transition looks great, running iOS apps on macOS is going to be wild, and I think I’m going to like where they’re going with the Big Sur design. (But don’t think I’ve forgotten last week’s App Store review problems.)

    → 12:35 PM, Jun 22
  • Fixing the App Store for developers

    It’s WWDC opening day. I wasn’t planning on writing about the App Store again, because I feel like I’ve said it all before, but maybe I haven’t put it together in one place, or in a concise enough format.

    Because I’ve dedicated the last several years to working on Micro.blog and writing about the open web, I think about the problems with massive social networks all the time. I’m obsessed with it. The App Store is also a huge platform with far too much power, so fixing it is not all that different than figuring out what to do with Facebook.

    Here are the 4 things Apple should do:

    • Allow side-loading. Essentially like Gatekeeper on macOS, but for iOS instead, this can still allow Apple to disable malware while letting developers skip app review. As I wrote in 2011, there will always be another controversy until side-loading is allowed.
    • Don’t require in-app purchase. Exclusive payment mirrors the problem of exclusive distribution, so both have a similar solution. Let developers charge customers outside the App Store. Apple should compete on payment user experience, not with force.
    • Keep curating the App Store. Apple is on the right track with highlighting great apps in the store. The point of my post about open gardens is that by loosening their tight control over distribution, Apple would actually be more free to curate, even rejecting apps because there would be an alternative with side-loading.
    • Lower the cut to 15%. For all paid downloads, all subscriptions, and for all companies. This is the least significant part of anything in this blog post, because as Jason Fried writes, choice is more important than money. But it would go a long way to rebuilding trust with developers.

    Anything short of all this is a band-aid, not a permanent fix.

    → 6:11 AM, Jun 22
  • When did we all just accept that of course Apple’s services revenue needs to keep growing? No company deserves success automatically. Whether the App Store is very profitable or just a little profitable is not my problem.

    → 12:50 PM, Jun 21
  • Daniel and I recorded a new Core Intuition today all about the App Store, Hey rejection, and thoughts leading up to WWDC next week. This issue is not going to go away until Apple loosens their grip over distribution and payment.

    → 4:23 PM, Jun 18
  • Apple's statement about EU antitrust

    I have long argued for fixing the 2 most fundamental problems with the App Store: exclusive distribution and exclusive payment. With Apple’s monopoly on iOS app distribution, we should have more options such as side-loading, reduced payment fees, and flexibility to sell subscriptions outside the store without hiding external links from potential users.

    See my blog posts from 2011, 2016, 2018, 2019, and my broader essay on open gardens.

    Now the EU is investigating Apple. Apple’s response:

    It’s disappointing the European Commission is advancing baseless complaints from a handful of companies who simply want a free ride, and don’t want to play by the same rules as everyone else… We don’t think that’s right — we want to maintain a level playing field where anyone with determination and a great idea can succeed.

    This is the worst, most insulting statement from Apple that I’ve ever seen. Everything in it is backwards.

    → 11:09 AM, Jun 16
  • Micro.blog 1.8.3 for iOS

    Just a quick update for the iOS version of Micro.blog. From the release notes:

    • Fixed username search.
    • Fixed opening links to account-related screens in posts.
    • Fixed navigation bar glitch when dragging conversations on some iPads.
    • Updated full-screen photo viewer to not hide status bar.

    You can download it in the App Store.

    → 4:17 PM, May 21
  • If you’re using iA Writer, check out version 5.5.1 now in the App Store. They’ve improved Micro.blog sign-in, plus other fixes.

    → 9:29 AM, May 21
  • We’ve updated Sunlit in the App Store today with several bug fixes. Sunlit is our iOS app that is just for photos, kind of like Instagram but powered by Micro.blog.

    → 7:15 AM, Mar 31
  • Micro.blog 1.7.3 for iOS

    We’ve shipped version 1.7.3 of Micro.blog for iOS. From the release notes:

    • Fixed issues and improved colors in Dark Mode.
    • Fixed crashes when sharing some photos to Micro.blog from other apps.
    • Fixed blurry thumbnails when selecting or filtering a photo.

    There were several Dark Mode-related glitches fixes in this update. Dragging to view a conversation looks better, navigation bar colors update when switching to Dark Mode without restarting the app, and we’ve switched the timeline background color to use full black instead of very dark gray.

    You can grab the latest version in the App Store. And if the official Micro.blog app isn’t your cup of tea, remember that there are other great third-party iOS apps including Gluon, Icro, and specialized tools like the new Mimi Uploader.

    → 6:18 AM, Mar 16
  • It has been months since I’ve submitted an update to the App Store. I still find the review delay infuriating, even if it’s just 1-2 days.

    → 6:49 AM, Mar 10
  • I could blog about the App Store vaping app controversy but I’ve said it already in my essay on open gardens.

    → 10:58 AM, Nov 19
  • Micro.blog 1.7.2 for iOS is now available in the App Store. Just a few more bug fixes and minor improvements.

    → 5:39 PM, Nov 2
  • Last week’s Core Intuition covered the Microsoft Surface event, App Store Search Ads, fixing old bugs, and responding to support emails. I’m making a renewed effort to at least not let my support email backlog get worse.

    → 8:24 AM, Oct 7
  • Micro.blog is doing much better in App Store searches now, possibly because I updated the keywords with this release. Went from around 60th place for “blogging” to 15th today.

    → 1:21 PM, Sep 19
  • This story about App Store search from The New York Times is really well done. It makes me wonder about Micro.blog search ranking and whether we should work to improve it (or run ads).

    → 12:00 PM, Sep 9
  • While a lot of people were traveling to San Jose last Sunday, I published a blog post about walled gardens, the App Store, Twitter, and the role of curation in social networks. This was primarily written 2 years ago and is adapted from a section of my book.

    → 7:55 AM, Jun 7
  • Open gardens

    In technology, the walled garden is a platform where one vendor controls distribution. If you want to make an iPhone app, your only choice is for Apple to approve it and sell it in the App Store. If you want to send a tweet, your only choice is to register on Twitter’s platform.

    Walled gardens like the App Store are user-friendly and developer-hostile. They take power away from independent publishers and put it in the hands of gatekeepers. The problem is exclusivity: there is only one gate, and those stuck outside are unable to distribute the same content. You can make Android apps, but not iPhone apps. Nothing exists outside the walls that closely resembles what is inside.

    Twitter is also a walled garden. Like the App Store, it is a closed platform with proprietary formats and a limited API. The difference is that Twitter’s garden is poorly curated and full of weeds. The walls are in such disrepair it’s hard to even tell where they are.

    Mike Monteiro emphasized this frustration in a post about the problems facing Twitter’s leaders. He talked about meeting in person with Jack Dorsey:

    We discussed Twitter’s role in the world stage. And I admired his vision, but feared his approach. Jack, and to an extent Twitter’s pet porg Biz Stone, have always believed that absolute free speech is the answer. They’re blind to the voices silenced by hate and intimidation. The voices that need to be protected. But anyone who’s ever tended a garden knows that for the good stuff to grow, you have to deal with the bad stuff. You can’t let the weeds choke the vegetables.

    The issue isn’t that Twitter doesn’t care. It’s instead a design flaw in the platform. Because tweets don’t exist outside of Twitter, when you’re banned from Twitter, you need to start over with a new format or on a new social network. For this reason, and because their business depends on a large user base, Twitter is hesitant to throw anyone off their service. They’re unwilling to tend the garden for fear of pulling too many weeds.

    It doesn’t matter who is guarding the walled garden’s gate if increasingly no one wants to go inside. So there’s a better word than “gatekeeper” to describe what we’re really after in building a great community-focused platform. It’s “curator”. Someone who is responsible for maintaining the best experience for users.

    The answer to a walled garden is not to create a platform without rules. It’s not outsourcing decisions to algorithms, with recommended users and topics that can be gamed or lead new users astray. That’s not enough for the challenges brought to us by massive, ad-based social networks, where fake news and hate can spread quickly.

    We need a new approach. Not controlled only by algorithms, but also not a walled garden that limits distribution of content. We need a system that prioritizes curation while preserving the freedom to publish outside of silos, with APIs based on the IndieWeb that are open by default instead of locked down with developer registration.

    I think of this as an open garden. It’s an open platform that also cares deeply about maintaining a healthy environment. Outside of the garden, the soil is the same and the same plants can grow, and you are free to copy flowers and trees from inside the garden and cultivate them yourself or let them grow wild. But inside is well-curated. Inside strives to be a high quality, safe environment.

    In my Kickstarter video for Micro.blog, I talked about this for social networking and blogs:

    If we start to separate the publishing from the social network, it unlocks something. It empowers writers to feel like they own their work, even if that’s short posts. And it frees social networks to build a safe community, without worrying about censorship, because no matter what the networks do you can always post to a site with your name on it.

    The fundamental problem in walled gardens like the App Store and Twitter is that they are closed. If they open up, they could in fact double-down on curation. There would be no need to loosen their quality standards because there’s an easy path to publishing without review by using the open web.

    I first wrote about this in 2014 in the context of learning from Beats Music. For Apple to deemphasize their algorithmic top 200 lists in the App Store they would need to focus on curation. Here’s what Beats was doing:

    Instead, they have a bunch of people — musicians and writers who deeply care about music — curating playlists. The top 25 playlists in a genre are so buried in the app that I had to search them out just to write this blog post, because they seem to carry no more weight than any other playlist. Much more common are playlists like “our top 20 of 2013”. That’s not a best-selling list; it’s based on real people’s favorites.

    After Apple acquired Beats Music, they brought some of those curation lessons over to Apple Music, and later redesigned the App Store with more featured apps and stories. There is only so much they can do, because the foundation of a walled garden is difficult to change.

    Twitter has likewise created an environment that ties their hands on curation, with discovery driven by trending hashtags and retweets. And for each rare time a popular account is banned for hate speech, there are still thousands of trolls who are making life miserable for users. Because there is no alternative, Twitter must allow nearly all content on their service. Because it exists apart from the open web, Twitter must give its worst users too much leeway before banning their account.

    The open garden solves this problem. It’s the same web inside a platform like Micro.blog as on the rest of the internet. By adopting open standards but also drawing a line across which we can apply community rules, it’s possible to build features that protect users.

    By encouraging the use of personal domain names, when Micro.blog does need to ask a member of the community to leave for violating our guidelines, that blogger can take their domain name and content with them, continuing to post to their own blog but blocked from interfering with the community. The curators of the platform have more freedom to block harassing posts because those problematic users can retreat to their own web site and leave everyone else in the community alone.

    To summarize:

    • Open gardens have curators instead of gatekeepers.
    • Open gardens use standards so that the same formats exist inside and outside the platform.

    This is only possible by embracing the open web. I believe it’s an important part of the way forward for all great platforms.

    → 3:48 PM, Jun 2
  • Mac Open Web is a new site by Brian Warren to showcase apps that promote the open web. As Brent says: “This is a page that would never appear as a category on the App Store — and yet it’s an important category.”

    → 2:02 PM, May 21
  • Sunlit 2.5.3 has been approved and should be available in the App Store now or soon. This update improves video posting and fixes an issue setting alt text for photos.

    → 8:29 AM, Apr 24
  • MacStories 10-year anniversary and pre-quadrant Twitter

    Congrats to Federico Viticci and the MacStories team on 10 years of MacStories. To appreciate how long ago this was, I re-read Federico’s interview with me from 7 years ago. This was 3 years after his first post but the content feels like a lifetime ago.

    I really like this interview because I think it captures that time on the App Store and as a Twitter developer. We talked about iOS 5 user interface design, my early indie apps before starting Micro.blog, but also a few things that are still relevant today, like using the iPad for real work and app pricing.

    Most importantly, it was a few months before Twitter’s infamous 4-quadrant chart that would set in motion Twitter’s move away from third-party developers. My priorities changed significantly after that, eventually leading to Micro.blog.

    → 9:01 AM, Apr 17
  • Sunlit with video playback

    Sunlit 2.5.1 is now available in the App Store. This update fixes an issue with videos not appearing in the timeline after the major new version we released yesterday to add video upload to the app and Micro.blog hosting.

    Here are a couple screenshots of the update with the video preview and new full-screen player:

    Sunlit screenshots
    → 11:44 AM, Apr 6
  • Sunlit 2.4 now available

    The new version of Sunlit is now available in the App Store. You can download it for free and use it with Micro.blog or to publish photos to an existing blog like WordPress.

    Why does controlling our own photos matter? As I wrote in this post about the way out of the mess created by massive social networks, having posts at our own domain names unlocks a few very important features:

    • Open standards mean interoperability with multiple tools. I can use IndieWeb tools like OwnYourGram to automatically copy Instagram posts to Micro.blog, or use traditional blogging apps like MarsEdit to upload and post photos.
    • Content ownership gives the flexibility to move photos between hosting providers. You can host on Micro.blog or WordPress or some future blogging platform without URLs breaking.
    • Smaller social networks get us away from ad-based businesses that sell our data. Because Sunlit is powered by Micro.blog, you can even follow Mastodon or PixelFed users and see their photos in the Sunlit timeline.

    I’m very excited about this release and hope you like it. It’s time to move away Instagram. If you need help importing your photos, check out this video I made about batch importing from Instagram to Micro.blog-hosted blogs.

    → 8:24 AM, Mar 20
  • My response to Apple's response to Spotify

    Apple responds to Spotify. Daniel Jalkut and I predicted most of this response on Core Intuition a couple days ago. I’m going to quote a few parts of Apple’s response and comment.

    Eleven years ago, the App Store brought that same passion for creativity to mobile apps. In the decade since, the App Store has helped create many millions of jobs, generated more than $120 billion for developers and created new industries through businesses started and grown entirely in the App Store ecosystem.

    Apple likes to brag about how much money they’ve paid to developers, but they leave out how much they’ve kept for themselves: about $50 billion. To Apple, they are doing us a big favor by letting us ship iOS apps.

    We’ve approved and distributed nearly 200 app updates on Spotify’s behalf, resulting in over 300 million downloaded copies of the Spotify app. The only time we have requested adjustments is when Spotify has tried to sidestep the same rules that every other app follows.

    It’s very important to remember that Apple’s rules are not laws. Apple’s rules have changed over the years, and especially around in-app purchase it often feels that they are applied inconsistently. Because Apple runs the platform, they can make any guidelines they wish, but there isn’t necessarily any inherent legal or moral justification in specific rules. We shouldn’t accept that all of Apple’s rules are fixed and cannot be improved.

    When you get to the scale of the App Store, there are also new monopoly and anti-trust questions. For more about this, see Ben Thompson’s article on Stratechery.

    Back to Apple:

    A full 84 percent of the apps in the App Store pay nothing to Apple when you download or use the app. That’s not discrimination, as Spotify claims; it’s by design.

    In 2011 I wrote a blog post with the premise that Apple made a mistake with how they handle free apps in the App Store, and what followed was years trying to make up for that mistake because of the burden of running the App Store. I think there was some truth to that, but now the business is very different. The App Store is a huge money-maker.

    And we built a secure payment system — no small undertaking — which allows users to have faith in in-app transactions. Spotify is asking to keep all those benefits while also retaining 100 percent of the revenue.

    And yet in the previous quote, Apple says that 84% of apps pay nothing and they are fine with that. Uber pays nothing to Apple. Games with ads pay nothing to Apple. Why is it wrong for Spotify to also want to limit how much they pay to Apple? The line Apple has drawn around in-app purchase is arbitrary. They could just have easily restricted Uber accepting payments, or banned third-party ads.

    Just this week, Spotify sued music creators after a decision by the US Copyright Royalty Board required Spotify to increase its royalty payments. This isn’t just wrong, it represents a real, meaningful and damaging step backwards for the music industry.

    This is irrelevant to Spotify’s complaints about the App Store. While I think Spotify’s argument would have been stronger if they had focused on a couple of their core complaints instead of mixing in issues such as Apple Watch development, Spotify didn’t bring up other concerns about Apple’s business that do not relate to the App Store. Apple trying to interject Spotify’s relationship with musicians is whataboutism.

    Overall, Apple’s response isn’t very convincing to me. There are still 2 fundamental problems with the App Store: exclusive distribution and exclusive payment. In that post from 8 years ago, I concluded with:

    Apple, want to charge 30%? Go for it. Want to make the submission rules more strict? Fine. Want to adjust how you run the App Store to reflect what’s happening in the market? No problem. Just give developers an out. We are going to be back here year after year with the latest controversy until exclusive app distribution is fixed.

    I think I’ve been proven right about this. This issue will never go away until Apple allows side-loading or makes it easier to let customers pay outside the App Store. In the meantime, I’ve been arguing for a 15% cut instead of 30% for all paid downloads and in-app purchase, which would go a long way to making this easier for developers.

    → 6:52 AM, Mar 15
  • Today’s Core Intuition is up, with more about Daniel’s new job and our thoughts on Spotify’s “Time to Play Fair” campaign against how Apple runs the App Store.

    → 8:14 PM, Mar 13
  • Brent Simmons has a good list of Marzipan questions. The one I’m slightly worried about is whether we can ship Marzipan apps outside the App Store. Other limitations will improve with time, but closing off distribution is a deal-breaker for me.

    → 8:33 PM, Mar 7
  • Sunlit 2.3.1 is now available in the App Store. If you’re interested in posting more photos to your own blog, check it out. It’s a free app and works well with Micro.blog.

    → 1:03 PM, Nov 29
  • There’s a nice feature on RSS apps (best viewed on iOS) in the App Store today.

    → 11:59 AM, Nov 29
  • There’s a really good follow-up about the App Store monopoly in today’s Stratechery daily update. Focusing on in-app purchase (digital goods) paints a very clear picture of why Apple’s rules need to change.

    → 9:31 AM, Nov 28
  • App Store rent-seeking

    Excellent article today from Ben Thompson. After laying out in detail why Apple has a strong argument in yesterday’s Supreme Court hearing, Ben moves to the larger question of the App Store monopoly:

    To put it another way, Apple profits handsomely from having a monopoly on iOS: if you want the Apple software experience, you have no choice but to buy Apple hardware. That is perfectly legitimate. The company, though, is leveraging that monopoly into an adjacent market — the digital content market — and rent-seeking. Apple does nothing to increase the value of Netlix shows or Spotify music or Amazon books or any number of digital services from any number of app providers; they simply skim off 30% because they can.

    I’ve been saying for years that the 30% cut is completely out of line with the value that Apple provides to developers. Developers should be calling for a more fair 15% rate across the board for all apps, and more flexibility to sell subscriptions outside the App Store. As I wrote earlier this summer, it shouldn’t sit well with developers when Apple talks about billions in services revenue, at our expense.

    → 8:58 AM, Nov 27
  • We just posted the first Core Intuition episode in a while. @danielpunkass and I talk about the Sunlit 2.2 release, the App Store, Android development, and iPhone XS leaks.

    → 10:33 AM, Sep 7
  • Sunlit 2.2.2 was approved and should be showing up in the App Store shortly. I like this version number so much that this will be the last release of Sunlit. (Kidding! We have a bunch of improvements we want to make.)

    → 4:10 PM, Sep 4
  • Sunlit 2.2 is here

    This week we shipped the new version of Sunlit, featuring an Instagram-like timeline of photos from people you’re following on Micro.blog. You can post photos to a microblog on Micro.blog, or to WordPress and other compatible blogs.

    The best way to understand Sunlit is to see it. I’ve prepared a short video below, talking through a few of the main screens, but the app has a lot more depth for editing photos and organizing photos into stories:

    Sunlit is a free download in the App Store. There’s no in-app purchase. If you like it, I hope you’ll support Micro.blog with a subscription to a hosted microblog or new photo blog. You can learn more at sunlit.io.

    → 9:17 AM, Sep 4
  • I know I complain about the App Store a lot, but the release process is really limiting and unpredictable. We’re juggling Sunlit 2.2 and a 2.2.1 update. Hope everything will be live on Tuesday. (Also shipping some M.b updates at the same time.)

    → 3:30 PM, Sep 2
  • The latest Core Intuition is out now, with @danielpunkass and I talking about the App Store, tracking sales, payment links for podcasts, and a wrap-up about Twitter.

    → 12:40 PM, Aug 20
  • We just posted Core Intuition 339: Apple services revenue, the App Store’s 30% cut, @danielpunkass getting back into iOS development, blogging features, and more.

    → 7:48 AM, Aug 3
  • Apple services and the App Store tax

    Jason Snell posted about Apple’s record services revenue:

    As someone who’s interested in products, I find the focus on Services revenue to be a bit dispiriting. I get excited at the prospect of new products and seeing how consumers are accepting or rejecting products in the market. But the discussion of Services, especially in a financial context, is essentially a conversation about how Apple can grind more money out of every single person who uses an iPhone, iPad, and Mac.

    Back in 2011 I explored the App Store’s 30% cut from the perspective of supporting free app downloads:

    I’ve argued that Apple’s 30% tax is about growing that to significant profit at the expense of developers, but in the back of my head I’ve also been concerned that maybe it’s just to keep the App Store from falling into the red. Maybe they are really struggling under the weight of what they created, and long app review times and lack of focus around the Mac App Store launch are just symptoms of that.

    In hindsight, 7 years later with $9.5 billion in services revenue per quarter, my attempt in that post to reconcile Apple’s cut seems like a stretch. To echo what Jason says above, I still believe that services should complement Apple’s core products.

    iCloud storage is there to make the experience of saving files or backing up your iPhone better, not to nickel-and-dime users who need more storage for a backup. The App Store is there to make discovering apps easier, not to turn developers into a profit center. The more these parts of Apple’s business dominate their revenue, the more divorced their product planning becomes from what users and developers need.

    $9.5 billion. As I’m posting this their stock price just pushed the company to $1 trillion in market cap. Many developers can’t make enough to support even a 1-person indie business full time.

    As an exclamation point on the discussion around services revenue, Apple has also cancelled their affiliate program. Stephen Hackett sums up what I think many people in the community are thinking:

    Payments made to people linking to apps with affiliate links comes out of Apple’s share of revenue generated by app sales and in-app purchases. How much money it costs them is unknown, but the idea that the reasons behind this move could be financial in nature feels pretty gross. Apple is a for-profit company, and it has no bottom-line reason to keep this program open, but sometimes doing the right thing comes with a cost.

    And John Voorhees on Apple’s statement that the App Store no longer needs affiliate links:

    If that’s the case, it’s short-sighted, but it’s certainly Apple prerogative to run its programs as it sees fit. Still, it’s not the right way to address the publications, developers, and others that have generated millions of dollars of referrals over the years in exchange for a modest 7% cut.

    I’ve argued since the first days of the App Store that Apple’s 30% cut is too high. This tax on developers is completely out of line with the value that Apple provides. The fact that Apple is bringing in so much money from services — nearly as much as the Mac and iPad combined — shouldn’t sit well with developers who are still struggling. It’s even worse now without the affiliate program, which developers could use to recoup some of that 30%.

    Note what I’m not saying. I’m not saying that Apple should lower the rate to match Stripe’s 3%, or that Apple should operate the App Store at a loss. It costs real money to maintain the App Store infrastructure and commit to featuring apps every day. But there should be a middle-ground that gives developers the best shot at a sustainable business.

    Introducing a 15% tier for in-app purchase subscriptions (after the first year) was a good start. Most developers thought we’d never see that. We should be calling for an across-the-board 15% rate for all App Store transactions. It’s the right thing for Apple to do. As Apple’s services revenue continues to grow — and the TV streaming service will only add to that — the time to make this change is now.

    → 8:57 AM, Aug 2
  • Just posted this week’s episode of Core Intuition with our initial thoughts on WWDC 2018: UIKit on the Mac, Siri’s automation-based strategy, App Store trials, and more.

    → 4:19 PM, Jun 7
  • 10 years ago today, @danielpunkass and I released the first episode of Core Intuition. It was right before WWDC when Apple introduced the App Store.

    → 7:07 AM, May 29
  • Just posted a new Core Intuition with a discussion about Google Duplex, App Store pricing, and Daniel’s rewrite of MarsEdit’s image handling code.

    → 8:48 AM, May 10
  • On the latest episode of Timetable, I talk about the upcoming Icro app for Micro.blog and what to do while waiting for the App Store.

    → 11:27 AM, May 8
  • App Store propagation delays of 24+ hours might even be worse when you’re waiting for someone else’s app to go live. Still really confused by these delays.

    → 11:45 AM, May 7
  • Core Intuition 321

    We start this week’s Core Intuition talking about the Apple education event in Chicago. More in the show notes:

    Daniel and Manton talk about Apple’s Chicago education event, and Apple’s challenge in breaking into the education market so dominated by Google. They scrutinize whether the special event was “event-worthy” or not. Daniel talks about his motivation problems with shipping MarsEdit updates, and complains again about App Store Review uncertainty. Finally, they talk about the challenge of knowing whether a product with lackluster success is on the brink of something great, or should be moved on from.

    Thanks for listening and subscribing to the show.

    → 11:51 AM, Mar 30
  • Sunlit 2.0.2 is now out in the App Store with a couple bug fixes.

    → 10:05 AM, Mar 15
  • Sunlit 2.0.1

    We released an update to Sunlit today. Lots of little bug fixes and improvements. (The App Store has been slow this week, but it should show up in your Updates tab soon if it’s not already there.)

    I also updated the Micro.blog timeline to add tiny photo thumbnails for Sunlit stories that have a title. Here’s a screenshot:

    Micro.blog timeline screenshot

    Because Micro.blog is focused on microblogging, short posts without a title still show directly in the timeline, but longer posts with many photos and a title just link back to your web site. Adding this little preview gives a hint for what is behind those links.

    → 4:17 PM, Mar 9
  • If you like what we’re doing with Sunlit, consider leaving a quick review in the App Store. We don’t link or prompt anywhere in the app for reviews.

    → 8:53 AM, Mar 8
  • Postponing the Sunlit release until tomorrow. App Store caching seems completely unreliable today. Not thrilled by this delay because we’ve had additional fixes for 2.0.1 we could’ve submitted if we knew we had an extra day of doing nothing.

    → 4:21 PM, Mar 6
  • Tired of waiting for the App Store to update, so instead I worked on something I can control: deployed some Micro.blog server improvements to add a Conversation link on the web for any post that has replies.

    → 2:23 PM, Mar 6
  • Pretty annoyed with the App Store this morning. Waiting 3+ hours for Sunlit to show up. Can never tell if I should wait a little longer or if it’s just broken.

    → 11:22 AM, Mar 6
  • Micro.blog 1.3.3 is out

    The new update to Micro.blog for iOS is now available in the App Store. As I wrote about yesterday, it includes an improved conversations gesture. Here’s the full list of changes:

    • Added swipe left on a post to view the conversation.
    • Added feed settings button when writing a new post for quickly toggling off cross-posting.
    • Added confirmation alert when removing a post.
    • Updated character counter to not include Markdown.
    • Updated sharing from other apps to not use the current draft or save it.
    • Fixed compatibility with some XML-RPC servers.
    • Fixed opening conversations from links in the timeline.

    Enjoy!

    → 9:12 AM, Feb 7
  • Micro.blog for iOS version 1.3.1 is now in the App Store. Fixes sharing photos from other apps and a few other changes.

    → 8:32 PM, Dec 29
  • Minor update to Micro.blog for iOS is now available in the App Store. Fixes posting via the Micropub API, plus a couple more iPhone X tweaks.

    → 10:50 PM, Nov 15
  • Has everyone already submitted their iPhone X-compatible apps to the App Store? Thinking I’ll do that in the next few days.

    → 4:54 PM, Oct 26
  • Timetable 66 and Release Notes

    I posted a new Timetable today after listening to the Release Notes podcast where Charles and Joe discuss requiring in-app purchase subscriptions. As I talk about on Timetable, I’ve been working on the Mac version of Micro.blog, so it was a good opportunity to make a final decision on Mac App Store support.

    Speaking of Release Notes, I’ll be out in Chicago for the conference next week. If you’re attending, hope to see you there. Ask me for a Micro.blog sticker.

    → 12:28 PM, Oct 10
  • Micro.blog for iOS version 1.1.1 is now available in the App Store. Bug fixes and refinements to the new 1.1 features.

    → 5:48 AM, Sep 20
  • Removing the App Store from iTunes is definitely the right move. Haven’t used it on the Mac in years. Even a company as large as Apple needs to focus on the right platforms.

    → 5:35 PM, Sep 12
  • Micro.blog for iOS 1.0.4 is now in the App Store with a fix for that “Share…” crash on the iPad.

    → 7:59 PM, Aug 11
  • Micro.blog 1.0.3 is now in the App Store. New user profile screen, share menu item, and other improvements.

    → 1:20 PM, Aug 9
  • Pushing the next iOS build up to Apple for approval. A few people are still on TestFlight… You should switch to the App Store version.

    → 9:04 AM, Aug 8
  • Sent an update to Kickstarter backers announcing the App Store version of Micro.blog, friend invites, and recent progress.

    → 11:27 AM, Jul 13
  • Micro.blog iOS going universal

    As I expected would happen, using iOS 11 on my iPad Pro after WWDC has inspired me to revisit the universal version of Micro.blog for iOS. Here’s a screenshot of my current build:

    Micro.blog iPad

    I plan to include this in 1.0. I’m in the process of moving the app from TestFlight to its final home in the App Store. As we prepare for the public launch, this’ll make it much easier for everyone to download it, and it shouldn’t be limited or scaled up on the iPad.

    → 11:26 AM, Jun 21
  • The iOS 11 App Store redesign story

    Three years ago I wrote that Apple should end the App Store top 200 lists, learning from Beats Music how to double down on curation:

    I wrote about Beats Music earlier, how it underscored to me that Apple needs to find the next product category to fall in love with, just like they used to feel about music. Of course we know that Apple already loves apps. Show that by doubling down on featured apps, staff picks, and app playlists.

    And:

    Apple shouldn’t wait until Thursday to feature a few great apps. Feature apps all the time. They’re on the right track with some of the “best of” sections in the store, and with the “Near Me” feature. Go a little further and it will make all the difference to bubble up great apps, and let the junk in the App Store fade away.

    I think they’ve done it for iOS 11. While the top charts aren’t completely gone, they no longer dominate the App Store user experience. Featured apps are center stage.

    Product manager Pedraum Pardehpoosh at WWDC even used the same phrase “double down” when describing Apple’s new focus on editorial content. During session 301, he said:

    We thought this was a perfect time to double down on the editorial curation that’s distinguished the App Store since its conception.

    Joe Cieplinski addresses the information density in the new App Store, pointing out that apps will be featured every day:

    That’s a big change from the weekly update schedule Apple has maintained since the beginning of the App Store. You can’t name something “Today” and then not update it every day. So instead of a few new items getting featured once a week, something new will be featured every single day.

    The “Today” tab is effectively a blog: reverse-chronological posts about what’s noteworthy in the store. It’s a much better default UI for content that is actively curated.

    The old App Store was designed like a database. Databases are good at showing grids and lists from an algorithm. But the App Store should tell a story about new apps. A blog-like format is the best way to do that.

    This plays to Apple’s strengths in design and taste. Where Google might hire more engineers to improve their store, Apple should hire more writers.

    So far I’ve only used the new App Store on my iPad, and only for a few days. After we’ve all lived with it for a few months, it will be easier to judge whether it works for developers. But it’s almost exactly what I was hoping for a few years ago. This redesign for iOS 11 is one of my favorite things to come out of WWDC.

    → 5:25 AM, Jun 12
  • Now that our new Apple developer account for Micro.blog has been approved, considering moving the app into the App Store sooner rather than later. TestFlight invites have been flaky. I spend a lot of time just re-sending invites that never went out.

    → 9:51 AM, May 31
  • On the latest Core Intuition we talk about WWDC events, a “Going Pro” mentality, and replying to App Store reviews. coreint.org/276

    → 1:13 PM, Mar 30
  • We posted the latest Core Int yesterday, covering App Store policy and whether the label “entrepreneur” defines us. coreint.org/274

    → 11:59 AM, Mar 19
  • No-pressure blogging

    I’ve been working on a post about walled gardens, the App Store, and social networks. I think it could be an important essay — a new take on the future of platforms.

    But if it’s not? If I’m wrong, and the idea is unoriginal or doesn’t go anywhere? That’s fine too! It’s just a blog post.

    I love that blogs can scale from the trivial to the important. The microblog post about what you had for breakfast. The half-baked rant about something you’re passionate about. And sometimes, the rare essay that really hits the mark and makes people think.

    → 12:50 PM, Mar 4
  • Core Intuition 254 and Kapeli wrap-up

    On Friday, Daniel and I recorded and published episode 254 of Core Intuition:

    Daniel and Manton dive into Apple’s controversial suspension of Dash developer Kapeli’s App Store account, and respond to listener Q&A about whether non-sandboxed apps are at risk of removal from the Mac App Store.

    Covering sensitive subjects like Kapeli’a suspension is difficult in a podcast format where you can’t perfectly prepare your thoughts. Did I go too far defending Bogdan Popescu? Did I not go far enough?

    Maybe we’ll know with some distance from this topic whether we reacted fairly. But I don’t think I overstated how important a moment this was for the App Store — both Apple’s influence over the narrative and as a test for their power in the store. Unfortunately the story still has a very unsatisfying ending.

    → 3:43 PM, Oct 16
  • Just posted episode 249 of Core Intuition with our reaction from today’s Apple event. Spoiler: I love Mario and hate Lightning headphones. We also discuss the upcoming App Store cleanup.

    → 10:08 PM, Sep 7
  • Long vs. pure App Store names

    David Smith has an analysis of long names in the App Store, as developers try to understand the scope of Apple’s upcoming cleanup changes. Don’t miss the text file of 255-character names he found, which are all ridiculous. I’d laugh if this kind of gaming of the store didn’t make me sad.

    I’ve always thought that the title shown in the App Store should be the actual app name. Keyword spamming is clearly bad, but I personally don’t like even tag lines in the name. Of the 4 apps from my company Riverfold that have been in the App Store, the names in the store all exactly match what is shown on your home screen:

    • Sunlit
    • Tweet Library
    • Clipstart
    • Watermark Mobile

    Maybe my sales suffered because of my refusal to add more words after the real name, but to me, these names are pure and gimmick-free. I don’t want my customers subjected to a truncated mess of words even before they use my app.

    If tag lines and brief descriptions in the App Store name are so common (and they are), then Apple should complement the new 50-character limit by having a separate 1-line description field in search results. This was discussed on the latest episode of Release Notes. My worry is that Apple attempts to fight problems with new policy alone instead of also encouraging the right behavior with App Store features.

    → 8:26 AM, Sep 6
  • Mac App Store developer survey

    DevMate surveyed 679 Mac developers to put together a report on who is using the Mac App Store vs. selling direct, what concerns developers have, which tools they use, and more. On why developers leave the Mac App Store:

    If you’re thinking giving away 30% of your hard-earned revenue is the deal-breaker, you’d be surprised. Revenue share is not the main reason developers flee. The main reason is the long and unclear App Review process, closely followed by revshare and the absence of trial versions.

    While sandboxing does show up on the complaint list, it’s ranked low as a reason to not use the Mac App Store, even though it was why I pulled my app Clipstart from the Mac App Store 4 years ago. And not much has changed since I wrote about Sketch and other apps leaving the Mac App Store last year.

    For anyone who has been following blog posts and conference talks about the Mac App Store, there won’t be many surprises in this new survey, but I found the details interesting. The survey appears to be a good snapshot of how the Mac community is feeling about selling software.

    → 1:04 PM, Aug 16
  • App maintenance and subscription rejections

    Jason Snell closed his first take on App Store subscriptions with a question about iPhone app maintenance vs. web services maintenance:

    Whether Apple would actually reject a subscription-based app that doesn’t offer any functionality outside of itself, I don’t know. It sure wouldn’t be the first time there was a baffling App Store rejection. But does Apple really want to take the position that ongoing maintenance of a web service has value, but ongoing maintenance and development of an app does not? I don’t think it does.

    As I wrote about in my post yesterday, users can more easily see the hosting costs for a web service. They’ve been trained by a decade of paying for web subscriptions. Maintenance for the app itself has some differences.

    Think about how costs scale if an app becomes popular. A web service becomes expensive to run, often thousands of dollars each month. You could say that a developer’s time for app maintenance is also thousands of dollars, but it’s essentially fixed. Outside of customer support costs, the incremental cost to a developer for an app doesn’t increase in the same way it does for scaling a backend service.

    I hate that Apple has the power to reject our business model for a potential app. I’m now leaning more to the idea that Apple should approve nearly everything and let customers decide on the value. But there is a difference between maintenance of an app vs. a web service, and the services that are clearly appropriate for subscriptions will be the most successful apps using this new model.

    → 6:27 AM, Jun 10
  • Core Intuition 236 and app subscriptions

    We published Core Intuition episode 236 today, discussing the recent App Store announcements and a listener question about offices. We wrap up with plans for WWDC.

    There has been a lot of great blog posts and podcast episodes already on the App Store subscription change. I listened to Under the Radar 31 and the Release Notes special edition today and recommend both. The most confusion seems to be around what kind of apps are appropriate for subscriptions, where by “appropriate” I mean “what Apple will approve”.

    John Gruber also follows up at Daring Fireball on this question:

    Professional apps that require “a lot of maintenance of new features and versions” don’t fit either of those categories. Would Twitter clients like Tweetbot and Twitterrific qualify for subscription pricing? After talking to Schiller yesterday, I thought so. Now, I don’t know.

    As I mention on Core Intuition, apps that have a backend service with obvious hosting and maintenance costs — a music streaming service, an invoicing web app, or a blogging platform, for example — are easier for users to understand as needing to be subscriptions. Twitter apps are an interesting example because some are pure clients to Twitter’s backend, but many increasingly have their own app-specific services like timeline syncing or push notifications.

    For years Apple has allowed apps to use auto-renewing subscriptions. I had an iPhone app and companion web service that was approved by Apple for auto-renewing subscriptions, after I made the case for the service as a “cloud” archive. From section 11.15 of the App Store review guidelines:

    Apps may only use auto-renewing subscriptions for periodicals (newspapers, magazines), business Apps (enterprise, productivity, professional creative, cloud storage), and media Apps (video, audio, voice), or the App will be rejected

    From my experience and listening to other developers, I’ve had the impression for a while that Apple would essentially reject most auto-renewing app submissions by default. While we still don’t know what “all categories” means in the new announcement, I expect it means that there will no longer be a kind of blanket rejection. Apple will still reject many apps as poorly suited for subscriptions, though, and maybe that’s okay for now.

    (I’m conflicted on this point. John Gruber’s suggestion to approve everything and let the market decide is compelling and fits better with my instinct that the control should be in developers' hands.)

    “Subscription fatigue” is a real thing that I’ll occasionally hear from customers about. No one wants to pay $1/month to 40 different apps and services; it feels like a burden in a way that paying the same total price to just two apps at $20/month does not. Nevertheless, subscriptions are very powerful. Everything I’ve done over the last few years is to position myself to eventually have a recurring-revenue success.

    → 1:47 PM, Jun 9
  • Paid search and App Store profit

    Reacting to a Bloomberg article about Apple adding paid search results in the App Store, John Gruber writes:

    This sounds like a terrible idea. The one and only thing Apple should do with App Store search is make it more accurate. They don’t need to squeeze any more money from it. More accurate, reliable App Store search would help users and help good developers.

    The Bloomberg article almost makes it sound like there’s a 100-person team working on paid search. I doubt that’s true. More likely, there’s a team working on several improvements to the App Store, including better search.

    Daniel Jalkut is also very skeptical:

    It’s hard to see how paid placement would consistently benefit either Apple or its direct customers. It’s unlikely that paid listings would be used to highlight apps that are in line with Apple’s other goals for the store.

    He rightly points out that making money from the App Store is Apple’s secondary goal. It’s more important to have an ecosystem of apps that make the iPhone itself indispensable. As I argued in a blog post in 2011 about free apps and distribution, I don’t think the App Store should be a source of significant profit for Apple at all.

    And if we’re keeping score with old posts where I write not what Apple should do but what I wish they’d do, see “I hope iAd fails” from 2010. iAd is shutting down in June.

    I just can’t believe Apple would prioritize paid search over all the other App Store feature requests that developers have. So I prefer to ignore the paid search rumor and instead take away from this article just the good news: Apple has a new team focused on improving the App Store.

    → 7:20 AM, Apr 19
  • Enjoyed the CocoaConf podcast with Brent Simmons. Life before the App Store: “It was fun! We could release software any time we wanted to.”

    → 2:35 PM, Feb 5
  • Submitted a new app to Apple for review this morning. Not sure when it will be released yet, but felt like it would be good to get it through the App Store review process just so that it’s ready.

    → 7:27 AM, Jan 17
  • Phil Schiller and the App Store

    Apple announced some leadership changes today, including that Phil Schiller will now lead the App Store on Apple’s various platforms:

    "With added responsibility for the App Store, Phil Schiller will focus on strategies to extend the ecosystem Apple customers have come to love when using their iPhone, iPad, Mac, Apple Watch and Apple TV. Phil now leads nearly all developer-related functions at Apple, in addition to his other marketing responsibilities including Worldwide Product Marketing, international marketing, education and business marketing."

    You may remember that Phil Schiller has gotten involved in controversial App Store rejections in the past, going back to 2009. See this post from Daring Fireball about Ninjawords, and another article at Techcrunch by MG Siegler.

    On recent episodes of Core Intuition, and in a blog post, I’ve argued that Apple can’t just make small improvements to the Mac App Store anymore. The time for slow iteration is over; now they have to make big changes to get developers back. I’d like to believe that putting Phil in charge is exactly that kind of first big step.

    Update: Less optimistically, though, there was this post in 2012 from Rogue Amoeba.

    → 8:49 AM, Dec 17
  • Apps on the new Apple TV

    We’ve had fun since Friday exploring the App Store on the Apple TV. There are a lot of expected apps but also some nice surprises. The only app that’s really missing for us is Sling TV. As soon as that ships, we’ll no longer need the Roku.

    I love apps that use full-screen photos to take advantage of the big screen — obviously games and streaming video, but even apps like Airbnb. Conrad Stoll also released a new game called Picturesque, where you try to identify photos of national parks in a time limit that varies by difficulty:

    "It's always exciting when you can build a product that bridges different hobbies and interest. Picturesque combines my work as an iOS developer with my passions for Backpacking and Photography. I'm happy for the result to be both my first game and my first foray into this new platform."

    It’s also great to see Space Age make the jump to the Apple TV. We’ve been playing a few games that are free downloads because we had already purchased them on iOS, including Oceanhorn and Crossy Road.

    → 1:00 PM, Oct 31
  • Gravity and the App Store

    Dan Moren, writing at Six Colors about the rejected app Gravity:

    "Really, what Apple needs is a small group within the App Store review team to flag apps that are pushing the envelope in smart, respectful ways; work with those apps’ developers; and present overall recommendations to App Store leadership—perhaps even reporting directly to Eddy Cue."

    I love this idea. It would both minimize unfair app rejections and help innovative apps bubble up to the featured sections in the App Store.

    → 1:50 PM, Oct 28
  • A great developer can come from anywhere

    It’s March 2009, the height of SXSW in Austin before the conference gets too big for itself. I’m hanging out downtown with tech folks from a blogging startup, having dinner and beers before we head to the party they’re putting on. The CTO, one of the first employees at the company, is talking about Memcache servers and MySQL scaling, and I’m hanging on every word. I love this stuff.

    I’m a Mac and iOS developer, but I often take a break from native app development to work on server software. So I’m asking him about MySQL replication and what it’s like to run a schema migration without the database falling over. The conversation sometimes shifts back to Apple platforms, and he says he’s been thinking about going to WWDC. I had been attending WWDC for a while, so I say sure, it’s expensive but you should consider it. If you’re doing more web stuff, though, maybe it’s not as important that you attend.

    We walk over to the party venue. It’s bigger and more crowded than he thought it would be. Their company has really taken off, growing well beyond the early days when it was just him and the founder trying to build something new. And it’s at this point that he turns to me and asks a question that brings us back to iOS development:

    "So what do you think of my app, Instapaper?"

    In answer to Marco Arment, at that time the CTO of Tumblr, I mutter something about liking it, but I haven’t really gotten it into my workflow yet. Hopefully whatever I said was encouraging. In subsequent years, of course, Instapaper would be one of my favorite apps.

    Later, replaying these conversations, I realized that I asked the wrong questions and gave the wrong advice. About WWDC, I should have said “Yes, absolutely!” with an exclamation point. Buy a ticket. If you can’t afford it, go anyway because you need to be there.

    But I didn’t say that because I wasn’t listening closely enough. I was so busy asking questions about Tumblr, that I wasn’t listening to the excitement in his voice about Instapaper. I was so busy thinking about server scaling and databases and all this other stuff that I could’ve learned from a book, that I didn’t hear what he was really saying.

    I should have asked about iOS pricing, free versions, sales, UI design, who did the icon, what does the private API look like. But I didn’t ask those things because I missed the big picture, how dominant the App Store would become for distribution, and so I missed what mattered. I’d like to think that since then I’ve gotten better at listening.

    Daniel Jalkut and I had Marco as a special guest on Core Intuition 200 not just because he’s a friend but also because he so well represents the goal that many of us have and our listeners have — to start our own company, to find success not just one time but again and again, and to have as thoughtful an approach as possible in the craft of software development.

    This week I’m in Indianapolis for the Release Notes conference. While I will have some stickers for anyone interested in my new microblogging platform, and I’ll probably ramble about it at some length if asked, I’ll also be listening. I’ll be listening because you never know which random developer you just met will end up doing their best work in the years ahead, and you want to be as encouraging as possible, offer the right kind of feedback, and also learn from their perspective.

    There’s a great line in the Pixar movie Ratatouille:

    "Not everyone can become a great artist. But a great artist can come from anywhere."

    I believe that’s equally true for developers. We often see someone go from nothing to a top app in the App Store. We often see someone start without an audience and then make friends on Twitter and blogs through the quality of their writing alone. And so we welcome new voices all the time if they’re respectful.

    There’s been some debate about Overcast 2.0’s patronage model. Some of the discussion is healthy — how does a successful business model for one developer apply to other apps? — and some of the discussion is divisive. Instead of asking the right questions, it’s easy to jump straight to a conclusion with the dismissive statement: “that’s fine for Marco, but his approach would never work for other developers”.

    The “that’s fine for Marco” attitude is poison for our community because it takes the opposite approach as that Ratatouille quote above. It implies that some developers have such an advantage that the rest of us shouldn’t even bother, because it’s not a level playing field. It’s true that some developers today have an advantage, whether through good timing or just a long history of shipping apps, but the lesson isn’t to give up; it’s to instead learn from it, and look at our own strengths. What small head start do we have that could grow into a great success tomorrow, too?

    Rewind a handful of years, back to that day at SXSW when I could name plenty of developers who had more attention and success in our community than Marco Arment. You can be damn sure that didn’t discourage him from taking Instapaper from an “in my spare time” niche app to the top of the News section on the App Store.

    I’ll never accept the implied negativity in the “that’s fine for Marco” argument. I’ll never accept that we should be jealous of another developer’s success instead of inspired by it to do our best work.

    → 2:43 PM, Oct 21
  • iAd hypocrisy

    I was looking for a different old post in my archives, and stumbled on this one: “I hope iAd fails”, which I wrote 5 years ago this month. One of my points was that we had a healthy marketplace in the App Store for normal people to actually pay for apps:

    "Do we really want to give that marketplace up? Because once it’s gone, and iAds are the norm, it will be an uphill battle to get anyone to pay for anything."

    Fast-forward 5 years to today, and well, we’re on that hill right now. Except there’s a landslide and I don’t know who’s going to get buried.

    On the Upgrade podcast, Jason Snell and Myke Hurley talked about whether iOS 9’s Apple News was relevant: what problems is it solving, if any, and — because it will feature unblockable ads powered by iAd — how does it fit into the larger issue of blocking web ads and closed platforms? The discussion starts about an hour in.

    (If you’ve used Apple News already, you may not have even seen any ads yet. But Apple’s page on Apple News Format makes it clear that they will be encouraging iAd for publishers: “Monetization is made simple with iAd”.)

    I stand by the opinion that iAd is a mistaken strategy. Apple, if you’re serious about this fight with Google, go all-in on the fight and abandon iAd. It seems hypocritical to attack web ads while rolling out your own news platform with ads that can’t be blocked.

    → 8:07 AM, Sep 28
  • Peace, indies, and the App Store

    You’ve probably heard that Marco Arment has pulled his content-blocking app Peace from the App Store. The app was extremely successful:

    "As I write this, Peace has been the number one paid app in the U.S. App Store for about 36 hours. It’s a massive achievement that should be the highlight of my professional career. If Overcast even broke the top 100, I’d be over the moon."

    I’ve seen some comments asking why he didn’t think to do this sooner, before he even shipped the app. But we are just now starting to understand the impact of ad blockers in iOS 9. I don’t think it’s an exaggeration to say that the web is different than it was a few days ago, and so our choices — and Marco’s — are different too. As I mentioned yesterday, content blockers are one facet of an overall shake-up for the web.

    Brent Simmons writes that only indies can do what Marco did. Marco must have left a lot of money on the table with this decision. It will always look like the right call to me when someone goes with their gut feeling and not with profit.

    → 8:53 AM, Sep 19
  • On this week’s Core Intuition, we talk about my trip to Europe, working while on vacation, the App Store, and AppHub: http://coreint.org/194

    → 6:32 AM, Aug 21
  • App Store delivery truck

    Charles Perry follows up from Brent’s post on the App Store with this point of view:

    “Today, the App Store is basically your delivery truck that takes cash on delivery. We wouldn’t blame a delivery truck for our business failure. It doesn’t make any sense. It’s not a delivery truck’s responsibility to ensure that there’s a market for our products. That’s what market research is for. It’s not a delivery truck’s responsibility to advertise our products or introduce them to customers. That’s what marketing is for.”

    I really like this analogy. However, if you take everything Charles says as truth, it reveals an even more serious problem: the 30% that Apple charges for distributing bits on their truck is outrageous. It’s flat-out wrong to charge such a high percentage if they are providing no value above credit card processing and file hosting.

    → 1:34 PM, Jul 3
  • Goodbye Riposte

    Jared Sinclair announces that Riposte will no longer be available:

    “As part of an agreement reached over an alleged trademark infringement, Riposte (the App.net app I made with Jamin Guy) will be removed from sale on the App Store. We’ll also be taking down the riposteapp.net homepage.”

    Even today, Riposte is arguably the best social networking client out there. It pioneered consistent gestures for navigation. It will remain on my home screen for some time to come.

    → 8:01 AM, Apr 13
  • On the latest Core Intuition, we follow up on App Store rejections, react to Swift 1.2 and Tim Cook’s recent comments, and discuss new blogging systems.

    → 12:42 PM, Feb 15
  • Core Intuition 171

    On this week’s Core Intuition:

    "Daniel and Manton touch again on the subject of killing off apps, assess the effectiveness of protest movements against the App Store, catch up on the state of the art for appealing App Store rejections, and acknowledge the coming end of NSConference."

    In this episode we talked about how I was going to need to more formally appeal the Sunlit 1.3 rejection, not just comment in the Resolution Center. But shortly after we recorded, the app magically went live in the store anyway. I was very happy to avoid making further coding changes, though I expect I’ll have to revisit this if the app is ever rejected again.

    → 7:09 AM, Feb 6
  • After a week hanging around in Apple’s Resolution Center, Sunlit 1.3 was approved and went live in the App Store last night. sunlit.io

    → 9:59 AM, Feb 5
  • Core Intuition 169

    Last night we published episode 169 of Core Intuition. As we’ve done on a couple recent episodes, we let this one run for an hour with a discussion of App Store revenue, sales charts, and progress on our own projects. Sunlit 1.3, the update I mention in the podcast, is complete now and submitted to Apple for review.

    → 7:00 AM, Jan 23
  • Tweet Library 2.7 and promising features

    Last year I wrote that I would be removing Tweet Library from the App Store at the end of December, and later said on Core Int and in a tweet that there would be one last update before the app is gone. It’s well into January and the old version is still for sale. I’m over a month behind schedule but still plan to release the updated version and stop selling the app.

    On the latest Release Notes podcast there was a great discussion about when to give up on an app that isn’t making money, including a mention of my plan with Tweet Library. Joe and Charles talked about why it’s usually such a bad idea to promise features before you ship, and whether there’s an obligation to give customers any updates at all.

    I pretty much agree with everything they said, but the upcoming Tweet Library 2.7 “features” are different. My goal with this release is for the app to be functional and stable for as long possible. I think the app needs better syncing of tweet collections to help future-proof it, to make it easier for customers to move between iOS devices when they upgrade their iPhone or iPad a year from now. For an app that is going away, I should do everything I can to make sure that a customer’s data is accessible and that import and export are as robust as possible.

    It’s a reasonable question to ask why I would spend so much time working on something that will essentially bring in no additional revenue. But while it won’t directly make any money, it probably helped convince some new customers to buy the app over the last month, and it will very likely reduce the support burden for the app over the following year.

    I also view it as a sort of parting “thank you” to my customers. It’s just the right thing to do to wrap up the app. Panic did the same thing when they stopped selling Unison, releasing a major free update at the same time.

    If you’re interested in picking up a copy of Tweet Library before it’s too late, you can buy it on the App Store for $4.99. The new version should ship in early February.

    → 10:55 AM, Jan 21
  • Core Int and Hour of Code

    We were lagging a little after the Thanksgiving break, so we posted two episodes of Core Intuition last week. On the latest episode we talk about the Hour of Code and welcome new listeners who found our podcast from the App Store feature.

    After we recorded, I helped out my son’s elementary school class with the Hour of Code tutorials. I learned a lot and came away even more impressed with the project. The reach is pretty incredible. Even if it only sways the interest of a couple kids here and there, but spread over classrooms all across the world, you can imagine how big a difference it might make.

    → 9:06 AM, Dec 15
  • Tweet Library 2.6.1 is now available in the App Store. It fixes layout problems on the iPad, a crash when sharing URLs, and updating Twitter saved searches.

    → 7:23 AM, Oct 10
  • Core Intuition episode 157 is now online. We talk about Brent going to Omni, trends in indie and full-time work, more on the iPhone 6, and App Store delays.

    → 11:11 AM, Oct 3
  • Sunlit 1.2.1 is now available in the App Store, fixing some problems communicating with Flickr after they switched to SSL-only. We fixed this months ago but I, uhm… forgot to submit it to Apple until recently.

    → 10:16 PM, Sep 3
  • Sunlit 1.2

    Sunlit version 1.2 is now available in the App Store. It includes a few minor improvements and one major change: you can now use the app with only a Flickr account. It no longer requires App.net.

    We hope this will allow more people to try the app. At any time, you can always add your App.net account to the app’s settings and it will unlock the more advanced features: syncing, sharing stories to other App.net users, and multi-user collaboration so that anyone can add photos and edit text in a story.

    Making App.net optional instead of required meant rethinking what the minimum features were that all users should have. Obviously you have to be able to create stories, add photos, include text descriptions, and use filters. But we also kept coming back to one thing: we could not ship without also supporting web publishing. The bulk of work on Sunlit 1.2 was creating a parallel implementation for publishing that would seamlessly work with exactly the same UI, with or without App.net.

    Some people may ask why we chose Flickr instead of creating our own user accounts system, or simply having no registration. To support publishing, it helps to have some unique username for a user, and a secure way to authenticate them on the server. It won’t surprise anyone to hear that a lot of people have Yahoo accounts. With a redesigned web and mobile experience, plus 1 TB of free photo storage, Yahoo’s giving Flickr something of a new resurgence. There’s a lot we could build on the Flickr API.

    At the same time, Sunlit’s App.net support is a powerful differentiator and we’ll continue to improve it. It lets you own your data, share it with other apps like Ohai, and sync to multiple users. I still believe in the App.net API and user community; it’s too good a platform to give up on.

    → 12:47 PM, May 8
  • Flappy Bird on steroids

    On this week’s Core Intuition, we talked a lot about Flappy Bird (and also Threes, and a few other things). One of the points I tried to make is that some of the negativity pointed toward the developer was totally uncalled for. Marco Arment says it well in his post on this topic:

    “Flappy Bird’s success was hilarious, but it also appears to be completely earned. I’ve read the posts suggesting he cheated at the ranks or reviews, but I haven’t seen any that supported those claims enough.”

    As I read Marco’s full post, and re-listened to what Daniel and I said on the podcast, I do wonder if developer Dong Nguyen had been so overwhelmed by the success that the line blurred for him between the death threats and the joke “this ruined my life” app reviews. You’d have to have a pretty thick skin to not let it get to you, even if I hope that most users had a good sense of humor about the whole thing. It’s true that the game is crazy addicting, but unlike some games — the worst of which are driven by consumable in-app purchases, gimmickly rigged to get users to feed money into the game — Flappy Bird is addicting in kind of the best way, because it’s something we’re all playing and can laugh about together.

    And Nguyen cares about more than just money. He’s demonstrated an empathy for customers that seems to be lacking in many corners of the App Store. Where some developers said he was leaving money on the table by not having more ads, and other developers were quick to rush in with rip-offs of his app, Ngugen wasn’t afraid to admit it was out of control and pull the app from the store. Do you think any of the other developers who renamed their app to include the word “flappy” would have pulled their app? Not a chance.

    I hope Nguyen can bounce back from this and ship more games. With so much attention now, it’ll be fascinating to see what they look like. Or if he’s stashed away some of that $50k/day and wants to just chill out for a while, that’s fine too.

    → 1:16 PM, Feb 13
  • Ending the App Store top 200

    I was chatting with some developers this week, complaining about this post on spamming the App Store and wondering if we’d ever have a better App Store, when I finally realized how we get there. The block for me had always been the top 200 lists. We all know that you can game them, buy your way in, and apps that make it in even on their own merits have a huge advantage over everything else, sometimes for months. But I couldn’t conceive of how you could actually get rid of them and if it would make the store better or worse.

    The answer is in Beats Music. They have no overall top 200 list! Instead, they have a bunch of people — musicians and writers who deeply care about music — curating playlists. The top 25 playlists in a genre are so buried in the app that I had to search them out just to write this blog post, because they seem to carry no more weight than any other playlist. Much more common are playlists like “our top 20 of 2013”. That’s not a best-selling list; it’s based on real people’s favorites.

    There are literally hundreds or maybe thousands of other playlists. Intro playlists for a band, related artists that were influential to a singer you like, playlists for a mood or activity, and more. This extra manual step makes it much easier for an algorithm to surface great music: just look for playlists that contain songs you already like, and chances are good that you’ll discover something new.

    I wrote about Beats Music earlier, how it underscored to me that Apple needs to find the next product category to fall in love with, just like they used to feel about music. Of course we know that Apple already loves apps. Show that by doubling down on featured apps, staff picks, and app playlists.

    How would this fix the junk problem in the App Store? Simple. No one in their right mind would ever feature one of these ad-filled, “re-skinned” cheap apps. Great recommendations mean less reliance on search, making scam apps more difficult to find by accident. (This focus is so complete in Beats Music, for the first couple days of using it I didn’t even realize you could search for a specific song or album.)

    This idea isn’t new. Here’s Jared Sinclair on app playlists, with the twist that they’re based on apps you have installed and use:

    “App playlists should be rigorously simple: just a list of apps. Not all the apps ever downloaded, but the apps that a given user currently has installed on their device. The assumption is that if somebody has an app on their device, they probably like it.”

    That would be great. But seeing Beats Music ship with almost no traditional music charts at all — in an industry that has embraced the top 40 for decades — tells me that the Beats approach would also work for apps. I think you need both an “installed” playlist and many more fully curated playlists to actually replace the top 200 in the App Store.

    Apple will need to ramp up their staff to do this, but if a new company like Beats can do it, surely a company as huge as Apple can also try. And they’ll have help from app fans everywhere. Writers are already doing this: see Federico Viticci’s must-have iPad apps of 2013 (could easily be an app playlist) or all the photo apps mentioned on The Sweet Setup (favorite photo apps playlist) or TechHive’s 5 apps for budgeting (my playlist would’ve added MoneyWell).

    Apple shouldn’t wait until Thursday to feature a few great apps. Feature apps all the time. They’re on the right track with some of the “best of” sections in the store, and with the “Near Me” feature. Go a little further and it will make all the difference to bubble up great apps, and let the junk in the App Store fade away. For the first time I can imagine the store without a top 200 at all, and it looks amazing.

    → 12:40 PM, Feb 7
  • Core Intuition 121

    On the latest episode of Core Intuition, we talk about how the Sunlit launch is going, expanding on my post about Sunlit and Storehouse. We also follow up with some comments from the Glassboard on privacy policies and the App Store review guidelines.

    This week’s show was sponsored by CocoaConf. They have 5 cities planned for the next few months: Chicago, Washington DC, Austin, San Jose, and Raleigh. I’ll be speaking at the stop here in Austin. If you’re in the area and attending, hope to see you there!

    → 2:40 PM, Jan 24
  • Tweet Library 2.4

    The latest version of Tweet Library was approved by Apple last night. It features an updated design for iOS 7, a new app icon, and a bunch of bug fixes. I also dropped the price to $4.99, universal for both iPhone and iPad, and it’s a free upgrade for all existing customers.

    The App Store screenshots weren’t updated yet, so I put together some screenshots using Sunlit here.

    I’m pretty happy with how this release turned out, but there’s still more work to do. I’ll be following up this release with some additional improvements specifically for iOS 7 soon. You can grab version 2.4 from the App Store here.

    → 8:42 AM, Oct 31
  • Tweet Library 2.3

    Tweet Library 2.3 shipped last week, and I just submitted an update last night to fix a few crashing bugs and other minor problems with the release. I’m pretty happy with this version. In addition to finally switching to Twitter’s v1.1 API — easier said than done; I used several API calls that were changed or completely went away — this release added better gestures, a month filter to the iPhone version, and an updated UI with a lighter, clearer design.

    You can see the full changes in the release notes, or listen to episode 88 of Core Intuition. Daniel and I discussed the expedited review process and new versions. Tweet Library 2.3 is available in the App Store for $7.99 as a universal app for both iPhone and iPad.

    → 6:19 AM, May 9
  • App Store old app maintenance

    David Smith on cleaning up the App Store:

    “The App Store currently has around 800k active apps listed. I suspect a significant number of these haven’t been updated in more than 12 months. An app that is listed for sale but is no longer under active development creates the possibility for bad user experience. It is like a grocery store that leaves expired produce on its shelves.”

    He makes a good argument for removing old apps from the store, but I’d probably hesitate going all the way to actively take them out. There is certainly too much clutter in the App Store — too many apps that aren’t providing much value, some with little chance of an update. But I also dislike the already fragile state of App Store inventory. iOS apps require much more active maintenance than traditional, direct download Mac apps, which can be hosted anywhere and stay available without constant attention from the developer.

    At one point on episode 14 of The New Disruptors podcast, Glenn Fleishman talked with John Gruber about apps as a unique art form unlike paintings or novels or even film because apps are never done. John Gruber from that show, talking about software:

    “To me it is an art form. But it is the one thing that is continuously diddled with. You write a novel and it’s done, it’s out there. Once it’s published, it’s published. You make a movie, it’s done. George Lucas gets a lot of flak because he keeps revisiting his old Star Wars movies and making a change here and there, but it’s not like every year he comes out with a new version of Star Wars. […] But software — an app that has a vibrant and still-growing user base — it’s the same thing, constantly being iterated. It’s the only art form that is like that.”

    There are always bugs, always missing features, and always (as is David’s point above) new hardware to adapt to. It’s an art form that won’t stay still, so maybe there is an inherent impermanence to it.

    But if apps are an art form, an important part of our culture, then it shouldn’t require so much work to make sure they don’t disappear forever, so quickly. This happened to me just this week, actually. I forgot to renew my iOS developer program account and my apps were automatically removed from sale for a few hours while I scrambled to pay my $99 again.

    Maybe there’s a compromise solution in here somewhere. Instead of being removed from sale, abandoned apps could switch to an archived state. They would no longer show up in top lists or even search, but could still be found with a direct link. With the right kind of fallback like that, Apple could be even more aggressive about gearing the App Store user experience around new apps and modern devices, without sacrificing what is good about the long tail of old apps.

    → 8:57 AM, Mar 22
  • Direct download as a bargaining chip

    In the closing paragraph of “my Mac App Store follow-up post”:www.manton.org/2011/06/m… I suggested that eventually most developers will exclusively distribute through the App Store. John Brayton, the developer of “CloudPull”:www.goldenhillsoftware.com for Google Docs backup, “called this out on Twitter”:twitter.com/johnbrayt…

    "Good post, but disagree that selling outside the MAS won't be worthwhile. IMHO we should be using our own stores as bargaining chip."

    “In a thread to the MacSB mailing list”:tech.groups.yahoo.com/group/mac… John has a related version of this reasoning:

    "Selling independently provides protection against Mac App Store policy decisions that could affect my app. If Apple decides tomorrow to kick me out of the Mac App Store, I would take a hit but I would still be able to sell my app."

    I couldn’t agree more, to both points. There may be some advantages to going App Store-only — less initial setup for checkout and licensing, no confusion about which version to buy, or where to upgrade — but indie Mac developers should be doing everything they can to control their own destiny. Having your own store is just good business sense.

    → 7:52 AM, Jun 26
  • Mac App Store follow-up

    I’ve been sitting on this post for a while. First the good news: “Clipstart”:www.riverfold.com/software/… is in the Mac App Store. Overall I was very happy with the response and glad to have a new way for customers to find the app.

    I’ve received a bunch of good feedback on “my blog post about Apple’s 30% cut”:www.manton.org/2011/01/a… A few people are really upset with Apple, and there are posts in the dev forums about Mac apps that still weren’t approved for one reason or another weeks after the store launched. Other developers keep quiet, either for fear of rocking the boat or because they are happy with their sales and don’t see a significant problem.

    And then there’s most of us who know Apple can do even better. We’re frustrated when an app (not just our own) is rejected or stuck in review indefinitely, but we just accept that things are a little dysfunctional and cross our fingers that maybe Apple will magically become more transparent.

    But it’s not going to happen by itself. It’s not going to happen because the culture of Apple under Steve Jobs is secrecy. Apple is about great products, sure, but they’re so obsessed with the big reveal that it weakens their communication with developers.

    From a “MacSB mailing list post about WWDC”:tech.groups.yahoo.com/group/mac… by Dave Howell, written back in February:

    "Second, Apple employees are no longer allowed to talk about anything. In the past, half of the value of WWDC was talking directly to the folks who wrote the OS frameworks you have questions about. But now the answer to any question is always either 'file a bug' or 'send an email to devprograms@apple.com.' They're all under a gag order."

    The baffling part is that many of the problems in the App Store process are easily solvable. The iTunes Connect team could, for example, make it a priority to answer all email. I don’t know what the organizational structure is over there, and I’m sympathetic to what must be a flood of app submissions, but it doesn’t feel like App Store support gets the same quality treatment that Developer Technical Support does.

    Contrast with “Gus Mueller’s point on Twitter”:twitter.com/ccgus/sta…

    "I'm with you on the 30% + silence issue. With PayPal, they'll call me back when I email them with problems or questions."

    “Michael Tsai echoes this”:mjtsai.com/blog/2011… on his blog:

    "The main value of Apple's 30% cut is access to a larger market, but it still doesn't look good that companies such as PayPal, eSellerate, and E-junkie charge much less and provide great service. I can e-mail or call those companies and get answers right away."

    Good support takes extra resources and it costs money. Luckily Apple has both, and that’s why drawing attention to Apple’s 30% cut was key to my original argument. Developers are playing by Apple’s rules and helping to fund the App Store.

    Despite all this, I’m upbeat. In 2011 I want to look for ways that I can help Apple succeed, such as filing bugs. For years I swore off bothering, because it took so long to turn around a fix, if ever, and I had long since worked around a bug and moved on. iOS changes that delay because it improves so significantly every single year.

    I’m all for “praising Apple when it’s deserved”:www.marco.org/2011/02/0… but history shows that Apple improves the App Store when people complain. My posts are negative when it’s warranted and worth paying attention to.

    The App Store is getting better. (I love that the Resolution Center is there even if I hope to never need to use it.) The writing is on the wall that a year from now most apps will be distributed through the Mac App Store, and the savings and independence of direct download sales won’t be worth the maintenance of two separate forms of distribution for many developers. But if Apple holds all the cards in this relationship, then we must hold Apple to a very high standard.

    → 9:22 AM, Jun 21
  • Where Apple went wrong with free apps

    John Gruber has a solid summary of the issues around in-app purchase. Regarding the closed platform:

    iOS isn’t and never was an open computer system. It’s a closed, controlled console system — more akin to Playstation or Wii or Xbox than to Mac OS X or Windows. It is, in Apple’s view, a privilege to have a native iOS app.

    This is the root of nearly every strength and problem with the App Store. I’ll never be happy about it. But in-app purchase restrictions are even more complicated than that. It started not just with the controlled environment but the decisions around free apps.

    Michael Tsai points to this Peter Oppenheimer quote from late February that Apple runs the App Store at “just a little over breakeven”. I’ve argued that Apple’s 30% tax is about growing that to significant profit at the expense of developers, but in the back of my head I’ve also been concerned that maybe it’s just to keep the App Store from falling into the red. Maybe they are really struggling under the weight of what they created, and long app review times and lack of focus around the Mac App Store launch are just symptoms of that.

    If this is true, then I’m more sympathetic to Apple’s predicament. They aren’t being greedy; they’re just trying not to lose money. But that doesn’t mean they didn’t make a mistake.

    Steve Jobs, announcing the App Store in March 2008:

    You know what price a lot of developers are going to pick? Free, right? So when a developer wants to distribute their app for free, there is no charge for free apps. At all. There’s no charge to the user, and there’s no charge to the developer. We’re going to pay for everything to get those apps out there for free. The developer and us have the same exact interest, which is to get as many apps out in front of as many iPhone users as possible.

    I remember being surprised when I heard this. We take for granted now that much of the App Store’s success is because of free apps, but I’m not sure it had to be that way. The iTunes Music Store launched with a full paid catalog of music. Many of the hits in the App Store, like Angry Birds and Doodle Jump, have never been free.

    But watching Steve Jobs from 2008, you can tell Apple was worried that what happened to the Mac (lack of third-party apps and games) might happen to the iPhone as well, so they gambled the profitability of the App Store away to encourage as many apps as possible. That was their choice.

    Again, from Steve Jobs: “We keep 30% to pay for running the App Store.” Not a profit center. Not a business. Just to pay for running the store, so that the user experience for app discovery on the iPhone is second to none.

    Today, we know that Apple has never planned well for free apps. You don’t need to look much further than their reversal of allowing in-app purchase in free apps to see that they are making this stuff up as they go along.

    When Steve Jobs said it, offering free apps for so little seemed almost foolish, like Apple was compensating for the high 30% by giving too good a deal to free apps. Why not charge some hosting fee? Or why not give up exclusive distribution and let free apps be installed directly by the user without forcing everything through the App Store? Unlimited bandwidth, promotion in the store, and everything else just for the $99 dev program fee was a pretty good deal.

    And now I wonder if Apple hasn’t been backpedaling ever since, trying to make up for that mistake: free apps are a burden. iAd was the first correction, because a share of revenue from free apps was going to Google instead of Apple. In-app purchase is the next correction, because real value can be delivered in a free app with transactions handled elsewhere.

    Apple can’t accept a future in which too many apps are technically free — something that has already happened on Android — unless they are also taking a cut when money changes hands outside of app download.

    Matt Drance clearly spotted the loophole that forces Apple to be so strict with in-app rules:

    30% to Apple across the board — app sales, IAP, and now subscriptions — is consistent, clear, and uncheatable. That cheating bit is significant: a 10% commission for subscriptions, for example, would see developers adopting the subscription system en masse so they could keep more money. Apps that were once $2.99 would suddenly be asking for installments like late-night infomercials.

    Apple is trapped by their original decision to shoulder the cost of free apps. They encouraged free apps and now they’ve got one band-aid on top of another — advertisements, in-app purchase, subscriptions — all trying to make free apps work for the App Store bottom line. These changes make developers nervous because all the power lies with Apple.

    Free apps and the problem of exclusive distribution are linked. Get rid of free apps, and the store can support itself naturally. Get rid of exclusive distribution, and Apple can be more creative about charging developers who do want to participate in the App Store. If Amazon isn’t happy with Apple’s terms, users can install the Kindle app outside the store and it doesn’t cost Apple anything to maintain.

    Apple, want to charge 30%? Go for it. Want to make the submission rules more strict? Fine. Want to adjust how you run the App Store to reflect what’s happening in the market? No problem. Just give developers an out. We are going to be back here year after year with the latest controversy until exclusive app distribution is fixed.

    → 11:49 AM, Mar 8
  • iPad 2 (and tweets)

    I couldn’t be more excited about the iPad 2. Yes, “most of it was expected”:twitter.com/manton/st… but faster and more memory is exactly what the iPad needs. I’ll be getting it on day 1 and can’t wait to give Tweet Library a try on the new hardware.

    During the announcement I collected 70 tweets that I thought captured the event. You can “view them on tweetlibrary.com”:tweetlibrary.com/manton/ip…

    Speaking of Tweet Library, Apple just approved version 1.2.2. It fixes a handful of bugs and adds a few new things, like block and report spam, for those of you using it as your main Twitter client. Check out the “full release notes”:www.riverfold.com/software/… or view it “in the App Store”:itunes.apple.com/us/app/tw…

    → 7:06 AM, Mar 4
  • In-app purchase changes

    With the recent release of “The Daily”:www.thedaily.com and the news of “Sony’s e-book app rejection”:arstechnica.com/apple/new… there’s speculation that Apple will change the rules around iOS in-app purchases. The 30% cut makes it difficult for some businesses to move to the App Store without passing a cost increase on to customers.

    Other than “no change”, I’ve only heard two possible solutions:

    • Special deals for the big guys. Amazon and other retailers could negotiate lower rates. But as Marco mentioned on “Build and Analyze”:5by5.tv/buildanal… the App Store treats large and small developers as equals. It’s a real strength that a 2-person game company can compete with Electronic Arts. I hope we never lose that.

    • Lower percentage for everyone. Not going to happen. Take an app like Twitterrific. I consider it a $5 app, but to the store it’s actually a free app with a $5 in-app upgrade. Lowering the in-app cut would encourage many previously paid apps to convert to free and pay less to Apple.

    This is why I believe the only option is for Apple to distinguish between in-app content and features. Content purchases, such as e-books or virtual game items, would be in one class of payment. Feature upgrades, such as unlocking core functionality in the app, would continue to be 30%, same as paid downloads.

    Is it confusing for developers? Is it totally subjective and up to the judgement of the review team? Yes. Welcome to the App Store.

    → 11:34 AM, Feb 10
  • Free 1-star reviews

    Before I released “Tweet Library”:www.riverfold.com/software/… I talked to everyone who would listen about the price. Several people suggested I go with a free app, but use in-app purchase to upgrade to the full version. Two apps that handle this well include “Twitterrific”:twitterrific.com and “SimpleNote”:simplenoteapp.com/. Countless games also take this approach.

    It’s the closest thing the App Store has to demos, but it comes at a cost: anyone can leave a 1-star “too expensive” review of your app without even upgrading to the full version. At that point they are not even rating the app they downloaded (a free, limited version that probably works just fine); they are simply commenting on a portion of the app they didn’t want to buy.

    There are two ways to give me feedback about Tweet Library:

    • Email support, post to Twitter, or write on your blog about the software. This is free.

    • Leave a review in the App Store. This is $9.99.

    I'm very comfortable with this model. The quality of feedback I get in email is extremely high, whether the customer has bought the app or not, and the App Store reviews aren't cluttered with pricing rants.

    → 7:29 AM, Oct 15
  • iTunes password caching

    “Mike Rohde racked up $190 in iTunes in-app purchases”:www.rohdesign.com/weblog/ar… without knowing it, blaming an app called “Fishies”:itunes.apple.com/us/app/fi… by PlayMesh for tricking his son into purchasing virtual items without a password prompt. He was obviously pretty upset — I would be too! — but calling it a “scam” probably goes too far. So what really happened?

    It is fairly well known that after the App Store prompts for your iTunes password, you can download more apps for a certain length of time (at least a few minutes) before it requires a password again. What seemed less clear is that this applies to in-app purchases as well.

    To be sure, I ran a test to confirm the behavior:

    • Download a new free app from the App Store (I downloaded the current number 1 iPhone app, Farm Story Summer).

    • Enter your password to confirm the download.

    • As soon as it finishes, go to another completely different app (in my case it was Iconfactory's Ramp Champ, which I had downloaded months ago).

    • Purchase an in-app virtual item.

    • It prompts for whether you want to buy the item (the standard Apple prompt), but without requiring a password.

    What must have happened to Mike is that he bought something, entered his password, and then handed the iPad over to his son. His son played the fish game and clicked a bunch of random stuff (likely got the Buy prompt), but because the whole concept of virtual currency is kind of confusing, and because it didn't ask for a password, the app happily let him make all the purchases.

    I doubt the developer of this app did anything wrong. A reasonable argument could be made that iTunes should either not cache passwords at all, or keep a separate cache for app downloads vs. in-app purchases, or maybe always prompt for a password on in-app purchases. My kids and other kids I know have also used this backdoor trick to sneak a couple app downloads, but usually it’s a few bucks, not $190. Consumable virtual items (that you can keep buying over and over) make this problem much worse.

    On “episode 60 of This Week In Startups”:thisweekin.com/thisweeki… Jason Calacanis interviewed ngmoco founder Neil Young about the mobile game business, focusing on the hit iPhone/iPad game “We Rule”:werule.ngmoco.com/. I was stunned to learn from the show that some individuals spend not only hundreds of dollars but up to $10,000 on in-app purchases in We Rule. Neil Young was happy to take their money, but something feels wrong here, like a gambling addiction gotten way out of hand. Or maybe just kids running up their dad’s credit card bill.

    → 11:21 AM, Jul 10
  • $10 iPad apps

    I’m fascinated with App Store pricing. There’s just so much interesting stuff going on:

    • 99-cent apps and the race to the bottom.

    • Users expecting apps to be cheaper because the device is smaller.

    • The high-end successes like OmniGraffle.

    • Sales and pricing gimmicks.

    • Whether apps can compete outside of the top 100.

    So when 37signals launched their first iPad app — Draft, for sketching mockups and quickly uploading them to Campfire — the first thing I wondered was: "how much?" The comments on their "launch blog post":[37signals.com/svn/posts...](http://37signals.com/svn/posts/2420-launch-draft-for-ipad) are a hilarious and sad mix of the usual cheapskates balanced with 37signals defenders. But the most amusing part is that at only $10, Draft is a bargain compared to Campfire itself, which has an entry-level paid plan of nearly $150/year.

    (I’m a big Campfire fan, actually. The best iPhone client for Campfire, Ember, has a permanent spot on “my home screen”:www.firstand20.com/homescree…)

    My first indie iPad app, a 3-4 week project that has stretched to 3-4 months, will also be $10. At that price it will be twice as expensive as its competition. I’m pricing it that way for three main reasons:

    • It's worth the price of two trips to Starbucks, because it takes the category in a new direction with features no one else is doing.

    • It's designed for people who are serious about this stuff, not an impulse buy, not for everyone.

    • It's a standalone app but includes an optional web complement, offered for free, but which will incur "real hosting costs":[www.heroku.com/.](http://www.heroku.com/.)

    Daniel Jalkut and I talked about this a bit on "Core Intuition 28":[www.coreint.org/2010/04/e...](http://www.coreint.org/2010/04/episode-28-the-ipad-super-episode/) — that it might be okay to overcharge a little for 1.0 rather than raise the price later, and that it should be possible to build a business on the iPad the same way many developers have on the Mac: not by looking for the big overnight hit but by steadily selling some number of copies every day and letting it spread by word of mouth.

    Marco Arment wrote about this as “App Store B”:www.marco.org/208454730 in October last year:

    "More of their customers notice and demand great design and polish. More sales come from people who have heard of your product first and seek it out by name. Many of these apps are priced above $0.99. These are unlikely to have giant bursts of sales, and hardly any will come close to matching the revenue of the high-profile success stories, but they have a much greater chance of building sustained, long-term income."

    We’re three months into the iPad, just passed 3 million devices sold, and not every app has dropped to near-free. I think $10 iPad apps in particular are going to remain pretty common.

    → 10:39 PM, Jun 23
  • New iPad hackers

    My first reaction when I started reading “The Kids Are All Right”:daringfireball.net/2010/04/k… on Daring Fireball was: Well, I had to disagree with a John Gruber essay eventually, might as well be this one. There was no developer program fee when I started building Mac apps! You could write whatever you wanted and share it with friends.

    But then I thought more about the $99 hurdle. What was I doing as a teenager and would the procedures Apple has in place now have stopped me? (For context, I’m 34.)

    I started programming for the Mac with THINK Pascal, a beautiful little development environment. Then I moved to C with Dave Mark’s book, which came with a C compiler on a floppy inside the back cover. Eventually I saved up and bought Symantec C++. Even at an educational discount these were expensive compared to the free Xcode of today.

    At that point I’m pretty heavily invested in the Mac, but the killer was the documentation. I’m sure I spent hundreds of dollars on “Inside Macintosh”:en.wikipedia.org/wiki/Insi… books. Our senior year in high school, my friends and I would meet at a restaurant before class for coffee and breakfast. I remember I’d get there early and sit in the booth with one of my oversized volumes of Inside Mac, taking in too much caffeine for my own good while I devoured every page, even the advanced topics that were still over my head.

    I lived and breathed this stuff pretty heavily for a few years. To imagine letting a $99 iPhone dev fee and some locked-down APIs prevent me from building apps is laughable. Great computers inspire people to build new software. That’s how it was when I got my first Mac, and I’m sure it’s that way for the new generation of young iPhone and iPad tinkerers.

    One day I hope the App Store will be more open. But it is what it is. I’ll point out where I think Apple can improve, and then I’ll build and ship anyway. It makes no sense to sit around and complain on my blog about the good old days while some kid half my age is taking his or her idea all the way to the top of the App Store and owning the platform of the future.

    → 2:13 PM, Apr 16
  • Quiet rejections, no big news

    It appears I was too optimistic “in my last post”:www.manton.org/2010/03/2… about the App Store getting better.

    The iPhone version of Snowtape, in development for months, “was rejected”:www.vemedio.com/blog/post… because it could let users record and share audio from the internet:

    "His sole words were, that there are lots of things missing in the SDK agreement and that they can not foresee any circumstance that leads to a denial of an app. That's right! We did not violate any paragraph of the SDK, yet they forbid us distributing our app."

    The developer removed the ability to transfer audio files off the phone and then Apple let the app through.

    Then there’s this post “on the developer forums”:devforums.apple.com/message/1… about an iPad app rejection because they recreated a UI innovation from the new Photos app. Apple said:

    "The application uses a tap and a pinch to expand feature that is present in Apple iPad Applications. This action is associated solely with Apple applications, and we kindly ask that you update your app appropriately."

    I’ve been doing a bunch of iPhone and iPad development this week. The more I work with it, the more I love the platform. But it just takes a couple rejections to sour the whole experience.

    And yes, I realize I’m posting this on one of the most exciting days in the history of the App Store. The first round of iPad apps hitting the store today look fantastic.

    → 2:23 PM, Apr 1
  • iPad ships next week

    With the iPad set to ship in just a week and a half, I’ve been quietly reshuffling some of my projects around it. I’ve written critically of the iPhone and App Store a couple times, such as how the iPhone is a gold rush distraction that “doesn’t need me”:www.manton.org/2009/09/i… I also stand by “earlier opinions”:www.manton.org/2009/11/t… of how unfixable the App Store is, especially now when it’s obvious that any effort trying to convince Apple to open the store is completely wasted. They never will.

    But I really like what I’ve seen of the iPad platform so far and I think it represents a big shift for everyday computing in a way that a cell phone can’t. So I renewed my membership in the iPhone developer program.

    I’m working on 2 apps for the iPad. The first is just a minor iPad refresh of an existing iPhone app at VitalSource called “Bookshelf Noteview”:itunes.apple.com/us/app/bo… (iTunes link). It’s for reading notes and highlights synced from our e-book platform.

    I’m not ready to announce the next app yet, but it’s a personal project which I had originally written for the Mac over a year ago. I shelved it at the time because I wasn’t sure there was demand, the backend web services weren’t mature, and I wasn’t ready to take it to completion. For the iPad though, it might be perfect.

    And that’s ultimately where I see the most interesting potential for the iPad. New middle-ground apps that we haven’t even thought of yet, not ports from another platform. Apps that would feel small or distracting or wrong on the Mac, yet equally oversized for a relatively underpowered iPhone. Maybe the never-tested-on-a-real-device launch day apps will be buggy and the overall quality low, but I can’t wait to try them anyway.

    → 5:48 AM, Mar 23
  • iPad

    My quote from “Cult of Mac”:www.cultofmac.com/i-have-be… sums up my feelings about the iPad from a business perspective:

    "I was so annoyed with the closed nature of the App Store that I stopped developing for the iPhone. The iPad will still have those frustrations, but the large screen opens up a whole new class of applications. It's impossible to resist."

    Will there be a “Clipstart”:www.riverfold.com/software/… for iPad? I hope so. This platform will be the future for plenty of customers. Apple lived up to the hype not because of the hardware or distribution or anything entirely revolutionary, but because of the software. Splitviews and popovers. Keynote and Pages. These apps are just as competent as their desktop versions.

    Daniel and I talked about the iPad for most of “Core Intuition 26”:www.coreint.org/2010/02/e…

    → 9:54 AM, Feb 8
  • The only 2 fixes for the iPhone platform

    I let my iPhone developer account expire last week. Even though I had already stopped development on my iPhone projects, officially letting go of even the temptation to build for the iPhone platform has really helped me focus.

    The Rogue Amoeba rejection for Airfoil Speakers Touch has been covered on Twitter and at Daring Fireball, but I think it’s easy to get distracted by legal technicalities and not the heart of the matter: as long as Apple is the gatekeeper, there will be bad decisions and apps that deserve to be approved will be rejected instead. For this reason the App Store cannot be fixed with incremental improvements.

    There are only two possible solutions:

    • Accept all applications. Joe Hewitt, the developer of the Facebook application who this week also quit the App Store, has written well on this solution.
    • Allow applications to be installed on the phone without being listed in the App Store. Both Android and the Palm Pre support this model.

    There is no third or fourth solution. There is no compromise or small improvement to the review process. Better transparency or tiered support options won’t help either. Without either of the above two changes, rejections will continue because in a subjective review process there will always be bad judgement calls. Some percentage of indie developers will abandon the iPhone either because the risk is too great or based on principle alone.

    Let me take the second one (allow applications to be installed without being listed) because it plays directly to this Rogue Amoeba rejection. Rogue Amoeba is one of my favorite Mac companies, and Daniel Jalkut and I record Core Intuition using their Audio Hijack Pro app. It’s universally regarded as great software.

    It might surprise you to find out that Audio Hijack Pro is not listed in the Apple Downloads site, though other Rogue Amoeba products such as Fission, Nicecast, and Airfoil are. I’m not sure Rogue Amoeba has ever spoken on the record about this, but Apple apparently doesn’t like the app and won’t list it. Maybe because you can use it to record copyrighted music? Who knows.

    But it doesn’t matter because being rejected from Apple Downloads doesn’t mean you can’t make Mac software! It just means you have to market the software yourself. Rogue Amoeba has to work extra hard to get the word out about the app, but their business won’t fail just because Apple doesn’t give it their blessing.

    This is so important for a small company. I want my software to fail because it sucks, or is buggy, or doesn’t have the right features, not because Apple can shut me down over a minor difference of opinion.

    There are a lot of well-intentioned suggestions for improving the App Store, but the result will always be the same until we acknowledge the root problem. The only fix is for Apple to remove itself as gatekeeper, or let us route around them.

    → 1:07 PM, Nov 13
  • Crippled iPhone LGPL

    I mentioned on the “latest Core Intuition”:www.coreint.org/2009/08/e… that I no longer have any plans to release my own iPhone software. While that decision is mostly based on my unwillingness to give Apple so much control over my business, and frustrations with the App Store process in particular, there are a handful of technical reasons why iPhone development is not a good fit for me. Here’s one: open source.

    “Daniel Jalkut’s essay on the GPL”:www.red-sweater.com/blog/825/… hits all the points about how the GPL can hurt developers by discouraging commercial participation. I’ve used LGPL projects in both “Clipstart”:www.riverfold.com/software/… and “Wii Transfer”:www.riverfold.com/software/… and I am careful to use them correctly. But iPhone development presents an interesting problem.

    Can’t run command line tools. Separating the GPL code into a command line tool that is inside your application bundle is a common way to get around licensing issues. This is not allowed in the iPhone SDK.

    Can’t replace dynamic libraries. The LGPL says that you can also link to libraries at runtime, but the catch is that the user must be able to replace an LGPL library with a newer version of their choosing. There is no way for normal users to do this on the iPhone.

    Can’t use private frameworks. Oh, that point above about dynamic libraries? Actually it’s a moot point because Apple requires everything to be statically linked anyway. So you are blocked at every pass; you can’t ship an app that loads code dynamically even if the user could touch it.

    The only solution I’ve seen so far is to release a special version of your Xcode project, with most of your application split into compiled libraries instead of source code, and allow developers with the iPhone SDK to relink your application with a different copy of whatever LGPL code you used. I stopped researching this when I put my own iPhone projects on hold, though. It’s just another example of how the closed nature of the platform creates an unnecessary burden in the software development process.

    → 3:04 PM, Sep 5
  • $999 hope

    “Huge post from Craig Hockenberry”:furbo.org/2009/07/1… on the App Store. Lots of good points. I especially like the insight comparing it to the music store, the need for upgrade revenue, and ideas for improving discoverability.

    Where I have a problem is at the $999.

    Not for support or early access to new versions of the iPhone OS, that’s fine. ADC Select and Premier members are used to paying for non-essential bonuses. The issue is whether we should pay extra to work around a problem that Apple has created for themselves and developers.

    And I totally respect that Craig is just throwing out a bunch of possible solutions, hoping that something will stick, that Apple will start to pay attention and draw inspiration from the community. “As he said on Twitter”:twitter.com/chockenbe… “I just want to put money where my mouth is.” I think the $999 figure speaks to just how painful this process has become. Luckily developers are also natural problem-solvers, forever hopeful even when desperate.

    But just as the $99 fee to become an iPhone developer didn’t filter out the junk apps and unserious developers new to the platform, neither will throwing more money at the problem make it go away. The gold rush is still on, and we should expect app submissions to only accelerate.

    Most importantly, let’s take a step back and remember: it was Apple’s choice to build a closed system, one in which they alone could approve and deny apps. The idea that we should pay extra because they underestimated how much work it would be to approve thousands of apps really bothers me. It would be punishing developers for Apple’s own failure.

    “Colin Barrett pointed out”:twitter.com/cbarrett/… that Apple loses money on free apps, when you consider server overhead and review staff. I find it difficult to believe that Apple is doing anything except raking in the cash from the App Store. After all, they are used to giving away bandwidth for a number of products: Safari and QuickTime downloads, iLife and iWork software updates, not to mention updates to Mac OS X itself.

    From an article back in May, “Techcrunch also assumes”:www.techcrunch.com/2009/05/1… that Apple is doing quite well off the App Store:

    "$1 million a day means that Apple would be making $300,000 a day (its 30% cut). Extrapolated out over 10 months (the approximate age of the App Store), that would be about $90 million."

    I want to believe that there is a solution to this. A quick reading of “AppShopper.com”:www.appshopper.com shows that on some days up to 100-200 apps go live on the store. That’s a lot of apps. But Apple is a large company, and they’ve surely dealt with more difficult staffing problems than hiring some people who know how to use an iPhone.

    Other than a handful of exceptions in the jailbreak community, iPhone developers are playing by the rules Apple created. The burden is on Apple to deliver fast reviews, and it’s something that all developers deserve, not just a select few with extra cash to burn.

    → 12:41 AM, Jul 14
  • Clipstart for iPhone?

    You know it has been a good conference when you come back inspired, with ideas and tools to build new things. No surprise that WWDC was like that for me, as it is pretty much every year.

    Even before the keynote was over I was getting questions — which continued all week — about whether I had iPhone plans. At the very least, Clipstart 1.1 needs to be able to import videos off of the 3GS. “That’s in beta now”:www.riverfold.com/forums/to… But what about a native phone app?

    I’ve convinced myself over the last couple weeks, after listening to what people are doing with their phones and evaluating the existing applications in the App Store, that Clipstart for iPhone would be a very useful app. Video on the 3GS is a big deal. Eventually I can see a new top-level Video category in the App Store, and whoever is in that list is going to do very well.

    “Neven Mrgan”:mrgan.tumblr.com/post/1240… sums up the urgency:

    "I'm sure Phil Schiller's prediction of iPhone 3GS quickly becoming the most popular video-capable phone — if not the most popular consumer video device period — is right on the money. A message for those working on apps that help us shoot, edit, organize, and share quick, casual video clips: get ready to get busy."

    I’ll admit that after WWDC I panicked, thinking for a moment that I had to deliver Clipstart for iPhone immediately, and drop everything I’m doing to make that happen. I no longer believe that. The Mac version of Clipstart has a lot of potential and I can’t get too distracted from following up on that. But at the same time I will be expanding what I do on the phone, so we’ll see where that goes.

    → 11:01 AM, Jun 29
  • App Store new version UI

    Centralized app update notifications on the iPhone were a great idea, right? Turns out, maybe not. My App Store icon has a “26” badge on it. I have no idea which apps have a new version available until I click and scroll through the list, or use iTunes. The reality is that at least 3/4 of them are for apps I downloaded but don’t use very often. I now have to set aside some time to weed through this list of apps.

    I’d much rather get a friendly reminder of a new version when I launch the app itself — maybe even outside the app’s control, near the top of the screen just like when a phone call is in the background. There are a few apps I use every day that were updated weeks ago, but I continued to use an old version because the notification was lost in the noise of dozens of other junk apps.

    → 7:11 PM, Jan 19
  • Buzz on software entrepreneurship

    “Buzz Andersen responds”:log.scifihifi.com/post/4759… to some of Mike Lee’s recent blog posts:

    "We're living in the 'anyone can play guitar' era of software entrepreneurship. Because of the confluence of increasingly accessible developer tools and the Internet, it's now reasonable to think that one or two talented people, with little to no investment, can make anything from a good living to a fortune by bringing their idea to life. What kills me about the outmoded Silicon Valley gold rush mentality that I feel has entered the Mac developer community for the first time because of the iPhone is how much it fundamentally ignores the significance of Apple's App Store as a field leveler."

    Although I was at first disappointed that I had no time (either at VitalSource or for my own projects) to have an iPhone app at launch, as the weeks and months pass since the App Store opened I find myself less and less sure about what the App Store market actually looks like. Everything is changing very quickly. While there is no doubt a huge opportunity in iPhone development — and with another 30-40 million iPhones hitting next year, each of those new customers will have their own impulse buys and novelty purchases, to say nothing of the real apps that people need on their phone — at the same time I wonder when iPhone development will be as mature and stable as the Mac software market is.

    This isn’t a direct comment on what Buzz is saying. His blog and comments on “Mike’s post”:www.atomicwang.org/motherfuc… are right-on as usual.

    → 8:42 AM, Aug 27
  • RSS
  • JSON Feed
  • Surprise me!
  • Tweets