# Method for Common Development across Multiple Applications

**URL:** <https://forums.losant.com/t/method-for-common-development-across-multiple-applications/5676>\
**Category:** Help\
**Tags:** versioning, application\
**Created:** [November 7, 2024, 4:23pm UTC](https://forums.losant.com/t/method-for-common-development-across-multiple-applications/5676 "2024-11-07T16:23:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\
**Post date:** [November 7, 2024, 4:23pm UTC](https://forums.losant.com/t/method-for-common-development-across-multiple-applications/5676/1 "2024-11-07T16:23:59Z")

</div>

I have two applications today, one that represents devices in a production fleet, and a second that represents a development fleet. I think I’d like to develop workflows/dashboards/experiences. in the development application, where there is little risk of disturbing the production environment, and export/import the latest releases to the production application once new workflows/dashboards/experiences are ‘ready for production’

Is the concept of keeping dev and prod as separate applications flawed? I can appreciate the effort taken to create version control at the workflow/etc level inside a given application, and don’t want to create a design that is counter to Losant’s intended implementation.

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [November 7, 2024, 4:33pm UTC](https://forums.losant.com/t/method-for-common-development-across-multiple-applications/5676/2 "2024-11-07T16:33:00Z")

</div>

You are referring to what we call “Application Lifecycle”, which uses the export/import features exactly as you described. In most cases, application lifecycle replaces the per-resource version control features. We have a full guide here:

> **[How To Use Import Features to Manage an Application Development Lifecycle](https://docs.losant.com/guides/how-to-use-import-features-to-manage-an-application-development-lifecycle/)**
>
> Learn how to use Losant's application import functionality to promote changes from staging applications to your production solution.

---

<div class="post-metadata">

**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\
**Post date:** [November 8, 2024, 3:48am UTC](https://forums.losant.com/t/method-for-common-development-across-multiple-applications/5676/3 "2024-11-08T03:48:02Z")

</div>

Brandon, this is exactly what I was looking for. I had noticed the exported files were organized super-convenient for use with GitHub; now I see that was totally intentional. This was a good read, thank you for the response.