# Suggestion for Progress Bar

**URL:** <https://community.thunkable.com/t/suggestion-for-progress-bar/4108799>\
**Category:** Questions about Thunkable X\
**Tags:** progress\
**Created:** [July 17, 2026, 6:13pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799 "2026-07-17T18:13:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![majidfareed1977](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@majidfareed1977](https://community.thunkable.com/u/majidfareed1977)\
**Post date:** [July 17, 2026, 6:13pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/1 "2026-07-17T18:13:54Z")

</div>

I was looking into ways to implement a progress bar and came across an approach that I think could work well as an off-the-shelf solution.

I used a **Slider** in **disabled** mode. By default, I set:

- `Disabled = true`
- `Visible = false`

Whenever I need to display progress, I simply set `Visible = true`.

The nice part is that, each time I use it, I can dynamically set the **minimum** and **maximum** values in the blocks. Then, after each completed step, I manually update the slider’s value until it reaches the maximum. Visually, it works quite well and gives the appearance of a standard progress bar.

I’d be interested to hear your thoughts. Do you see any drawbacks or limitations that I might have overlooked?

 ![slidebar](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/b/3/b3364bc5a79a6368b3909ac651e834c2b41f4355.jpeg)

---

<div class="post-metadata">

**Author:** ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)\
**Post date:** [July 20, 2026, 7:44pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/2 "2026-07-20T19:44:22Z")

</div>

Is there a reason you want to use stored variables compared to app variables?

---

<div class="post-metadata">

**Author:** ![majidfareed1977](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@majidfareed1977](https://community.thunkable.com/u/majidfareed1977)\
**Post date:** [July 20, 2026, 8:08pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/3 "2026-07-20T20:08:51Z")

</div>

When the app starts it load huge database for the first time, so I wanted to save it in local mobile storage in order not to load it again unless there is a change in the database. The change is detected through a checksum value in the google sheet where my database is.

---

<div class="post-metadata">

**Author:** ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)\
**Post date:** [July 20, 2026, 8:51pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/4 "2026-07-20T20:51:37Z")

</div>

Sounds reasonable. In that case, despite its looks, your blocks seem fine. I don’t see any limitations with the setup.

---

<div class="post-metadata">

**Author:** ![majidfareed1977](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@majidfareed1977](https://community.thunkable.com/u/majidfareed1977)\
**Post date:** [July 20, 2026, 8:07pm UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/5 "2026-07-20T20:07:33Z")

</div>

When the app starts it load huge database for the first time, so I wanted to save it in local mobile storage so that it is not loaded again unless there is a change in the database. The change is detected through a checksum value..

**…**  
**Best Regards,**

**Majid FAREED**

---

<div class="post-metadata">

**Author:** ![majidfareed1977](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@majidfareed1977](https://community.thunkable.com/u/majidfareed1977)\
**Post date:** [July 21, 2026, 5:18am UTC](https://community.thunkable.com/t/suggestion-for-progress-bar/4108799/6 "2026-07-21T05:18:10Z")

</div>

Is there any better way to implement routine?