Offboarding and Source Code Requests
We hope you're enjoying your experience with Ozone. We understand that when you're ready to take the next development step, you may request access to the source code of your apps developed on our platform. We want to clarify our policy regarding source code requests and the potential challenges associated with it.
Why Source Code May Not Be Easily Readable:
When you request access to the source code of your Ozone app post-changes, it's important to note that the source code generated by our platform may not be in a format that is easily readable or editable by developers. This is because Ozone relies on visual builders like Adalo (https://adalo.com) and Flutterflow (https://flutterflow.com), which utilize Flutter as the underlying development framework. It's important to note that while Flutterflow has an easy source code export, Adalo is significantly harder.
About Flutter:
Flutter is a powerful framework developed by Google, known for its efficiency and performance. However, the code generated by visual builders and frameworks like Adalo and Flutterflow may be highly abstracted and optimized for their specific purposes.
Reintegration Challenges:
Integrating external edits or modifications into the Ozone workflow can be a complex process. The code generated by Rehost is intricately tied to the visual elements and functionality of your app. When source code is altered externally, it may not seamlessly reintegrate into our platform.
Delays and Uncertainty:
Reintegrating modified source code into the Ozone environment can result in delays and may not be guaranteed to work as expected. The visual design and functionality of your app in Ozone are intricately linked to the original code generated by our platform. Any changes made externally may not align with the Ozone structure.
Our Suggestion:
If you anticipate the need for extensive code-level modifications or customizations to your app, we recommend discussing your requirements with us beforehand. We can explore alternative development approaches or strategies that align better with your specific needs.
Our Commitment:
At Ozone, we are committed to providing you with the best possible experience and ensuring the smooth operation of your apps. While we may not readily provide source code due to the complexity of its integration, we are always here to support you with any app-related issues or questions you may have.
If you have any concerns or specific requirements regarding your app's source code, please feel free to reach out to our support team. We'll be happy to discuss your needs and find the best solution for your project.
Thank you for choosing Ozone for your app development needs.
Best Regards,
The Ozone Team
Why Source Code May Not Be Easily Readable:
When you request access to the source code of your Ozone app post-changes, it's important to note that the source code generated by our platform may not be in a format that is easily readable or editable by developers. This is because Ozone relies on visual builders like Adalo (https://adalo.com) and Flutterflow (https://flutterflow.com), which utilize Flutter as the underlying development framework. It's important to note that while Flutterflow has an easy source code export, Adalo is significantly harder.
About Flutter:
Flutter is a powerful framework developed by Google, known for its efficiency and performance. However, the code generated by visual builders and frameworks like Adalo and Flutterflow may be highly abstracted and optimized for their specific purposes.
Reintegration Challenges:
Integrating external edits or modifications into the Ozone workflow can be a complex process. The code generated by Rehost is intricately tied to the visual elements and functionality of your app. When source code is altered externally, it may not seamlessly reintegrate into our platform.
Delays and Uncertainty:
Reintegrating modified source code into the Ozone environment can result in delays and may not be guaranteed to work as expected. The visual design and functionality of your app in Ozone are intricately linked to the original code generated by our platform. Any changes made externally may not align with the Ozone structure.
Our Suggestion:
If you anticipate the need for extensive code-level modifications or customizations to your app, we recommend discussing your requirements with us beforehand. We can explore alternative development approaches or strategies that align better with your specific needs.
Our Commitment:
At Ozone, we are committed to providing you with the best possible experience and ensuring the smooth operation of your apps. While we may not readily provide source code due to the complexity of its integration, we are always here to support you with any app-related issues or questions you may have.
If you have any concerns or specific requirements regarding your app's source code, please feel free to reach out to our support team. We'll be happy to discuss your needs and find the best solution for your project.
Thank you for choosing Ozone for your app development needs.
Best Regards,
The Ozone Team
Updated on: 05/02/2024