What does the future availability of the Flash Player runtime look like?

hi all,

 

i'm maintaining product portfolio several flex (sdk 3.5) based products run in browser flash player plugins.

we're encountering clients start having problems availability of flash player runtime on systems (either through browsers abandoning npapi plugins or flash player not being available).

 

we're of course looking ahead , trying determine best way of continuing our code base, , runtime target ensure our products remain available on many platforms possible.

when around, can see possible alternatives flash player, neither of looks path i'd gladly follow:

- adjusting make products run in adobe air, worth (is runtime going around long enough put in effort)?

- i've seen apache flexjs trying compile mxml html5 compatible css/js (but of important tech amf, e4x etc. not supported yet, means converting mxml code of our existing projects new flexjs flavour of mxml, , being open source project there seemingly little guarantee of continuity in availability)

- javafx option mean rewriting our entire frontend codebase scratch

 

i hoping i'm not 1 problem , adobe or other devs may give hints how ensure target runtime of our flex products remains available on longer period of time (>5 years now)?

is there perhaps adobe manufactured html5 compiler flex projects in works, or way continue using flash player after browser vendors start block it?

 

we have 10 years worth of development in our flex codebase , seems such waste have rewrite different runtime.

any thoughts, helpful links appreciated!

 

thanks,

ferrie

sorry late response on this.  cleaning posts weren't answered in beta forums , wanted give response.

 

you know adobe's support flex ended around 2011.  donated code apache foundation, , apache flex project continues develop , maintain flex sdk.  there ongoing support flex through apache foundation, it's not we're throwing full weight of company behind anymore.

 

there no plans @ time discontinue flash player, landscape evolving, , it's clear browser vendors pursuing strategies increase friction users running flash content.  don't see trend reversing anytime soon.

 

at point in 2017, html5 landscape has sufficiently evolved point can reasonably replicate functionality in flex applications using html , javascript.  think you're taking gamble maintaining status quo.

 

i'm pretty pragmatic person.  if in shoes, i'd looking @ air hedge against browser friction, , simultaneously figuring out how can modularize things incrementally conform mainstream html/javascript technology stack. (e.g. replacing amf back-end services rest apis) if needed cut on @ point, i'm not staring down wholesale rewrite.

 

that said, don't think ever nirvana of maintenance-free products, because there's fragmentation , change happening in market.  new display technologies emerge higher densities, new categories devices , form factors go in , out of fashion, browsers , operating systems changing, etc.  said, minimizing risk in technology stack save work , keep more nimble , competitive in long run.

More discussions in Flash Player Beta Channel

adobe