Skip to main content

👋 Hello team, I’m Rotem the Apps Framework Product Manager

As part of our ongoing efforts to simplify your app development process and enhance collaboration among multiple developers working on the same app, we're working on new guidelines for managing draft versions - and we’d love to get your feedback.

These guidelines are shaped by many insightful conversations with you, and we believe this approach will help streamline the overall developer experience:

✅ Proposed Workflow for Single- and Multi-Collaborator Apps

  1. Developers will build and test their app using a dedicated development account. 
  2. The main monday.com account will host both the staging (draft) and production (live) versions of the app. In other words, the draft version in this account will be used as the staging environment, and the live version as production.
  3. Each app will have only one draft version and one live version in every account. Multiple draft versions will no longer be allowed.
  4. To sync app changes from the development environment to staging and production:
    a. Create the manifest file by using the export manifest CLI command in the development environment.
    b. Use git diff to compare the previous manifest file with the new one.
    c. Use the import manifest CLI command to update the app in staging and production.

    Going forward, we will also add GitHub Actions to support this in your CI/CD flow.

We’d love to hear your thoughts:

  • Does this flow align with your current development practices?
  • Is there anything you'd like us to adjust or clarify?

Thanks again for your ongoing feedback and collaboration 🙌

Hey Rotem,

How would this affect apps that use the sentance recipes as I don’t believe these are currently supported by the manifest file?

 

Would it still be a manuall creation to the staging/production app?

 

Hey ​@mitchell.hudson , 
The integration sentence builder app feature is indeed not supported by the manifest file. Alternatively, you can use the new integration for workflow block — our stable and scalable infrastructure for supporting automations — which is supported by the manifest file. 

Thanks,

Rotem

Thanks Rotem,

We use workflow actions in other apps, however not all plans have workflows enabled, what if they are building apps for the lower tiered accounts? Or need our apps to support those lower tiered accounts?

I know there is a process coming to convert sentance builder recipes into workflow actions, is that part of this as well?

 

Hi ​@rotemin 

How about the use case where multiple developers are working on the same app feature. Currently we have a draft version per developer so they can point that draft to their local setup and test. 

If only one draft version remains, only one developer can work/test locally at the same time.

Is this use case being taken into account?

Best,

Maarten

Hey ​@mitchell.hudson , 
The integration sentence builder app feature is indeed not supported by the manifest file. Alternatively, you can use the new integration for workflow block — our stable and scalable infrastructure for supporting automations — which is supported by the manifest file. 

Thanks,

Rotem

Are sentence builder app features deprecated? Should we cease further app development on them? What options for automations and integrations are there then for non-enterprise accounts?

Reply


Terms & ConditionsCookie settings