EOL as End Of Life
here the definition from wikipedia End-of-life (product)
"End-of-life" (EOL) is a term used with respect to a product supplied to customers, indicating that the product is in the end of its useful life (from the vendor's point of view), and a vendor stops marketing, selling, or rework sustaining it. (The vendor may simply intend to limit or end support for the product.) In the specific case of product sales, a vendor may employ the more specific term "end-of-sale" (EOS). The time-frame after the last production date depends on the product and relates to the expected product lifetime from a customer's point of view. Different lifetime examples include toys from fast food chains (weeks or months), mobile phones (3 years) and cars (10 years).
And as you all know already Adobe announced Flash EOL for 2020,
and yeah sure "it sucks" and make some people worry to the point that they want (demand) that Adobe now provide a number for "years of commitment" to the Adobe AIR (which I already pointed out is a ridiculous demand).
So why am I talking again about EOL ?
because the way Adobe did it for Flash is not that bad, it could have been much much worst
see that for example
see that part "a classic silent EOL"
and the discussions about that
so yeah big software corporation don't really hesitate to kill a product for various reasons
ever loved a google product that got "discontinued" and left you barely few months to backup your data?
So when an EOL is public and made official, like Adobe did with Flash, is not that bad.
Other way to use an "EOL" for a company is to force users to upgrade to a new product
for example: Two years after Windows 10: Windows 7 is still threatening a 2020 EOL meltdown
Not that I try to paint anything Flash in a positive light, but considering that browser vendors were heavily forcing the hand of Adobe (constant critics/ranting about the plugin, blocking the plugin, click-to-play to just use the plugin etc.) and that, finally, having a clean cut between "flash tech" and the browser dependency is a pretty good idea (remember that AIR originally was marketed as "Out Of Browser" experience), yeah that Flash EOL is not that bad.
The take for indie devs: anything that is not good enough for big corpo is an opportunity.
When Google discontinue something like "Google Reader", hey clone/copy the basic and produce a RSS reader of your own, then go propose this alternative to all the disgruntle google users who wish they could still use a nice RSS reader.
The same thing can be applied to "playing SWF file in a browser", hey lucky us we can easily build a basic browser based on Safari Webkit with Adobe AIR and reuse a Flash Plugin (without blocking it) to play those SWF inside AIR directly.
And/or simply port your app/games from an online SWF to a desktop/mobile Adobe AIR app.
And if there is a lesson to be learned is that software have a life cycle, and ours too.
If you publish any app out there, realise that
- you will need to maintain/update it as long as you want this app to be seen "alive"
- you may need to EOL this software for various reasons
- do it silently ?
- do it publicly ?
There is no really a "right way" to do it, sure if an app is not really popular and used,
doing a silent EOL is very tempting.
My point is even at a small level of "indie" we can follow the general Software release life cycle
and include also how we handle "End of Life" of a product.