Oh the places this post will go!

Now when I post something new on my blog, it automatically flows out to people who follow my RSS feed, to people who follow me on Medium, and through Facebook’s algorithm as an Instant Article.  

This is the first new post that will go to all those places.

Even better, when I update this post, Facebook will automatically get the update. So will readers on my blog. However Medium and people reading via RSS, unless their RSS app has been programmed to do updates (I don’t know of any, but it is possible) will not get updates. 

Twitter will get a link via Radio3
, however because this post occupies more than 140 chars, they will only get a link. I hope at some point they relax that limit. 

This is progress! Seriously. It’s a big deal. 😉

PS: Earlier today I wrote a post that explains at a high level how this works. 


Original URL: http://scripting.com/liveblog/users/davewiner/2016/02/24/1057.html

Original article

Google launches voice typing in Google Docs

We launched Voice typing in Docs to help you capture ideas, compose a letter, or even write the next great novel—all without touching your keyboard. Starting today, you can also edit and format your documents with your voice.

To get started, select “Voice typing” in the “Tools” menu when you’re using Docs in Chrome. Say what comes to mind—then start editing and formatting with commands like “copy,” “insert table,” and “highlight.”

Check out the full list of commands in our Help Center or simply say “Voice commands help” when you’re voice typing.
It’s a quick and easy way to get ideas out of your head, and into a doc. So try out Voice typing (and editing and formatting) today!

Posted by Isaiah Greene, Product Manager


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/VwDNJ2MZuig/type-edit-and-format-with-your-voice-in.html

Original article

Voice Recognition and Text to Speech in Python

It’s tough for an erstwhile Iron Man to work on creating their personal AI assistant on the weekends. Like any other time-pressured inventor without a PhD in computer science and linguistics, I decided to use a library for speech recognition and synthesis. Fortunately, Python offers several choices. Unfortunately, many of simply them don’t work any more. I will discuss the ones that are still functional and can be used with Python 2.7 and Python 3 (up to Python 3.5 at the time of writing).

j-a-r-v-i-s

My AI assistant is actually a little humbler – I call it Samwise

Jarvis’s Mouth: Text-to-Speech

We’ve all heard of Google’s AI initiatives (maybe Larry Page aspires to Tony Stark status?), so it should come as little surprise that they offer a RESTful way to do voice recognition and speech synthesis. The Python library that nicely wraps their text-to-speech API is gTTS.

gTTS takes advantage of Google Translate’s voice capability and downloads its response to a parameterized GET request into an mp3 file (or in-memory file). However, you would need one of the pygame, pyglet + AVBin, or VLC Player python libraries to play that mp3. This is additional complexity and dependency bloat. Additionally, you need an API key to use Google Translate (no longer free because of the “substantial economic burden caused by unintended abuse”).

I also found pyttsx, which is a great offline option. JPercent has updated it for Python 3. Install JPercent’s version by downloading the repository and pip install from that local folder; otherwise pip install pyttsx directly. For Windows, you need to install PyWin32 and make sure you have the Microsoft Speech API installed. If you’re using virtualenv, you must copy the win32 folders and the files with win32 in its name from your python install directory’s Lib/site-packages to your virtual env’s Lib/site-packages. Additionally, pyttsx has difficulty detecting the installed libraries on Windows 10 and must be manually initialized to use ‘sapi5’.

Jarvis’s Ears: Speech Recognition

SpeechRecognition is a wonderful, up to date library that offers to use CMU’s open source Sphinx project, Google services, or Wit.ai to convert audio input into text. If you intend to recognize microphone input, you’ll also need PyAudio. Sphinx is enormously powerful, but SpeechRecognition includes a wheel package for a simple language definition and handles all of the complexity for us. While Google speech recognition is a paid service, Wit.ai is free as of last January, when they were acquired by Facebook. I found Google’s offering to be of the highest quality, and you have 50 calls/day free with your developer API key. Sphinx’s voice recognition was by far the poorest and often garbled words, though still tended to produce useful recognized words in the middle and end of the phrase.

Jarvis’s Brain: The Code

