Mike Isaac and Quentin Hardy, reporting for The New York Times:

Facebook acquired Parse, a toolkit and support system for mobile developers, in 2013. At the time, the social network’s ambitions were high: Parse would be Facebook’s way into one day harnessing developers to become a true cloud business, competing alongside the likes of Amazon, Google and Microsoft.

Those ambitions, it seems, have fallen back to earth. On Thursday, Facebook said it plans to shut down Parse, the services platform for which it paid upwards of a reported $85 million.

And from the announcement on the Parse blog:

We understand that this won’t be an easy transition, and we’re working hard to make this process as easy as possible. We are committed to maintaining the backend service during the sunset period, and are providing several tools to help migrate applications to other services.

Parse provided a series of online backend tools for app developers, and this will certainly be a hassle for those who implemented Parse services in their iOS apps. Not to mention apps that were built on top of Parse and then abandoned – while those apps may still be working on modern versions of iOS thanks to backwards API compatibility, they will stop working once Parse – the online component – shuts down for good.

Below, I’ve compiled a list of some reactions from the developer community to the Parse announcement. See also: Connected #13 from November 2014 on App Store preservation.

Read more

Robleh Jama has been using Medium to share press kits for apps:

When you put everything a blogger needs for their article in one spot, they’re going to like that. They’re going to appreciate you because you didn’t just do what’s most convenient for you. You actually thought about them. And even if they don’t write about you now, it starts the relationships on the right foot.

We kept it as unlisted because we figured that it’d be best for bloggers and journalists to get the details first, before passing it along to their audiences. Unlisted posts on Medium are visible to only those who have the link. It won’t be listed on Medium’s public pages or your profile. You can choose to keep it as a draft, or publish the post as an Unlisted post, like we did, or a public post.

I agree with this. I’ve been sent a few Medium-hosted press releases over the past few months – most recently, one for Pigment – and the experience was better than having to download a bunch of PDFs and folders full of screenshots. Perhaps Dropbox could leverage the convenience of easily editable/linkable documents with Paper (imagine if you could combine text and media stored somewhere else in your Dropbox within a single shared document).

Side note: if you’re looking for something a bit more customizable and advanced, I can’t recommend presskit() enough.

Curtis Herbert has some wisdom for indie developers running a business:

What happens when the developer, designer, and the “evil” business/marketing person are all one in the same? You get a blog post out of it! Welcome to my inner struggles with Slopes as I’ve tried to turn it into a serious business.

Over the last few months I’ve learned that there is a need to compromise on some of my ideals. Well, compromise might not be the right word. I think some of the things that we think compromise our ideals actually don’t, when done right. I think as a designer / developer I was too quick to dismiss things I needed to implement to help my business be healthy just because of some preconceived “Apple would never do this” notion.

I would say that this applies to a lot of creative endeavors online. Many of us are fixated on ideals of elegance and perfectionism that aren’t healthy for the business, which ultimately results in failure to monetize and survive. A great product doesn’t sell by itself.

Hi, I’m John Petitto, one of IBM’s Swift developers located at IBM’s Mobile Innovation Lab in Austin. We love Swift here and thought you would too so we are making our IBM Swift Sandbox available to developers on developerWorks.

The IBM Swift Sandbox is an interactive website that lets you write Swift code and execute it in a server environment – on top of Linux! Each sandbox runs on IBM Cloud in a Docker container. In addition, both the latest versions of Swift and its standard library are available for you to use.

Neat idea by IBM to write and execute Swift code in any desktop web browser. Too bad the web app is barely usable in iOS Safari because of text selection issues. I’d love to have something like this as a native iOS app eventually (if Apple allows it; but if they allow Pythonista, why not a Swift interpreter now that the language is open source?).

Writing for Ars Technica, Andrew Cunningham interviewed Craig Federighi on Swift going open source and how Apple is approaching open development:

The Swift team will be developing completely in the open on GitHub,” Federighi told Ars. “As they’re working day-to-day and making modifications to the language, including their work on Swift 3.0, all of that is going to be happening out in the open on GitHub.”

So instead of getting a big Swift 3.0 info dump at WWDC 2016 in the summer and then digging into the Xcode betas and adapting, developers can already find an “evolution document” on the Swift site that maps out where the language is headed in its next major version.