# Question about using Any Component to create new components and saving them to a Database **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [January 2, 2020, 3:47pm UTC](https://community.thunkable.com/t/question-about-using-any-component-to-create-new-components-and-saving-them-to-a-database/389216 "2020-01-02T15:47:01Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![domhnallohanlon](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/domhnallohanlon/32/29554_2.png) [@domhnallohanlon](https://community.thunkable.com/u/domhnallohanlon)\ **Post date:** [January 4, 2020, 1:28am UTC](https://community.thunkable.com/t/question-about-using-any-component-to-create-new-components-and-saving-them-to-a-database/389216/12 "2020-01-04T01:28:54Z")
here’s an example of this working with cloud variables now: > [@Where does Thunkable Live belong in your development workflow?](http://community.thunkable.com/t/where-does-thunkable-live-belong-in-your-development-workflow/390641): > > Thunkable Live is a super useful tool to speed up your app development cycle. Like any tool, there are some things it’s really good at, but you can’t use it for everything. Here’s my take on where Thunkable Live fits into a typical app development life cycle, followed by a more in-depth comparison. Sketching Prototyping Thunkable Live Emulator Installing Sketching Whether your using pen and paper or you have a whiteboard and some dry erase markers, there’s really no substitute for… There are a small few improvements to make in terms of UX, but if a switch is toggled on one device, that same switch will toggle on every device. Hope that helps! --- _[View the full topic](https://community.thunkable.com/t/question-about-using-any-component-to-create-new-components-and-saving-them-to-a-database/389216)._