I ultimately opted to use pyttsx and SpeechRecognition/Sphinx because they are offline and free, with great open source licenses. Whichever route you may choose, you can now assemble these libraries to create your own Frankensteinien AI assistant:

The code itself is straightforward, as anyone would hope after spending a couple of hours researching this on a weekend (and getting it to work on Windows, no less). Try it out!


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/nRIs8Iv5cnM/

Original article

YouTube Can Now Blur Faces, Logos, and More With Its New Motion-Tracking Tool

YouTube’s built-in editing tools aren’t always the best tools for a given job. If you need to blur a face or an image, however, it just got a heck of a lot easier with YouTube’s new blur tool.

Read more…



Original URL: http://feeds.gawker.com/~r/lifehacker/full/~3/Q9kM6CxEG34/youtube-can-now-blur-faces-logos-and-more-with-its-ne-1761235761

Original article

CALIcon16 Call for Presentations

CALIcon16 June 16-18 Georgia State University College of Law Atlanta, GA http://2016.calicon.org Call for Presentations (Deadline Friday, April 8, 2016): Declining applications and the legal marketplace recession creates a more complex and competitive market for legal education and lawyers.  Many of the fixes have a technology component like distance learning, formative assessment, virtual law practice, law […]


Original URL: http://spotlight.classcaster.net/2016/02/25/calicon16-call-for-presentations/

Original article

GPL Violations Related to Combining ZFS and Linux

February 25, 2016 by Bradley M. Kuhn and Karen M. Sandler

GPL Violations Related to Combining ZFS and Linux

This post discusses an atypical GPL violation. Unlike most GPL violations
Conservancy faces, in this case, a third-party entity holds a magic wand that
can instantly resolve the situation. Oracle is the primary copyright holder
of ZFS, and, despite nearly eight years (going back to the days of Sun’s
control of the code) of the anti-license-proliferation community’s urging,
Oracle continues to license their code under their own, GPL-incompatible
license. While this violation has many facets, and Oracle did not themselves
violate GPL in this specific case, they hold the keys to this particular
kingdom and they forbid the Linux community to enter. While there are
complexities that we must address, in this context, Oracle could make
everyone’s life easier by waving their magic relicensing wand. Nevertheless,
until they do, since GPL-incompatible licenses are the root of all GPL
violations, combinations of GPL’d code with Oracle’s GPL-incompatible code
yield GPL violations, such as the ongoing violation by Canonical, Ltd.

The Basic Facts

Sun released the Z File System (ZFS) code
under the Common Development
and Distribution License, version 1 (CDDLv1)
as part of OpenSolaris. Sun
was ultimately acquired by Oracle. Community members, mostly acting
non-commercially, have improved ZFS and adapted it to function with Linux,
but unfortunately, CDDLv1 is incompatible with GPLv2, so distribution of
binaries is not permitted (see below for details). Many community members
have been frustrated for years that Oracle didn’t simply relicense the code
under a GPLv2-compatible license.

The situation escalated last week
because Canonical,
Ltd. announced their plans to commercially distribute, in Ubuntu 16.04, a
binary distribution of ZFS as a Linux kernel module
, which adapts ZFS
natively for Linux. Conservancy contacted Canonical to inform them of their
GPL violation, and Canonical encouraged us to speak publicly. We’re glad to
do so to clarify the differing views on this issue. As you’ll read below,
Conservancy disagrees with Canonical’s decision, and Conservancy hopes to
continue dialogue with Canonical regarding their violation. We do not give
up on friendly resolution of a GPL violation easily and are glad Canonical
seeks to transparently discuss both sides of this issue in public.

Summary of our Conclusion

We are sympathetic to Canonical’s frustration in this desire to easily
support more features for their users. However, as set out below, we have
concluded that their distribution of zfs.ko violates the GPL. We have
written this statement to answer, from the point of view of many key Linux
copyright holders, the community questions that we’ve seen on this
matter.

Specifically, we provide our detailed analysis of the incompatibility
between CDDLv1 and GPLv2 — and its potential impact on the trajectory
of free software development — below. However, our conclusion is simple: Conservancy and the Linux copyright
holders in the GPL Compliance Project for
Linux Developers
believe that distribution of ZFS binaries is a GPL
violation and infringes Linux’s copyright. We are also concerned that it may
infringe Oracle’s copyrights in ZFS. As such, we again ask Oracle to respect
community norms against license proliferation and simply relicense its
copyrights in ZFS under a GPLv2-compatible license.

