Tag Archives: wwdc

Apple podcast spec changes

At WWDC last week, Apple introduced changes to their RSS feed extension for podcasts. Before reviewing the session, I was worried that Apple would be moving to Apple News Format instead of RSS. That would’ve been a major setback for the open web, since Apple News Format is such an app-specific, closed format, controlled by a single company. Luckily the actual changes Apple introduced are pretty minor and shouldn’t upset the status quo much.

There are 2 sets of changes: support for supplementary episode types, like bonus content; and metadata for show seasons, likely influenced by popular shows like Serial, where people new to podcasts might be confused about where to start listening. There are a few new tags for these types of shows under the itunes RSS namespace.

Episode type is the simplest change. It looks like
<itunes:episodeType>full</itunes:episodeType>
and can have values “full, “trailer”, or “bonus”.

For seasons, the episode number and season number can be split into separate elements. It’s compatible with the traditional RSS title, so there’s little downside except extra clutter in your RSS feed. Here’s an example:

<channel>
  <itunes:type>serial</itunes:type> <!-- or "episodic" -->
  ...

  <item>
    <title>S01 Episode 01: The First Episode</title>
    <itunes:title>The First Episode</itunes:title>
    <itunes:episode>1</itunes:episode>
    <itunes:season>1</itunes:season>
    ...
  </item>

</channel>

Jason Snell’s first reaction to these changes was positive:

I’m excited by these changes because, yes, some of my podcasts are seasonal and are best consumed from the first episode onward. I’ll be adjusting my own podcast feeds to take advantage of Apple’s extensions as soon as it makes sense to do so.

Ben Thompson covers the extensions briefly and then focuses his weekly article on analytics and podcast advertising:

The new extensions are a nice addition, and a way in which Apple can enhance the user experience to the benefit of everyone. As you might expect, though, I’m particularly interested in the news about analytics. Problem solved, right? Or is it problem caused?

After reading Ben’s take, I don’t think these changes are significant enough to have much effect right away. That should be a relief to all of us who love podcasts and don’t want a shake-up.

When designing JSON Feed, we resisted adding everything that Apple Podcasts needs to the official spec. Now that more podcast tools have adopted JSON Feed, I expect there to be a discussion among developers about the best path forward for podcast-specific extensions in JSON Feed. That discussion should now include support for show seasons, too.

San Jose is less crowded

On Core Intuition last week, I said San Jose was “more confined” than San Francisco. I meant that mostly as a good thing, although I do miss the open spaces in San Francisco: the parks and incredible views near the water. Gus Mueller has a post about how San Jose felt closer together and less crowded:

In San Jose you had a clear view of the sidewalks and you generally knew who was a developer and who was a local. And because it wasn’t so crowded, you ran into people all the time. You didn’t have to organize meetups, you just kind of went out and you knew you’d run into someone to hang with.

Gus was also a guest with Marco Arment on The Run Loop podcast. They talked a lot about the different feel of WWDC in San Jose. Seems a universal opinion that San Jose is a good fit.

10.5-inch iPad Pro resolution

Federico Viticci reviews the new 10.5-inch iPad Pro at MacStories. On the screen size:

While some had assumed that Apple would take the same 2732 x 2048 display of the 12.9” iPad Pro and condense it to a smaller size, the company has introduced a new resolution in the iOS device matrix – a decision, I think, made to hit 264ppi on a 10.5” panel while retaining UI elements that are large and comfortable to tap. Cramming the large iPad’s display in this model might have resulted in a richer multitasking experience at an even smaller scale, but I believe touch usability would have suffered.

I assumed until reading Federico’s review that when my 12.9-inch iPad Pro was ready for an upgrade, I’d downsize to the new 10.5-inch. That no longer seems like a good choice. While my MacBook Pro is getting repaired this week, I’m using the 12.9 as my exclusive computer. The extra resolution in split view is really great. I don’t think I’d want to give that up.

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.

Siri’s slow pace

