Silverlight & Flash Application Replacement
for businesses in Australia, New Zealand, the UK and the US.
Flash Player support ended on 31 December 2020 and Silverlight on 12 October 2021. No current browser runs either, so these applications are not degraded, they are unreachable.
- Independent No licence commission, no reseller agenda
- 18+ yrs Building business software
- Fixed Price scopes, no surprises
- AU NZ UK US Perth-based, working remotely
Not deprecated. Actually dead.
This is the one category on this list where the application genuinely stopped working rather than quietly carrying on. Every current browser removed the plugin, so a Silverlight or Flash application is reachable only through an old browser kept alive on an isolated machine, if at all.
What is usually left is a dashboard, a training module, an interactive diagram or a data-entry front end that was the best available option in 2010 and now cannot be opened.
Your Silverlight / Flash project, end to end
Three stages. Scoped and fixed-price before anything starts, delivered by the founder, and your existing system stays running until cutover.
-
Week 0
Read the system as it is
We go through the existing application and record what it actually does, including the parts nobody documented. You get a written inventory and a fixed price before any build starts.
-
Weeks 1-N
Rebuild and run in parallel
The replacement runs beside the original until the numbers reconcile. The old system stays untouched and switched on the whole time.
-
Cutover
Go live and hand over
Cutover on a date you choose, then thirty days of support. Source code, documentation and credentials are handed to you, in your name.
What the work actually is
Rebuild it as something browsers still run
We work out what the application did, from the source project where it exists and from the compiled package where it does not, and rebuild it with standard web technology.
What you have now
- .xap Silverlight packages
- .swf and .fla Flash files
- The original source, sometimes
- An old browser on an isolated machine
Rebuild it as something browsers still run
We work out what the application did, from the source project where it exists and from the compiled package where it does not, and rebuild it with standard web technology.
See how a project runsWhat you end up with
- A browser application in HTML and JavaScript that needs no plugin
- The same interactivity, working on phones and tablets as well
- Content recovered even where the source project was lost
The 5 pieces of Silverlight / Flash work we are asked for
Most engagements are some combination of these, and most start with the first.
Recover what the application did
From the .fla or Silverlight project where the source survived, and by inspecting the compiled .swf or .xap where it did not.
Get the data out
Anything the application stored or cached locally is extracted before the old environment is retired.
Rebuild in standard web technology
HTML, CSS and JavaScript, so it runs in every current browser with no plugin and no compatibility mode.
Make it work on mobile
Neither Flash nor Silverlight ever ran on phones. Rebuilding is the point at which that finally gets fixed.
Preserve the content
Training modules and interactive material rebuilt rather than lost, which is often the real value in the asset.
Where you are now
It works, and nobody will touch it
- Flash Player unsupported since 31 December 2020
- Silverlight unsupported since 12 October 2021
- Reachable only through an old browser on an isolated machine
- Never worked on phones or tablets at all
After
Supported, documented and yours
- Runs in every current browser with no plugin
- Works on phones and tablets for the first time
- No isolated machine to maintain
- Content and interactivity preserved rather than abandoned
Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.
Get a fixed-price scopeSilverlight / Flash questions
Our Flash source files are long gone. Is it still recoverable?
Usually. A compiled .swf can be inspected to establish structure, assets and behaviour. It is more work than having the .fla, and it is a normal situation rather than a dead end.
Can it be made to run again as it is?
Not in any browser you should be using. Options that keep it alive involve unsupported browsers or emulation on isolated machines, which is a holding action, not a fix.
We have training modules built in Flash. Can those be saved?
Yes, and this is one of the most common versions of this job. The content and the interaction design are the valuable parts and both can be rebuilt in standard web technology.
Will it work on tablets afterwards?
Yes. Neither plugin ever ran on iOS or Android, so rebuilding is usually the first time the material becomes usable on the devices people actually have.
Is this urgent?
More than most items on this list, because the application is already unusable rather than merely unsupported. If a business process still depends on it, it is being worked around right now.
Sending your details…
You can stay on this page while we send it.
Tell us what you are running
What the system does, roughly how old it is, and what is forcing the question. We will come back with a straight answer and a fixed-price scope, even if the answer is to leave it alone.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.