One unintended consequence of the accelerating popularity of HTML5 for mobile app development is an ability to skate past Apple’s App Store restrictions on in-app sales.  So I put this question to Piotr Steininger of Tapangi Consulting:

There’s talk out there about being able to use HTML5 to get around Apple’s App Store ban on charging for in-app purchases.  In other words (I think), somehow HTML5 allows content producers to get around this problem by making apps (and other things) downloadable directly through web browsers.  So … how is it that HTML5 allows getting around this issue?

Some background: Apple announced a policy change earlier this year, specifically in Section 11.14 of its App Store guidelines, Continue reading

In June of this year, Senator Al Franken (D. Minn.) introduced the “Location Privacy Protection Act of 2011” (S. 1223).  According to the bill summary available on Franken’s website, a 2010 investigation by the Wall Street Journal revealed that 47 of the top 101 mobile applications for Apple iPhones and Google Android phones disclose user location without consent of the user.

According to Franken’s bill summary, current law prevents disclosure of user location during telephone calls without user consent. Currently, no similar legislation protects user location when a user accesses information through a mobile web browser or mobile application. Franken claims that his bill will close loopholes in the Electronic Communications Privacy Act that allow for this distinction.

If S. 1223 passes, companies will be required to obtain permission not only to collect mobile user location information but also to share that information with third parties. Additionally, the bill seeks to put in place measures to prevent stalking through location information.

As of this writing, Franken’s bill has been assigned to the Senate Judiciary Committee and is being cosponsored by Sens. Blumenthal, Coons, Durbin, Menendez, and Sanders.

Original Post (published 9/8/2011)

When was the last time you read a license agreement after installing software or downloading an app on your smartphone? If you’re like most people, the answer is probably never.

According to some estimates, fewer than 8 percent of us actually read the entirety of those agreements, despite rising concerns about digital privacy and data collection. Continue reading

Kate Tummarello is a Research and Social Media Intern with Mirsky & Company and a reporter at Roll Call/Congressional Quarterly.  Follow Kate on Twitter @ktummarello.

Apple’s App Store is full of subscription-based content providers. Whether you’re watching a movie on the Netflix app, reading a book through the Kindle app or streaming a TV show using the Hulu Premium app, you’re probably used to paying for the app and then paying more for the content.

But that’s changing, thanks to Apple’s new policy, which will prohibit developers from requiring users to make a second purchase to access content once they have purchased the app itself.

Apple rumor website MacWorld reported earlier this summer that Apple was planning on this new policy. The article quoted Section 11.14 of Apple’s App Store guidelines:

Apps can read or play approved content (specifically magazines, newspapers, books, audio, music, and video) that is subscribed to or purchased outside of the app, as long as there is no button or external link in the app to purchase the approved content. Apple will not receive any portion of the revenues for approved content that is subscribed to or purchased outside of the app.

Previously, developers could charge one price for the app and then offer more content for a second price within the app. Unlike purchases made through the app store, where Apple receives 30 percent of the profit, profits made from purchases within the app itself would go entirely to the developer. In eliminating the possibility for in-app purchases, Apple is ensuring that it retains its 30 percent.

But developers are looking to find ways around this policy. According to MacWorld, Netflix has found a loophole in instructing users to “visit Netflix.com” without providing a button for users to do so.

Others are turning to the much anticipated HTML5. According to Piotr Steininger, co-founder of Tapangi Consulting [http://tapangi.com/] based in Washington, DC, HTML5 may open floodgates for apps that are accessed through a device’s web browser rather than through an app store.  Or in other words, “Rather than buying an app in the app store you just go to a URL and you’ve got an app to go,” Steininger says. “You load it once on the iPad and download a book locally, and you’re good to go.”

Amazon has already unveiled an HTML5-based Kindle app that works within a device’s browser, including on the iPad. The app synchronizes with a user’s Kindle library, and users can shop for Kindle content within the app. According to many reports, other content providers, including Wal-Mart, are similarly attempting to use HTML5-based apps to avoid the Apple App Store and its rules and fees.

Much has been made lately of tension between Twitter and its outside developers.  The issues stoking the fire are less legal issues than business issues brought to front-burner by two particular factors:

(1) The maturity of Twitter as a development platform, or in the words of Ryan Sarver of Twitter, “In the early days, all the clients except Twitter.com were built out by ecosystem companies, mainly because Twitter was so focused on keeping the lights on.  But we learned that in order for us to really grow, we had to start taking over that core experience.” (quoted in the NY Times, 7/17/11).

(2) A reported Federal Trade Commission inquiry into the relationship by the , which has (in some views) caused Twitter to re-think its liberal open-door policy when it came to permitting outside development on its platform.

An excellent story and accompanying podcast on this subject appeared in the NY Times last week, written by Claire Cain Miller.

Bottom line: Twitter is seeking to control the applications that control access to Twitter, meaning desktop and mobile, and leaving the field open to enterprise applications, usability applications, analysis and similar applications.

Certainly the business reasons seem pretty clear, in that Twitter seeks to control core functionality – and the development of that core functionality – of the mother ship.  Although it is not terribly surprising that that strikes some critics as cynical, see for example here (“Twitter, just be honest: ‘The only way we can figure out how to make money is same ol’ display ads and we need to own the client for that.’”)

There are legal issues here, namely the ability of the platform to restrict access to its API.  As Claire Miller and others have noted, part of the problem for Twitter is that developer expectations may have been artificially inflated.  But there is more.  The FTC hint of antitrust scrutiny may be causing Twitter some heartburn about its historical open-ness.  Some analogy from two unrelated contexts: In trademark law, the concept “use in commerce” requires confirmation of continued public use of a registered trademark every 5 years or so.  In real property law, a property owner’s failure to restrict public access to property – and thus demonstrate its private claim – can, under some circumstances, support a court’s granting a permanent public right of way.

Quoting Rob Diana from Regular Geek, “Twitter also now owns the platform as a whole and must be as reliable as a utility company.  They must provide all of the capabilities that consumers need in the clients.” (emphasis added) A danger for a “public utility” of the information superhighway is creeping expectation of the duties and obligations of public purpose: Loss of commercial freedom, permanent regulatory scrutiny and public stakeholder claims.  It may very well be that Twitter is acting much like New York’s Rockefeller Center, which closes public access to traffic one day a year as a legal “fiction” in order to continue to assert private ownership rights.

Twitter rolled out its new API TOS (“Developer Rules of the Road”) in March of this year.  Rob Diana noted at that time that the announcement may have been – or perhaps should have been – anticlimactic, in that “A basic Twitter client is a terrible idea in today’s ecosystem.”  Wrote Diana:

Unless there is major functionality outside of the existing solutions, a new client is a losing idea. There is a high barrier to entry when we already have third-party clients like Tweetdeck, Seesmic, HootSuite and PeopleBrowser. This does not include some of the other applications that focus on team or brand management. So, by saying not to develop a new client, Twitter has saved us and investors a lot of time and money.