It’s WWDC week. I’m back home after a short week in San Jose. Monday’s keynote was a big event, with great news for Mac and iPad users, but I keep coming back to the most surprising “miss” in all of the announcements, and the one thing that I thought was surely a lock for the conference: SiriKit.

When I was on The Talk Show last week with Brent Simmons, John Gruber wrapped up the episode by asking about expectations for WWDC. I’m a big fan of the Amazon Echo, and I think Siri is behind in responsiveness and extensibility. I predicted at least 20 new domains and intents for SiriKit, if not a more open architecture that could grow into as big a platform as Alexa’s thousands of skills.

This week should’ve been a great one for Siri. Instead, we got not the hoped for 20 new domains but literally only 2, for taking notes and managing to-do lists. HomePod will have no support for apps at all, and it will initially ship only into a few English-speaking countries, erasing the traditional advantage Siri had over Alexa for localization.

There are good ideas in SiriKit. I’m excited about experimenting with creating “notes” in my app, and I like that in session 214 and session 228 they highlighted some of the new tweaks such as alternative app names and vocabulary. But there has to be more. Siri deserves several sessions at WWDC and much more attention from Apple.

Voice assistants represent the first real change in years to how we interact with computers, perhaps as important as the original graphical user interface. The company that created the Knowledge Navigator concept video should be firmly in the lead today. A year from now, at WWDC 2018, the lack of significant improvements to Siri will have stretched to 2 years, and that delay is going to look like a mistake even to Siri’s most vocal defenders.

Core Intuition 285 and WWDC

We posted a new Core Intuition this week about WWDC. From the show notes:

Daniel and Manton catch upon WWDC, and Manton’s ailing MacBook Pro. They talk about new hardware announcements and react to highlights from the Keynote. Manton laments Apple’s continued, slow progress with SiriKit, and Daniel is frustrated that HomePod is not a Wifi hub. Finally, they talk about iOS Drag and Drop and compare it with Apple’s traditional tendency to move slowly but surely into the future.

After we recorded, I watched the first episode of Planet of the Apps, and started to get into more of the conference session videos. We’ll be following up next week on more from WWDC.

Jean MacDonald on The Run Loop

Jean MacDonald was on the latest episode of Collin Donnell’s new podcast The Run Loop. They talk about App Camp For Girls, Micro.blog, Portland, and more, with a preview of Jean’s talk at CocoaConf Next Door. It’s a great episode to queue up before WWDC.

And a related reminder: we’re having an informal meetup on Tuesday at lunch for anyone interested in independent microblogging. Sign up for more information here. Hope you can make it and say hi to me and Jean.

WWDC moves back to San Jose

I have a tradition when I go to San Francisco for WWDC. I arrive early on Sunday before the conference, drop my bags at the hotel, and take a cab to the Presidio. The weather is usually beautiful. I visit the Walt Disney Family Museum, maybe sit in the grass with a coffee, then go for a walk to take in views of the Golden Gate Bridge.

I’ve done this the last handful of years. It’s always a perfect reset to whatever stress was happening with my own coding projects and business. You can find blog posts and tweets from past years.

I attended WWDC in San Jose a few times. Moving WWDC back there will probably end up being fine. If you’re at the convention center, or hanging out with attendees at a restaurant, or taking a break to work at a coffee shop around the corner, or even going to a party — many cities will suffice for that. I’m sure the conference will be great.

I’ll still miss San Francisco. I know it’s not a perfect city. But it’s historic and unique. That’s why I recorded a podcast episode about it over 10 years ago, and I’ve learned much more since. I always get something out of the trip.

Kickstarter, first week wrap-up

One week down. The launch on Kickstarter is going great. It’s fantastic to see everyone’s reaction to the project. More than ever, I’m convinced that the time is right for this.

I wanted to highlight a few posts and links. I was a little caught off guard by activity on the first day, so I’ve yet to really reach out to press contacts who might want to write about Micro.blog. I’ve been focused on replying to questions about the service and book.

John Voorhees wrote for MacStories about the Kickstarter:

