# Feature Requests

**URL:** <https://community.thunkable.com/t/feature-requests/64316>\
**Category:** Questions about Thunkable X\
**Tags:** feature-requests\
**Created:** [January 12, 2019, 1:53pm UTC](https://community.thunkable.com/t/feature-requests/64316 "2019-01-12T13:53:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jane](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jane/32/27575_2.png) [@jane](https://community.thunkable.com/u/jane)\
**Post date:** [June 27, 2019, 4:56pm UTC](https://community.thunkable.com/t/feature-requests/64316/3 "2019-06-27T16:56:08Z")

</div>

Hi Steve,

You can read about adding animations to your app [here](https://docs.thunkable.com/lottie).  
Thunkers have had success using .gif files as background images of components!

Users can edit the splash screen in PRO by [changing their app icon](https://docs.thunkable.com/app-icon-+-name).

We’re still working on the Text Input focus!

You can use true/false variables to disable a Button without making it grey.

> [@Is there a way to disable button WITHOUT shading to grey?](http://community.thunkable.com/t/is-there-a-way-to-disable-button-without-shading-to-grey/110296/2):
>
> You will evidently need a few more blocks, but not a ton. The idea is that, instead of disabling the button, you set a global variable, let’s call it “enable\_button” and set it by default to true. When the button needs disabling, you set that variable to false instead of actually disabling the button. Then in the button.click event block, you enclose ALL of the processing in a conditional block “if enable\_button do”. If the user clicks the button when enabled, which is the default, it works n…

---

_[View the full topic](https://community.thunkable.com/t/feature-requests/64316)._
