# Unused screen with blocks: Is this a bug risk at build?

**URL:** <https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249>\
**Category:** Questions about Thunkable X\
**Created:** [August 26, 2020, 2:04am UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249 "2020-08-26T02:04:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![penny](https://avatars.discourse-cdn.com/v4/letter/p/8baadc/32.png) [@penny](https://community.thunkable.com/u/penny)\
**Post date:** [August 26, 2020, 2:04am UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249/1 "2020-08-26T02:04:05Z")

</div>

If I have a screen in development which has components and blocks, but I am not sure whether to use it or not, I can direct navigation around it. It is isolated from the flow (something like commenting out a bit of code that you don’t want to use OR delete). But, **is this a potential source of bugs for a built app?** Is it better to just delete the screen, or save it to myScreens? I have asked this question before but it got buried in lots of other issues that were happening at that time. Thus, there was never an answer.  
Thx

---

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [August 26, 2020, 4:28am UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249/2 "2020-08-26T04:28:36Z")

</div>

There shouldn’t be any problem with an extra non-visitable screen as long as you don’t have things like variable definitions that conflict with other screens or blocks that affect code on other screens.

So I would say no harm keeping it. It shouldn’t introduce bugs. But in terms of efficiency, you’d probably want to delete it from the completed app if it’s really not needed.

---

<div class="post-metadata">

**Author:** ![actech](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@actech](https://community.thunkable.com/u/actech)\
**Post date:** [August 26, 2020, 6:26am UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249/3 "2020-08-26T06:26:29Z")

</div>

It makes sense to save the screen separately when its functionality can be used in different projects. Otherwise, it is better to leave the screen in this project, but make a copy of this project without this screen before publishing it. This way, you will always have a project version to work with and debug, and a clean version to publish. You should not leave an unnecessary screen in the published app.

---

<div class="post-metadata">

**Author:** ![penny](https://avatars.discourse-cdn.com/v4/letter/p/8baadc/32.png) [@penny](https://community.thunkable.com/u/penny)\
**Post date:** [August 27, 2020, 1:22am UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249/4 "2020-08-27T01:22:22Z")

</div>

Great. Thanks for the tips.  
🙂

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [November 8, 2024, 12:24pm UTC](https://community.thunkable.com/t/unused-screen-with-blocks-is-this-a-bug-risk-at-build/769249/5 "2024-11-08T12:24:37Z")

</div>