Micro.blog has a lot in common with social networks like Twitter, such as replies and favorites, but with an important difference. Instead of locking users into a proprietary system owned by someone else, the content created by individuals is owned and controlled by them. As part of the Micro.blog service, Reece is also building publishing tools with Markdown support, including a native iPhone app, to help people get started with microblogging.

John had interviewed me at WWDC last year about what I was up to. While I didn’t have the name Micro.blog yet back then, I was actively working on the service and you can hear many of the same themes from back in June as I’m saying today.

I thought Marco Arment summed up the urgency well:

We’ve all been pouring a lot more of our writing and attention into Twitter and Facebook than the rest of the web, and the diversity and decentralization of the web has suffered greatly. Far too much power now rests in far too few hands, and we’re starting to suffer tremendous consequences.

Reaction from the WordPress community has also been encouraging. I knew I wanted to reach WordPress fans, because Micro.blog works great with WordPress, but I’m not as plugged into that community. I was excited to see Matt Mullenweg tweet a link to it. And WP Tavern did an excellent write-up, mixing interview questions with previous posts of mine:

During his 14 years of blogging and 10 years of using Twitter, Reece became an advocate for the open web. He said he used to be excited about Twitter and built apps for the platform but grew disillusioned at their approach to locking down the API.

I’m thankful for local articles as well, such as this story from Silicon Hills News by Laura Lorek. Laura is just in the last day of her own Kickstarter campaign for a podcast companion to the Austin news site.

Not to mention blog posts from Brent Simmons, Gus Mueller, Becky Hansmeyer, Ben Brooks, Dave Peck, Chris Aldrich, John Johnston, and the hundreds of tweets and links I’ve seen over the last week. It’s really special to see it spread so far. Thank you again to everyone who has linked to the project.

Now that I’ve had a week to reflect on the campaign, and listen to feedback, I’m starting to form a much clearer picture of how the rest of the month needs to play out. This is the kind of opportunity that doesn’t come around very often. I’m looking forward for the work ahead.

Tagging WWDC microblog posts

I didn’t post as much as I hoped to during WWDC 2016 — just a couple full posts related to the conference, a half dozen microblog posts, and one photo. But nevertheless I wanted to collect them together since I didn’t have a full wrap-up post like last year.

One of the advantages to hosting my own short posts — and only cross-posting to Twitter as an afterthought, not the primary location — is that I can easily tag all the posts in a series. This worked out really well while visiting coffee shops earlier this year.

For WWDC, I’ve used the tag #wwdc2016. I probably won’t go back to tag previous conferences, but I’ll use this format going forward for attending events where I publish a series of microblog posts and photos.

Podcast thoughts on WWDC

I’m back from San Francisco, catching up on everything I missed while traveling. I recorded a few podcast episodes during WWDC week, both my own and an interview.

On Core Intuition, Daniel and I talked right after the keynote about the morning’s announcements. From the show notes:

Manton and Daniel react to the 2016 WWDC keynote. […] iMessage and Siri extensibility, Continuity improvements, Apple Pay for the web, Apple’s keynote diversity, and more.

In the middle of the week, I talked with John Voorhees of MacStories about WWDC news but also a lot about microblogging. It may be the most I’ve shared about my latest project, all in one place.

Yesterday, I recorded a short episode of Timetable. I wanted to capture what the trip to San Francisco each year means to me, outside of the conference itself. I find the week a good opportunity to reset and think about where my focus should be across my projects.

Only taking my iPad Pro to WWDC

I’ll be in San Francisco for WWDC, although as usual in recent years I won’t be staying all week. While out there I’ll be attending AltConf and other events, recording a podcast or two, and catching up on some writing.

I probably should take my MacBook Pro to code on projects, but I never have time. And I’ve been working so much lately, I probably need a break from Xcode for a few days. So I’m going to travel light this time and only take my iPad Pro with me.

I used my iPad Pro often when working from coffee shops and libraries earlier this year. I think I have a pretty good sense of what I’m productive with on it. iPhone and Mac app coding is out, but email, chat, writing blog posts, and even light web site maintenance are all fine, and those are the kind of things I do while traveling.

