# FirstRun Screen on Published Web App

**URL:** <https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378>\
**Category:** Questions about Thunkable X\
**Created:** [October 30, 2020, 4:12pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378 "2020-10-30T16:12:17Z")\
**Posts on this page:** 6\
**Page:** 1

<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:** [October 30, 2020, 4:12pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/1 "2020-10-30T16:12:17Z")

</div>

I’ve read that having an uninitialized _stored_ variable can cause a project published as a Web App to crash. And I’ve experienced that. I have a stored variable called FirstRun that is null and then changes to true after the app has started. That way, I can show an intro screen once to users and then never again.

Is there a way to do that on a Web App without it crashing?

---

<div class="post-metadata">

**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\
**Post date:** [October 30, 2020, 4:22pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/2 "2020-10-30T16:22:20Z")

</div>

What about using a cloud variable for screens after a signup/login or local storage for before a sign in screen?

---

<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:** [October 30, 2020, 4:22pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/3 "2020-10-30T16:22:28Z")

</div>

I figured out a workaround. I created a new screen that says “If platform is web” navigate to main screen else navigate to FirstRun Screen (which checks the _stored_ variable). So I bypass the check on the stored variable and the Web App no longer crashes.

---

<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:** [October 30, 2020, 4:22pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/4 "2020-10-30T16:22:41Z")

</div>

Hmm… haven’t tried that.

---

<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:** [October 30, 2020, 4:24pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/5 "2020-10-30T16:24:46Z")

</div>

> [@jared](#):
>
> What about using a cloud variable for screens after a signup/login or local storage for before a sign in screen?

A cloud variable works as a Web App. Thank you, @jared!

---

<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:21pm UTC](https://community.thunkable.com/t/firstrun-screen-on-published-web-app/941378/6 "2024-11-08T12:21:53Z")

</div>