GPL Incompatibility

The license of Linux, the GNU General Public License, version 2 (GPLv2), is
conceptually known as a strong copyleft
license. A strong copyleft license extends software freedom policies as far
as copyright law allows. As such, GPLv2 requires that, when combinations
and/or derivatives are made under copyright law with GPLv2’d works, the
license of the resulting combination and/or derivative is also GPLv2.

The Free Software Foundation (FSF)
has long
discussed the question of licenses incompatible with the GPL
, pointing
out that:

In order to combine two programs (or substantial parts of them) into a
larger work, you need to have permission to use both programs in this
way. If the two programs’ licenses permit this, they are compatible. If
there is no way to satisfy both licenses at once, they are incompatible.

License compatibility is not merely a question for Free Software
licenses. We can analyze any two copyright licenses and consider whether
they are compatible.

In the proprietary software world, rarely are two licenses ever
compatible. You can’t, by default, license a copy of Oracle’s database, and
then make a combination with Apple’s iOS. To do so, you would need to
negotiate (and pay for) a special license from both Apple and Oracle to make
that combination.

Furthermore, with proprietary software, there is a practical problem
somewhat unrelated to the legal permission: you must procure (again, likely
for a rather expensive fee) a copy of the source code for Apple’s and
Oracle’s proprietary software to have the practical ability to make the
combination.

Since the GPL, and all copyleft licenses, are fundamentally copyright
licenses, the analysis is similar. However,
GPL requires that all software distributions include complete corresponding
source code to any binaries, so the practical problem never presents itself.
Nevertheless, when you wish to combine GPL’d software with some other
software and distribute the resulting combination, both the copyright holders
of the GPL’d software and the copyright holders of the other software must
provide a license that allows distribution of the combination.

Most prefer to discuss the issue of combining truly proprietary,
no-source-available copyrighted material with GPL’d software, as it creates the most
stark practical contrast, and is the most offensive fact pattern.
Proprietary software gives the users no freedom to even examine, let alone
modify, rebuild, and reinstall the software. The proprietary license doesn’t
allow nor even give the practical ability to redistribute source code, and
the GPL mandates source distribution when binary distribution occurs. The
incompatibility is intuitively obvious. Few consider the fact that
proprietary software licensing is just one (rather egregious) example of a
GPL-incompatible license.

In that context, we can imagine licenses that are GPL-incompatible, but do
give some interesting permissions to users. An example is
source-code-available systems that prohibit commercial distribution and
forbid modification to the source code. The GPL has terms that permit
modification and allow commercial distribution of GPL’d software, and as
such, even though source code is available for non-commercial, non-modifiable
software, the license is nonetheless GPL-incompatible.

Finally, we can consider the most subtle class of GPL-incompatibility, in
which we find ZFS’s license,
the Common
Development and Distribution License, version 1 (CDDLv1)
. The CDDLv1 is
considered both
a Free
Software
and an Open
Source
license, and is a weak copyleft license. Nevertheless, neither
CDDLv1 nor GPLv2 permits combination of copyrighted material under the
other license.

To understand this non-intuitive incompatibility, we can analyze in
detail the requirements of both licenses. First, GPLv2 requires:

[§2](b) You must cause any work that you distribute … that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole … under the terms of this
License.…

[§]3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also…

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above…

[§]6. …You may not impose any further
restrictions on the recipients’ exercise of the rights granted herein.

According to these provisions of GPLv2, if you create a binary work that
incorporates components from the GPLv2’d program, you must provide the
complete corresponding source for that entire work with the binary, and the
terms of the GPLv2 apply to that source. If the sources as a whole cannot be
outbound-licensed under GPLv2, you have no permission under copyright law to
distribute the binary work, since GPLv2 didn’t grant you that permission.