That leaves podcast recording as the only question mark, but actually I’ve recorded every episode of Timetable using my iPhone specifically so that I could get used to recording away from my office. I wrote a few months ago about my microphone for Timetable. I’ll do the same thing when Daniel and I record our WWDC thoughts after the keynote, with editing on the iPad Pro.

I’m excited about the conference. I’m looking forward to catching up with folks, the news from Apple, and — because I won’t even have my laptop — a bit of a break from the stress of thinking I should be programming.

Core Intuition’s 8 years and overselling WWDC

It’s 2 weeks before WWDC, which means it was also 8 years ago that we published the first episode of Core Intuition. At WWDC that year, Apple showed off iPhone OS 2.0, MobileMe, and the iPhone 3G. The yearly cycle of improvements to the OS and hardware don’t look much different today, but Apple keeps rolling, and so the total changes since 2008 are massive.

For as many years as I’ve been out to San Francisco for WWDC (and to San Jose before then), each year I have fewer expectations for the conference itself. Some years I don’t even bother guessing or dreaming about new features — I have no pressing needs, no critical missing APIs, no questions to ask Apple engineers in the labs — and I’m happily surprised by whatever Apple gives us.

This year is a little different. It’s the first year that I can remember since the Mac OS X 10.0 and 10.1 releases where an Apple platform needed significant performance improvements to be usable for anyone except early adopters. The first couple versions of Apple Watch were ambitious on features, but now it’s time to do the less glamorous work of making the platform fast. I hope watchOS 3.0 will be the same kind of milestone that Mac OS X 10.2 was in that regard. (And like Mac OS X, I hope it can be done mostly in new software.)

Back to WWDC the conference. I’m still thinking about the interesting venue change for Monday to the Bill Graham Civic Auditorium.

In the discussion on Core Intuition 229 last month, I kept coming back to the idea that this change has to be about growing the conference to allow more developers. Since more people show up on Monday (press and business folks, for example, who have less interest in the technical sessions or labs), you could have a bigger space on Monday and then oversell the conference as a whole, knowing that some ticket holders wouldn’t be around later in the week back at Moscone West.

Maybe that creates more problems than it solves because of packed rooms and long lines to get into sessions, though. Now that I’ve had a while to think about it, it seems unlikely that Apple would risk making the conference worse just to squeeze in another 500 developers.

Could there be some creative layouts in Moscone West that Apple hasn’t tried yet? There are so many downsides to changing the venue that I want to believe it’s part of addressing the biggest issue with the conference: most people don’t win the ticket lottery.

There’s still the problem of hotels. Linking to my post about not giving up on WWDC, John Gruber singled out Airbnb as a bad solution, since there just aren’t that many rooms available. That’s true. And even worse, potential last-minute cancellations make Airbnb less reliable. Where I said Airbnb, I should have just said “cheaper hotel”.

(Alex Cash also has tips for saving money at WWDC. Casey Liss has a good post about rising hotel prices.)

Nevertheless, I know some developers are using Airbnb this year, and I’d like to try it next year for a change of pace and scenery away from the conference. With the convenience of Uber, the risk of settling for a place farther away seems low.

And finally, I’ve enjoyed many recent podcasts about WWDC. Two highlights: Under the Radar episode 24, where Marco Arment and David Smith share their thoughts on whether to attend the conference; and Thoroughly Considered 12, about not just WWDC but the value of attending or exhibiting at conferences as a company.

Don’t give up on WWDC

There’s a nice sale going on across several smaller, regional developer conferences right now. I think any of these conferences would be a great experience, so if you’re considering one you could save $100 by acting now.

I wanted to comment on something Joe Cieplinski said about WWDC while linking to this promotion:

Folks say that WWDC is the one time where everyone in our community can get together, but frankly, the price of hotels in San Francisco has made that statement a bit disingenuous. Many—if not most—of us can’t afford to make it to this party, so maybe this is no longer the party for “everyone.”

Curtis Herbert also echoed some of these themes in a post:

While it’s a shame to end the WWDC tradition, it makes sense to follow all the other technical communities out there and rely on smaller, more accessible and distributed, community-run conferences throughout the year. It’s a sign that our community growing up and leaving the nest. One city can’t hold us all anymore.

