<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrew W. Donoho on Medium]]></title>
        <description><![CDATA[Stories by Andrew W. Donoho on Medium]]></description>
        <link>https://medium.com/@adonoho?source=rss-2d4ed10f926d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yKl0cZxUfS8ya51l.jpeg</url>
            <title>Stories by Andrew W. Donoho on Medium</title>
            <link>https://medium.com/@adonoho?source=rss-2d4ed10f926d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:37:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adonoho/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Parse Server: A Viable Open Source Platform?]]></title>
            <link>https://medium.com/@adonoho/parse-server-a-viable-open-source-platform-f222d8364311?source=rss-2d4ed10f926d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f222d8364311</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[parse]]></category>
            <dc:creator><![CDATA[Andrew W. Donoho]]></dc:creator>
            <pubDate>Thu, 28 Apr 2016 21:53:32 GMT</pubDate>
            <atom:updated>2016-04-28T21:53:32.082Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, April 28th, 2016, Facebook announced that 9,500+ apps migrated off of Parse’s infrastructure onto their own private DBs. WoW! 500K claimed Parse apps =&gt; 9.5K apps with enough business to pay for DB storage.</p><p>No wonder they’re shutting it down.</p><p>My app, <a href="http://bit.ly/SpotMarksTheTax">Spot marks the taX™ Residency App</a>, is a proud member of the 9.5K Parse survivors. (By the way, as I have both a production and test server, I count as two of the above apps. What if those 9,500 Parse apps actually represent only 4,750 mobile apps?)</p><p>As a developer, you have to ask yourself about the viability of maintaining your app on the <a href="https://github.com/ParsePlatform/parse-server">Open Parse Server</a>. Open source software depends upon the kindness of strangers; people like me. (I have made extremely modest contributions to the <a href="https://github.com/ParsePlatform/Parse-SDK-iOS-OSX">Parse iOS SDK</a>.) How many people are working on the platform? Github lists 66 people lead by non-Facebook employee, <a href="http://github.com/flovilmart">Florent Vilmart</a>. The Facebook employed contributors are winding their contributions down. This is to be expected — Facebook is abandoning the platform.</p><p>The normal dynamic around open source platforms is that there is some strategic or tactical reason for companies to pay for engineers to modify and improve the code base. Do such reasons exist for the Open Parse Server? There were several startup announcements shortly after Facebook announced the demise of their service. But lets run the numbers. 9,500 apps have been moved into a self-managed situation. The vast majority of those are almost certainly running the DB themselves or on <a href="http://mlab.com/">mLab.com</a> or similar. In other words, these 9,500 developers are largely self sufficient. Will they fund contributions to the Open Parse Server?</p><p>I’m doubtful.</p><p>As a developer, you have to balance the costs you incur maintaining abandonware versus the costs of moving off of the platform. To my mind, the key determinant of whether to stay is the quality and quantity of folks maintaining your platform. On July 28, 2016 Facebook wants all of us to be running everything on our infrastructure. What happens if Mr. Vilmart is the only person contributing to the Open Parse Server? I think that means you pull the trigger to get off of Open Parse Server.</p><p>As a modest user of Parse functionality, I intend to continue to run my apps on Open Parse Server and mLab.com through the balance of 2017. I am building test apps that use different platforms — Amazon Web Services, Google Cloud Platform, or Microsoft Azure. In other words, I am moving to a large scale platform whose business is to support third party apps. Currently, the most complete of these serverless cloud platforms is from Amazon Web Services. Depending upon when I feel I need to pull the platform migration trigger, then the other two platforms should be quite a bit more mature. AWS is the serverless cloud architecture leader. If I had to move right now, I would move my apps to them.</p><p>What about all of the app server companies? Kinvey? Backendless? Others? If the least expensive, large scale MBaaS vendor, Parse, only had 9,500 commercially sustainable apps, then how stable can these other players be? What is their cash flow and profitability like? If it wasn’t viable for Facebook, why is it viable for these guys/gals? The big three above are just adding mobile device support to their existing stable of services; the marginal cost to them to support mobile apps is quite modest. They can stay in the game a long time. Can the small guys survive while the big guys encroach into their space? Are you going to bet your business on it?</p><p>As my app is stable, I am loathe to incur platform migration challenges. But I am planning to do so. I chose Parse so I could avoid running a platform. While Heroku and mLab are going to make running on their infrastructure painless, bit rot will set in. Node.js will improve. Apple WWDC is right around the corner; Apple will be introducing changes into iOS. Google I/O is also happening in May; Android will change. Will the Parse client SDKs survive the underlying platform mutation?</p><p>Platform maintenance is a real expense. Do you, as a Parse developer, want to incur it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f222d8364311" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Civilized Technology]]></title>
            <link>https://medium.com/@adonoho/civilized-technology-31d423aa8a89?source=rss-2d4ed10f926d------2</link>
            <guid isPermaLink="false">https://medium.com/p/31d423aa8a89</guid>
            <category><![CDATA[apple-watch]]></category>
            <dc:creator><![CDATA[Andrew W. Donoho]]></dc:creator>
            <pubDate>Thu, 18 Jun 2015 16:02:38 GMT</pubDate>
            <atom:updated>2015-06-18T16:02:38.400Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone expected me to have an Apple Watch delivered the day it was unveiled. As a long time Apple developer, 30+ years, I had already seen the Watch in person. I knew what it would do; yet I tarried.</p><p>I don’t wear a watch.</p><p>Just because Apple now makes a watch should I buy it?</p><p>As an older geek/nerd/developer, I’ve found that advantages accrue to me from my knowledge, my ability to avoid foolish projects, and my developing sense of style. Yes, I compete with sartorial schlubs. Visibly standing out has brought business my way.</p><p>As a Texan, it is my birthright to wear a hat. I’m creating a style around being a “Gentleman Programmer”; I’ve chosen though to wear “city boy” Stetsons — a straw Open Road and a felt Stratoliner — iconic headgear of men of power, LBJ and Howard Hughes, respectively.</p><p>If I was going to wear a watch, it needed to complement my emerging style. The Watch needed to amplify the look of a Gentleman Programmer. Hence, the Sport Edition was eliminated. As Gentlemen are refined, I went to the black stainless with black stainless links. I chose to order the 38mm Watch instead of the 42mm; it is sleeker and refined. As a programmer, you also chose the platform with the tightest constraints first. The smaller watch embodies those constraints. It will require invention and insight to deliver an effective UI on such a small device. I’ve already tried apps that were clearly designed with the larger watch in mind. They are unpleasant to use.</p><p>I was visiting in NYC and having a getting to know you conversation with a fascinating Parisian couple over coffee near the High Line. My Watch buzzed with a message from my neighbor — our dog had escaped from her yard and he had put her back. I was able to surreptitiously provide the canned “Thank You” response. Then, more importantly, I was able to politely disengage from the conversation with a reason and call our house sitter.</p><p>Upon returning from the call, Catherine remarked on how civilized the whole interruption had been. She now felt very well disposed to buying a watch herself. She had just seen it improve the quality of life and not interrupt it.</p><p>Any technology that can improve life and not interrupt it is civilied indeed.</p><p>The Apple Watch is civilized.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31d423aa8a89" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>