Changes beyond the supplied functionality should be planned as a separate development project. Contact the author through the item’s listed channel to ask whether customization services are currently available, or work with a qualified Flutter/Perfex developer.
Describe the business problem, the affected users, and the expected outcome. Include the current app/API versions, relevant screenshots, desired platforms, and any existing customizations.
For example, “Add a customer-visible project document section with the same ownership restrictions as existing project files” is more useful than “add more features.”
Before work begins, agree on deliverables, acceptance criteria, cost, timing, source-code handover, maintenance responsibilities, and how future vendor updates will be handled. Clarify whether the work includes backend changes, migration, translations, tests, or store submission.
New customer-facing API functionality must enforce authentication, contact permissions, and customer ownership on the server. A new mobile screen alone cannot safely expose staff-only records.
Keep changes under version control and test them against the supported release combination. Record which files and API contracts changed so future updates remain manageable.
Customization availability, pricing, and delivery dates require a separate agreement. Do not assume that purchasing an Extended License includes custom development or that the source-code purchase covers a new feature request.