GPLv2-compatible licenses do not contradict the requirements of GPLv2, which is
what makes them compatible. For example, highly permissive licenses like
the ISC
license
allow imposition of additional licensing requirements (even
proprietary ones), and so combining ISC-licensed source and GPLv2’d
source into a binary work is permitted; compliance with GPLv2 is possible
when distributing binaries based on the combined sources.

CDDLv1, however, contains various provisions that are incompatible with
that outcome. Specifically, CDDLv1 requires (emphasis ours):

[§]3.1 … Any Covered Software that You distribute or otherwise make available in
Executable form must also be made available in Source Code form and that
Source Code form must be distributed only under the terms of this
License
. …

[§] 3.4 … You may not offer or impose any terms on any Covered
Software in Source Code form that alters or restricts the applicable
version of this License

CDDLv1 is a weak copyleft license in that it allows you create a binary work with
components under different terms (see CDDLv1§3.6). However, as seen
in the text above, with regard to the specific copyrighted material already
under CDDLv1, that material must remain only licensed under the terms of
the CDDLv1. Furthermore, when redistributing the source code, you cannot
alter the terms of the license on that copyrighted material.

GPLv2, as shown above, requires that you alter those terms for the source
code — namely, as a strong copyleft, the terms of GPLv2 apply to the
entire complete corresponding source for any binary work. Furthermore,
downstream users need permission to make GPLv2’d modifications to that
source. This creates a contradiction; you cannot simultaneously satisfy
that obligation of GPLv2 and also avoid alter[ing] the terms of
CDDLv1-licensed source. Thus, the licenses are incompatible, and
redistributing a binary work incorporating CDDLv1’d and GPLv2’d copyrighted
portions constitutes copyright infringement in both directions. (In
addition to this big incompatibility, there are also other smaller
incompatibilities throughout CDDLv1.)

We believe Sun was aware when drafting CDDLv1 of
the incompatibilities; in fact, our research into its history indicates the
GPLv2-incompatibility was Sun’s design choice. At the time, Sun’s apparent
goal was to draw developers away from GNU and Linux development into
Solaris. Not only did Sun not want code from GNU and Linux in Solaris,
more importantly, Sun did not want technological advantages from Solaris’ kernel to
appear in Linux.

Much has changed in the seven and a half years since CDDLv1’s publication
and promulgation. OpenSolaris has been discontinued; CDDLv1 codebases
never became an active area of Free Software development like GNU and
Linux. Oracle could now easily indicate that combination of ZFS with Linux
into binary works is permitted, (e.g., as the overwhelming majority
copyright holder0, Oracle
could make
a decree like the one University of California did to fix a similar
incompatibility
). Until Oracle takes an action like that, it remains a
license violation of both CDDLv1 and GPLv2 to distribute
binary works that combine together and/or derive from both GPLv2 and CDDLv1
sources.

What Constitutes a Combined/Derivative Work?

Once license incompatibility is established, the
remaining question is solely whether or not combining ZFS with Linux creates
a combined and/or derivative work under copyright law (which then would, in
turn, trigger the GPLv2 obligations on the ZFS code).

Conservancy has helped put similar questions (still
pending) before a Court,
in Hellwig’s
VMware case
that
Conservancy currently funds.
In fact, the same questions come up with all sorts of GPL-incompatible Linux
modules and reuses of Linux code.

Courts have not spoken specifically on this question; precedents that
exist are not perfectly on-topic. Citing an opinion of a lawyer is
often not helpful in this context, because lawyers advise clients, and
argue zealously for their clients’ views. When Courts are unclear on a
matter, it generates disputes, and only Courts (or possibly new
legislation) can ultimately resolve those disputes.

Nevertheless, our lawyers have analyzed these situations with
the assistance of our license compliance and software forensics staff for
many years, and we have yet to encounter a Linux module that — when
distributed in binary form — did not, in our view, yield combined
work with Linux. The FSF, stewards of the GPL,
have stated
many times over the past decades that they believe there is no legal
distinction between dynamic and static
linking of a C program
and we agree. Accordingly, the analysis is quite
obvious to us1: if ZFS were
statically linked with Linux and shipped as a single work, few would argue
it was not a “work based on the Program” under GPLv2. And, if
we believe there is no legal difference when we change that linking from
static to dynamic, we conclude easily that binary distribution of ZFS plus
Linux — even with ZFS in a .ko file — constitutes distribution
of a combined work, which we name Linux+ZFS.

