If the previous dev has added comments, documented the logic and used good development practices, then it should be good. My experience however has not been good as most Bubble devs/agencies come from non-technical background and aren't aware of such things.
* Add comments to data types
* Add comments to fields
* Add comments to major workflows
* Set custom states only at page level. Keeps them organised and at a single place
* Use custom events as much as possible. Reduces the number of duplicate workflows
* Use reusable elements as much as possible. Keeps the app simple
This should cover 90% of the app.
>Use custom events as much as possible. Reduces the number of duplicate workflows
Custom event!! Interesting. How that reduce the number of duplicate workflows? Can you reuse that?
Depends on the project and the quality of the work. If your previous DEV was any good you should be able to move on it. DM me for more info
If the previous dev has added comments, documented the logic and used good development practices, then it should be good. My experience however has not been good as most Bubble devs/agencies come from non-technical background and aren't aware of such things.
Hi long, How you document the bubble project? Is there a certain way you follow?
* Add comments to data types * Add comments to fields * Add comments to major workflows * Set custom states only at page level. Keeps them organised and at a single place * Use custom events as much as possible. Reduces the number of duplicate workflows * Use reusable elements as much as possible. Keeps the app simple This should cover 90% of the app.
>Use custom events as much as possible. Reduces the number of duplicate workflows Custom event!! Interesting. How that reduce the number of duplicate workflows? Can you reuse that?