Slashdot Mirror

An anonymous reader writes Writer and former software engineer Matt Gemmell adds his voice to the recent rumblings about writing code as a profession. Gemmell worries that the latest "software Renaissance," which was precipitated by the explosion of mobile devices, is drawing to a close. "Small shops are closing. Three-person companies are dropping back to sole proprietorships all over the place. Products are being acquired every week, usually just for their development teams, and then discarded. The implacable, crushing wheels of industry, slow to move because of their size, have at last arrived on the frontier. Our frontier, or at least yours now. I've relinquished my claim." He also pointed out the cumulative and intractable harm being done by software patents, walled-garden app stores, an increasingly crowded market, and race-to-the-bottom pricing. He says that while the available tools make it a fantastic time to develop software, actually being an independent developer may be less sustainable than ever.

Following news this week of a game developer who turned the Android version of a game free because of piracy concerns, software developer Matt Gemmell has written a lengthy post explaining why he thinks Android apps are laboring under a broken business model. "People have to get paid. There has to be a revenue stream. You can’t reliably have that revenue stream if the platform itself and the damaged philosophy behind it actively sabotages commerce. If you want a platform to be commercially viable for third-party software developers, you have to lock it down. Just like in real life, closing the door and locking it helps make sure that your money remains yours. Bad behaviour has to be more difficult than good behaviour - and good behaviour means paying for your software." He also has some harsh arguments about some of the assumptions and philosophies underpinning the an industry built on an open platform. "Nerds like to say that people care about choice at that level. Nerds are wrong. Nerds care about choice, and nerds are such a tiny minority of people that nobody else much cares what the hell they think. Android is designed with far too much nerd philosophy, and open is gravy to those people because it’s synonymous with customization. ... Open is broken as a money-making platform model, unless you’re making the OS or the handsets. Most of us aren't doing that."

MikeatWired writes "Jon Udell writes that when it was recently discovered that some iPhone apps were uploading users' contacts to the cloud, one proposed remedy was to modify iOS to require explicit user approval. But in one typical scenario that's not a choice a user should have to make. A social service that uses contacts to find which of a new user's friends are already members doesn't need cleartext email addresses. If I upload hashes of my contacts, and you upload hashes of yours, the service can match hashes without knowing the email addresses from which they're derived. In the post Hashing for privacy in social apps, Matt Gemmell shows how it can be done." (Read more, below.) "Why wasn't it? Not for nefarious reasons, Gemmell says, but rather because developers simply weren't aware of the option to uses hashes as a proxy for email addresses. A translucent solution encrypts the sensitive data so that it is hidden even from the operator of the service, while enabling the two parties (parents, babysitters) to rendezvous. How many applications can benefit from translucency? We won't know until we start looking. The translucent approach doesn't lie along the path of least resistance, though. It takes creative thinking and hard work to craft applications that don't unnecessarily require users to disclose, or services to store, personal data. But if you can solve a problem in a translucent way, you should. We can all live without more of those headlines and apologies."