Canonical has found some lawyers who disagree — a minority position, from our understanding of community norms. But Canonical’s
public position on the matter contributes to license uncertainty, and
opponents of Free Software may use this as an opportunity to marginalize
copyleft enforcement generally. Canonical can resolve the situation by
ceasing the infringing distribution, but Oracle can also unilaterally resolve
this trivially with a simple relicense of ZFS to a GPL-compatible license.

Thus, all parties currently stand at an impasse. Conservancy (as a Linux
copyright holder ourselves), along with the members of our coalition in the
GPL Compliance Project for Linux Developers, all agree that Canonical and
others infringe Linux copyrights when they distribute zfs.ko. Canonical’s
lawyers disagree. Oracle refuses to relicense their ZFS copyrights under a
GPL-compatible license.

Ultimately, various Courts in the world will have to rule on the more
general question of Linux combinations. Conservancy is committed to
working towards achieving clarity on these questions in the long term. That work began in earnest last year with the
VMware lawsuit, and our work in this area will continue indefinitely,
as resources permit. We must do so, because, too
often, companies are complacent about compliance. While we and other
community-driven organizations have historically avoided lawsuits at any cost
in the past, the absence of litigation on these questions caused many
companies to treat the GPL as a weaker copyleft than it actually is.

Why Conservancy Does Not Use Litigation Immediately

As discussed in our
principles
, Conservancy, while willing to litigate, uses
litigation only as a last resort. Compliance actions are primarily
education and assistance processes to aid those who are not following the
license.
We completely
exhaust every other diplomatic option
for compliance before seeking
resolution from the Courts.

“Almost There” is More Painful Than Proprietary

Conservancy and our GPL Compliance Project for Linux Developers are quite
sympathetic to the feeling of “almost there” that exists with ZFS
for Linux. CDDL is a Free Software license, but sadly a
GPL-incompatible one. Like a partial fix for a problematic bug, a
GPL-incompatible Free Software license feels like a solution that’s
“oh-so-close”. Everyone wants to try to tweak
that incomplete solution into a full one. We hope this explanation helps
bring clarity that the seemingly “almost there” of
combining CDDL’d and GPL’d code is a mirage. The community must seek
together a better solution.

Oracle holds the better solution in their hands; like waving a magic wand,
they can take any of a myriad of actions to communicate permission to
relicense ZFS under GPL. Conservancy encourages Free Software enthusiasts
and for-profit companies alike to lobby Oracle to relicense their ZFS
copyrights. While this change by Oracle cannot resolve Canonical’s
violation, Oracle’s relicensing would create a path for Canonical that
might ultimately yield a compliant binary distribution of Linux+ZFS. As
such, we’ve asked Canonical to commit to lobbying Oracle for this
change.

Is The Analysis Different With Source-Only Distribution?

We cannot close discussion without considering one final unique aspect to
this situation. CDDLv1 does allow for free redistribution of ZFS source
code. We can also therefore consider the requirements when distributing
Linux and ZFS in source code form only.

Pure distribution of source with no binaries is undeniably
different. When distributing source code and no binaries,
requirements in those sections of GPLv2 and CDDLv1 that cover modification
and/or binary (or “Executable”, as CDDLv1 calls it)
distribution do not activate. Therefore, the analysis is simpler, and we
find no specific clause in either license that prohibits
source-only redistribution of Linux and ZFS, even on the same distribution
media.

Nevertheless, there may be arguments for contributory and/or indirect
copyright infringement in many jurisdictions. We present no specific
analysis ourselves on the efficacy of a contributory infringement claim
regarding source-only distributions of ZFS and Linux. However, in our GPL
litigation experience, we have noticed that judges are savvy at sniffing
out attempts to circumvent legal requirements, and they are skeptical about
attempts to exploit loopholes. Furthermore, we cannot predict Oracle’s
view — given its past willingness to enforce copyleft licenses, and
Oracle’s recent attempts to adjudicate the limits of copyright in Court.
Downstream users should consider carefully before engaging in even
source-only distribution.

