# \[Video Tutorial\] - Don't Repeat Yourself: Abstracting Repetitive Tulip Steps into Separate Apps

**URL:** <https://community.tulip.co/t/video-tutorial-dont-repeat-yourself-abstracting-repetitive-tulip-steps-into-separate-apps/9878>\
**Category:** Show and Tell\
**Created:** [November 20, 2023, 9:54pm UTC](https://community.tulip.co/t/video-tutorial-dont-repeat-yourself-abstracting-repetitive-tulip-steps-into-separate-apps/9878 "2023-11-20T21:54:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [November 22, 2023, 11:06am UTC](https://community.tulip.co/t/video-tutorial-dont-repeat-yourself-abstracting-repetitive-tulip-steps-into-separate-apps/9878/3 "2023-11-22T11:06:49Z")

</div>

I hope Tulip will eventually provide native support for running other apps “on top” of a main app. This would make development much more efficient and less convoluted.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/c/ca60f75fa6590c18c8d0bbb2c56d89f94982037f.png)

And each app should have access to the other apps last state after a jump has occurred and have access to or reference a copy in the log.

The completions could still be logged individually per app in addition to that.

That would open a new world because you could offload common tasks to dedicated apps or “modules” that together then build an entire app.

The “workaround” suggested in the video currently breaks the single trail record idea.

---

_[View the full topic](https://community.tulip.co/t/video-tutorial-dont-repeat-yourself-abstracting-repetitive-tulip-steps-into-separate-apps/9878)._