I think it’s possible to go out to WWDC without spending a fortune. You can attend AltConf, find an Airbnb room for $150/night, and stay a few days instead of all week. I downgraded my expectations for WWDC and booked a cheaper hotel room a couple of months ago. It’s about how much you want to be there.

In fact, I’d still argue that it’s less expensive to “attend” WWDC now because it has been proven how much you can get out of AltConf and other events without the $1600 conference ticket. When I went to my first WWDC back when it was held in San Jose (and the same could be said for the early years in San Francisco), hotels and flights were cheaper but it was pointless to attend without a ticket.

I can’t go to every conference. This year I’ve picked 2: WWDC (probably without a ticket) and Release Notes (in September). I wrote about Release Notes last year and highly recommend it again.

But I stand by the opinion that WWDC is worth preserving as the best place for everyone to go — with or without a ticket, with or without a fancy hotel room — because there’s room for thousands of more developers than at a small conference. I hope that Apple’s change of venue for the keynote and Monday sessions means they are trying to expand the conference to even more developers.

I’m so excited about Monday’s new venue that I’m actually thinking about trying to get a ticket in the lottery, to experience what it’s like and what it means for the conference going forward. The main thing holding me back is that it seems wasteful if I’m not staying through Friday, when another developer — maybe someone who hasn’t attended before — could get that ticket instead.

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.

Floyd Norman’s sketch of Steve Jobs

Disney Legend Floyd Norman has an excellent blog, usually recollecting on the early days of the Walt Disney studio, or more recent animation ventures. This week he wrote about Steve Jobs:

“An animated motion picture goes through many iterations while in production and screenings were held on a regular basis. I honestly doubt Steve was trying to curry favor with Disney. Being a shrewd negotiator Jobs didn’t need any extra help to get his way. I think he brought Apple gifts purely as a gesture of friendliness. After all, shouldn’t everybody have a Mac Laptop?”

The post includes a fantastic sketch of Steve. My only regret from WWDC this year is that I didn’t have a ticket to see Floyd speak at the conference. Although Apple doesn’t usually release the video of lunchtime sessions, I very much hope it was filmed and will show up on YouTube or Vimeo one day.

More quick blogging workflows

I had a great conversion with Seth Clifford one night at WWDC, about writing and blogging. We all want to get better at writing and posting more frequently. As I mentioned in yesterday’s post, the best way to improve anything is to do more of it, more often.

I believe there are two important facets to microblogging. The first is the timeline experience: a reverse-chronological list of posts from your friends, like you see on Twitter. The second is that posting should be effortless: if there’s less friction between your idea and publishing it, you’ll write more often. So a big part of posting regularly is just having a system that makes it easy.

Seth updated his iOS blogging workflow by using Drafts and WordPress’s email-to-blog feature. As a nice bonus, he gets Markdown files of each post saved to Dropbox:

“Drafts allows you to send email as an action. WordPress allows you to post into the system via email. Using a combination of the action and the Jetpack plugin’s email functionality, I can go from idea to published in seconds, without touching the WP iOS app (which continues to get better, but still isn’t fast) and get my local copy stored away.”

Also this week, Ben Brooks has switched his core Twitter posting to go through WordPress. He has a standalone microblog at benb.me where the posts live. They go out to Twitter automatically via IFTTT. Posting to a blog first and then Twitter second seems like a simple idea, but it is extremely powerful. Years from now you end up with an archive of all your short-form writing at your own domain. Not as an afterthought, but as the default.

The great thing about blogging is there’s no one correct way to do this stuff. I’m really happy to see these solutions from Seth and Ben, and I know other folks are working on similar workflows.

iOS 9 search

Federico Viticci has a comprehensive write-up about Apple’s approach to search in iOS 9, including comments from developers. On local app search:

“With local app search, iOS 9 can build an index of content, app features, and activities that users may want to get back to with a search query. Built like a database and already in use by Apple apps such as Mail and Reminders, CoreSpotlight will provide low level access to the index of an iOS device, making it easy to organize and retrieve content users have previously seen, created, or curated.”