We note
that Debian’s
decision to place source-only ZFS in a relegated area of their archive
called contrib
, is an innovative solution. Debian
fortunately had a long-standing policy that contrib was
specifically designed for source code that, while licensed under an
acceptable license
for Debian’s
Free Software Guidelines
, also has a default use that can cause
licensing problems for downstream Debian users. Therefore, Debian
communicates clearly to their users that this code is problematic by
keeping it out of their main archive. Furthermore, Debian
does not distribute any binary form of zfs.ko.

(Full disclosure: Conservancy has a services agreement with Debian in
which Conservancy occasionally gives its opinions, in a non-legal capacity,
to Debian on topics of Free Software licensing, and gave Debian advice on
this matter under that agreement. Conservancy is not Debian’s legal
counsel.)

Do Not Rely On This Document As Legal Advice

You cannot and should not rely on this document as legal
advice. Our lawyers, in conjunction with our GPL compliance and software
forensics experts, have analyzed the Linux+ZFS that Canonical includes in
their Ubuntu 16.04 prereleases. Conservancy has determined, with the advice
of both inside and outside law firm legal counsel, that the binary
distribution constitutes a derivative and/or combined work of ZFS and Linux
together, and therefore violates the GPL, as explained above. We also know
from Canonical’s
blog post
that they have found other lawyers to give them contradictory
advice. Such situations are common on groundbreaking legal issues, and,
after all, copyleft is perhaps the most novel legal construction for
copyright in its history. Lawyers and their clients who oppose copyleft will
attempt to limit copyleft’s scope (with litigation, FUD, and moxie), and
those of us who use copyleft as a tool for software freedom will
diametrically seek to uphold its scope to achieve the license drafter’s and
licensors’ intended broad impact for software freedom.

Indeed, Conservancy believes this situation is one battle in a larger
proxy war by those who seek to limit the scope of strong copyleft generally.
Yet, the GPL not only benefits charitable community organizations like
Conservancy, but also for-profit companies, since GPL ensures your
competitors cannot circumvent the license and gain an unfair advantage. We
therefore urge charities, trade associations and companies who care about
Linux to stand with us in opposition of GPL violations like this one.

More work might be
required to relicense all modern ZFS code, since others have contributed, but
we expect that those contributors would gladly relicense in the same manner
if Oracle does first.

More discussion on
these issues can be found in this
section of Copyleft and the GNU General Public License: A Comprehensive
Tutorial and Guide
, which is part
of copyleft.org, a project co-sponsored by
the FSF and Software Freedom Conservancy.

Posted by Bradley M. Kuhn and Karen M. Sandler on February 25, 2016. Please email any comments on this entry to info@sfconservancy.org.

Tags: GPL

Other Conservancy Blog entries…


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/eYPFZDMZVqY/

Original article

Just Landed Is Shutting Down

Just Landed is Shutting Down

I’ve recently made the difficult decision to sunset and eventually shut down my company’s popular iOS travel app, Just Landed, which launched on the App Store in June 2012. As of today, Just Landed is no longer available for sale on the iTunes App Store, but will continue to operate normally for existing users. The servers powering Just Landed will shut down completely in just over 5 months time, on July 31st 2016, at which point the app will cease to function. I expect that this will be an unpopular decision, so as a courtesy to our users, I want to take this opportunity to explain the reasons behind the shutdown.

First, let me say that I’m extremely grateful to all of you who used and supported Just Landed over the past few years. As an independent developer who made Just Landed with a couple of friends, it was thrilling to have hundreds of thousands of people not only use something that we created, but also write glowing reviews, and recommend it to their friends and colleagues. Just Landed also received high praise in the press, was frequently featured on the App Store by Apple, and was even mentioned on TV a couple of times. We never expected such a great response to the app.

So what went wrong?

1. Lack of Innovation in Flight Data

The first thing that makes running Just Landed difficult in the long-term is a serious lack of innovation in the flight data industry. An app like Just Landed relies on access to high quality flight data to function correctly. However, since the airline industry is extremely fragmented, and uses antiquated IT systems and many incompatible data formats, it is not practical for a small independent developer like us to negotiate data-sharing contracts with each individual airline, and then unscramble their jumbled data feeds into a usable format at a reasonable cost.

