Migration from Manifest V2 to Manifest V3.

Miguel Larreategui

(0)

Contact for pricing

About this service

Summary

Every extension codded with manifest V2 standars will stop working on chrome browsers mainly due to XSS vulnerabilities.

In order to mantain them they should be migrated to Manifest V3, all the architecture will be updated to meet the new requirements, cyber-security revised and cache memory, cookies, etc... re-mamaged. This is not an easy process, exponentially difficult the more complex the original extension is, and requieres expertise to carry out the process successfully.

Process

Requirements analysis: The original extension is submitted and a meeting is held to discuss the main funcionalities it has, where and when it works.

Calendar planning: After a thorough review, I present to you a course of action, milestones and a final budget.

Architecture: When the previous phases are complete a redesign of the architecture of the extension is created and presented to the customers.

Funcionalities implementeations: One by one each and every funcionality it previously had is implemented, and sent to test by the customer.

Final product (Phase 1): The final product is send to test by the customer, if any errors are found within the first 20 days of use they are patched for free. This step could have more than 1 phase if bugs are found.

Payday: 20 days period without trouble after the last phase Final Product, the paid is made.

FAQs

Can you add more funcionalities to the extension?
It's not a part of the service, but depending on the functionality itself it can be discussed and ajusted in the Requirements analysis phase.
Can you migrate extensions from the oficial chrome-extensions page?
Only if the source code is provided and a license or direct authoritation from the original author is provided.

What's included