I’ve been slowly going through WWDC session videos, but haven’t cracked open the documentation for search yet. Sounds like an important new API for any app that has user documents.

Apple News and RSS

Daniel Jalkut has an optimistic take on Apple News. He doesn’t think it is comparable to centralized publishing systems like Twitter or Medium for one important reason:

“Because the content doesn’t live on Apple’s servers. This is a key distinction in my mind. Apple’s News App serves primarily not as a source of information, but as an amplifier of it.”

Any technology that invokes “amplifier” in a review is something I want to pay attention to. I used the same word in the closing paragraph of my pitch for App.net. That service is fading away now, of course, but it’s just another reminder that even the most well-intentioned platforms are dangerous if they distract us from controlling our own content and hosting it at a custom domain.

WWDC 2015, basketball, and cartoons

Throughout the week I posted about WWDC to my microblog, but I thought I’d write a longer post with the week’s narrative. It’s useful to have these to refer to in the future when all the WWDCs blur together and I’ve forgotten which event was which. Where it adds any details I’ll link to a few of the shorter posts.

So let’s go back to Sunday morning a week ago when I arrived in San Francisco, ticketless but ready to learn and meet up with friends. What a great day. First burritos and coffee in the Mission, then to Oakland for the NBA finals, game 2. I had signed up on the Golden State Warriors mailing list a couple weeks earlier to get in on the pre-sale tickets. Excepting the nearby San Antonio Spurs, I’m almost never going to just coincidentally be in the same city as an NBA finals game. I couldn’t let that chance slip by.

Golden State Warriors

And it was an amazing game. Outwardly I was rooting for the Warriors — high fives to fans when the team came back to force overtime, wearing my new yellow shirt they gave everyone at the game. But inwardly I was also marveling at LeBron’s dominance and happy to see the series tied up. I want to see this thing go to 7 games.

Monday was the keynote and later the Cartoon Art Museum / NeXT fundraiser, with beautiful art on the wall from one of my favorite films this year, Song of the Sea. Tuesday I tried to catch up on some code at Sightglass Coffee, watch sessions at WeWork, and installed the iOS 9 beta on my retina iPad Mini. In the evening on this day and others there were parties, though I only attended a few.

The Talk Show

The Talk Show live with guest Phil Schiller was a great surprise. I’m so happy for John and his success. Developers who have only known Daring Fireball after it was already fairly popular may need this important reminder: John Gruber started a dozen years ago with a blog that no one read, just like the rest of us, and this week he conducted the best interview of a senior Apple executive I’ve ever seen. If you think it’s enough to just throw random quips to Twitter, it’s not enough. Blogging is still the best way to build an audience. (Don’t miss Marco’s post about the event and what it means for the new Apple.)

I have very little to complain to Apple about this year. Maybe the keynote was a little long, but the topics they hit and the new user features and APIs were exactly right. I’ve got Mac OS X 10.11 El Capitan installed and will require it for my next Mac app.

Golden State Bridge

Toward the middle of the week I wasn’t feeling particularly great — not sick, but not really upbeat enough to get excited about new APIs. I escaped the city for the afternoon on Wednesday, visiting the Walt Disney Family Museum and then walking down to Crissy Field toward the Golden Gate Bridge. I stretched my arms out wide to catch the wind and felt refreshed in a way that the stagnant weather back in Austin this time of year can’t hope to provide. I remember this tweet from 2012 and it’s always true again, year after year.

Thursday morning I caught a session at AltConf before heading to the airport. Flights were delayed out of SFO because of fog, so it was 3 hours waiting in San Francisco, and another 3 hours waiting in Phoenix after a missed connection. But it’s all good. WWDC was a little weird for me — not because of anything Apple did, just because I was a little wistful, and distracted by email and non-WWDC happenings too.

Nevertheless I’m inspired by the week. The success of both AltConf and now Layers, not to mention all the other smaller events and keynote watch parties, point to a very strong WWDC for years to come.