In fact, commercial flight data has been such a mess for so long, that a few specialized companies have sprung up to deal with this enormous headache. These companies act as middlemen who gather, sanitize, debug, and resell flight data to developers like us. Without the help of these companies, Just Landed could never have existed, because it was totally impractical to take on this huge data challenge ourselves just so that we could make an app.

Unfortunately, because there are only really a couple of these flight data resellers, there is effectively a duopoly in the flight data business — these companies enjoy significant pricing power and very little outside competition. Unlike most technology companies, they feel little pressure to innovate, and are not particularly concerned with modernizing their services, improving their data quality and reliability, or adding new features.

This lack of innovation in flight data has been a huge source of frustration for us, and ultimately limited our ability to improve upon the Just Landed app and the experience for our customers. In particular, flight data inaccuracies account for virtually all of the customer complaints that I receive, and the sad truth is that I have really no control over these errors, and little influence to improve the situation. For a long time I’ve viewed this as unsustainable, because we are at the mercy of companies who are both indifferent to the needs of our customers, and resisting progress.

2. Rising Costs

Since Just Landed launched in 2012, the cost of running the service has steadily increased over time. While flight data remains expensive, the real source of the cost increases has been adapting to the demise or restructuring of supporting services such as StackMob, UrbanAirship, and Bing Maps that Just Landed previously relied on. Traffic and mapping data in particular, much of which used to be free, has become quite expensive, and is now tightly controlled by big companies under oppressive Terms of Service.

Another reason for rising costs is that the profile of the typical Just Landed user has changed over time. While the app was initially used primarily by individuals who made a few airport pickups per year, today Just Landed is increasingly used by professional limousine and taxi drivers, airline professionals, and travel companies. These power users consume 100–500 times as much flight data per year as casual users, and so the cost of supporting will soon begin to overwhelm revenue from new app sales.

Just Landed’s pay-once business model relies on pricing the app above the average lifetime cost of acquiring and supporting a user. This was previously not at odds with typical App Store pricing ($0.99–4.99), but nowadays many of our users are anything but typical, meanwhile typical app prices globally have continued a steady slide to $0. Clearly this points to a broken business model, which leads me to my next point…

3. Deteriorating App Economy

With well over 2 million apps by now (officially 1.5M as of July 2015), the iTunes App Store is an incredibly crowded place where it’s almost impossible to get noticed. Despite the persistent myth of the app developer millionaire, it’s extremely hard to make a profit — let alone a living — as an iOS app developer. The Google Play Store is a similar story, except with the added bonus of rampant piracy and a zillion devices to support. There really isn’t gold in them hills, at least not anymore, and independent app development will soon be in sharp decline, if it isn’t already.

Essentially, there’s a massive oversupply of apps, and the app markets are now saturated and suffering from neglect and short-term thinking by the companies who operate them. As competition has intensified, developers have resorted to giving their apps away, often at the urging of the app stores themselves. Consequently, the willingness of users to pay for apps, even unique apps like Just Landed, has declined sharply, while expectations of what an app should deliver have never been higher. Developers have been forced to get absurdly creative with their business models and marketing strategies just to make any income at all, rather than making the best product for their users. Just Landed, being a paid app with high running costs, has been on the wrong side of these trends, and what worked in 2012 no longer works in 2016.

4. Limited Resources

The Just Landed app hasn’t been updated in over 2 years, which is pretty much an eternity on the App Store. This happened because other projects I was working on took priority, and because the economics simply don’t justify the cost of updating it. For a long time I wrestled with the idea of potentially giving the app new life by overhauling the design, changing the business model, supporting more languages and devices, and launching in more countries. However, I don’t believe that even such dramatic changes would be enough to overcome all of the systemic problems that I’ve outlined above.

Simply put, the odds of financial success for Just Landed 2.0 are slim to none, and I just don’t have the will or the resources to attempt such a foolish endeavor.


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/cwlCkhuwpYw/just-landed-is-shutting-down-629765cbe1d7

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: