# EM Desktop - Best practice with a lot of processes

**URL:** <https://community.easymorph.com/t/em-desktop-best-practice-with-a-lot-of-processes/6123>\
**Category:** Support\
**Created:** [April 17, 2025, 8:48am UTC](https://community.easymorph.com/t/em-desktop-best-practice-with-a-lot-of-processes/6123 "2025-04-17T08:48:47Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![WindBlast](https://community.easymorph.com/letter_avatar_proxy/v4/letter/w/74df32/32.png) [@WindBlast](https://community.easymorph.com/u/WindBlast)\
**Post date:** [April 17, 2025, 12:01pm UTC](https://community.easymorph.com/t/em-desktop-best-practice-with-a-lot-of-processes/6123/3 "2025-04-17T12:01:20Z")

</div>

Thank for your answer.

Of course we already use the action "call anorther module/project", and it's amazing 😉

I think we will just need to take some time to look at how we can build the project, because yes you are true, each part need to be readable for any future worker.  
I was asking if there is any recommendation in the usage of EasyMorph Desktop, because some tools can be a mess depending on how you build a project.  
But with my experience and your answer, I think any solution could be good.

Thank you

---

_[View the full topic](https://community.easymorph.com/t/em-desktop-best-practice-with-a-lot-of-processes/6123)._