Reengineering Adobe Flash to HTML5 fi

Reengineering Adobe Flash To HTML5: Top Tips.

December 31, 2020, will mark a watershed moment in technology – the point at which Adobe ends support of Flash Player and it is removed by all browsers. This is not a shocking development – it was announced back in 2017, but there are still many organisations that need to re-build their product applications in HTML5 by the end of the year or risk their services no longer working at all.

Organisations that will fall foul of the change are those organisations that provide services or software via browser-based extensions – the most vulnerable being e-learning, psychometric businesses and analytics organisations. Businesses that fall into those categories will have courses, animations, apps and other digital content published in Adobe Flash and must now look to convert their assets to HTML5 which will address new modern designs.

Why Adobe Flash to HTML5?

There are a number of features that HTML5 has over and above the use of Flash, but most significantly, HTML5 is mobile-ready where Flash was difficult to view on mobile devices. It responds to content and automatically adjusts on devices, making it much more user-friendly. It also isn’t as battery hungry as Flash, so is a better choice for mobile users.

Next Steps

Reengineering Adobe Flash to HTML5 1

Where organisations have Adobe Flash, it’s important within the time frame to put together an action plan to convert assets to HTML5. We recommend the following as an outline for consideration when deciding what to convert.

1 Decide if its more relevant to retire the asset or whether you want to convert it to HTML5 – do you still need it/use it/have a use for it in the future?

2 Do you have the source files to be able to redevelop the asset? If you don’t have them, you may be forced to replace it altogether.

3 Where you do have source files, it is possible to convert the asset, but you may decide to take a portion of what’s there and use it, or redesign/revamp it in some way. It depends upon the complexity of the existing Flash.

4 Put together a comprehensive list of which assets will be converted and to what extent, and create a list of standard settings for all developers to refer to during the conversion process, making things more streamlined once underway.

5 Consider if you have the resources to make the changes in the timeframe – the end of 2020 – can you convert them fast enough to meet the deadline?

Resources available

If the assets are business-critical and exist in numbers, it may be wise to consider how as an organisation you will re-engineer them both fast and efficiently. Business as usual tasks often take precedence for software development teams and bringing resources off strategic or critical work is simply not possible.

Likewise ramping up an in-house team takes time and hiring contractors from April 2020 becomes more problematic thanks to IR35 tax regulation that prevent full-time contractors being treated as ‘external’ consultants for tax reasons. Plus, reengineering Flash to HTML5 is a one-off requirement – and using a partner organisation means that resources can be ramped up in line with the demand for developers, but also scaled back upon project completion.

If you have a requirement to redevelop Flash into HTML5, please get in touch.