# iOS Extensions?

**URL:** https://community.thunkable.com/t/ios-extensions/3174
**Category:** Questions about Thunkable X
**Created:** [May 4, 2017, 1:41pm UTC](https://community.thunkable.com/t/ios-extensions/3174 "2017-05-04T13:41:12Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![ts02](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ts02/32/2013_2.png) [@ts02](https://community.thunkable.com/u/ts02)
#### Post date: [May 4, 2017, 1:41pm UTC](https://community.thunkable.com/t/ios-extensions/3174/1 "2017-05-04T13:41:12Z")

</div>

In the full version of iOS Thunkable, will we be able to create and use extensions?

---

<div class="post-metadata">

### Author: ![Helios](https://avatars.discourse-cdn.com/v4/letter/h/858c86/32.png) [@Helios](https://community.thunkable.com/u/Helios)
#### Post date: [May 4, 2017, 1:45pm UTC](https://community.thunkable.com/t/ios-extensions/3174/2 "2017-05-04T13:45:17Z")

</div>

It will definitely take a **_lot_** of time, considering that the iOS Alpha is still taking baby steps. Note that it has been only recently that extensions were added to the stable App Inventor server. Prior to that, you had to use a separate beta server ([extensions.appinventor.mit.edu](http://extensions.appinventor.mit.edu), if I remember right).

---

<div class="post-metadata">

### Author: ![ts02](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ts02/32/2013_2.png) [@ts02](https://community.thunkable.com/u/ts02)
#### Post date: [May 4, 2017, 1:47pm UTC](https://community.thunkable.com/t/ios-extensions/3174/3 "2017-05-04T13:47:44Z")

</div>

That’s why I’m saying in _the full version_. It might take years to complete at this rate, slowly but surely. 🙂

I remember AI2 without extensions, it wasn’t as easy to do complex things.

---

<div class="post-metadata">

### Author: ![Helios](https://avatars.discourse-cdn.com/v4/letter/h/858c86/32.png) [@Helios](https://community.thunkable.com/u/Helios)
#### Post date: [May 4, 2017, 1:49pm UTC](https://community.thunkable.com/t/ios-extensions/3174/4 "2017-05-04T13:49:18Z")

</div>

It depends on the kind of support iOS provides. Swift may be the way to go, but then the learning curve will be steep for most extension devs here who are used to Java. But yes, in a (near) distant future, this may happen.

---

<div class="post-metadata">

### Author: ![amrita](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/amrita/32/31_2.png) [@amrita](https://community.thunkable.com/u/amrita)
#### Post date: [May 5, 2017, 6:28pm UTC](https://community.thunkable.com/t/ios-extensions/3174/5 "2017-05-05T18:28:30Z")

</div>

Yes this is something we very much want to do, but it will take time.

---

<div class="post-metadata">

### Author: ![BillG](https://avatars.discourse-cdn.com/v4/letter/b/d78d45/32.png) [@BillG](https://community.thunkable.com/u/BillG)
#### Post date: [June 9, 2017, 11:19pm UTC](https://community.thunkable.com/t/ios-extensions/3174/6 "2017-06-09T23:19:01Z")

</div>

Hi @thunkable,

Just curious: What language will be used for the iOS extensions? I’m guessing the newer Swift? Or maybe the older Objective-C?

Thanks!  
BillG

---

<div class="post-metadata">

### Author: ![ILoveThunkable](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ilovethunkable/32/3134_2.png) [@ILoveThunkable](https://community.thunkable.com/u/ILoveThunkable)
#### Post date: [June 10, 2017, 7:09am UTC](https://community.thunkable.com/t/ios-extensions/3174/7 "2017-06-10T07:09:18Z")

</div>

They are using non of these languages, you may check out react-native.

---

<div class="post-metadata">

### Author: ![BillG](https://avatars.discourse-cdn.com/v4/letter/b/d78d45/32.png) [@BillG](https://community.thunkable.com/u/BillG)
#### Post date: [June 11, 2017, 12:49am UTC](https://community.thunkable.com/t/ios-extensions/3174/8 "2017-06-11T00:49:23Z")

</div>

Thanks @ILoveThunkable!  
BillG

---

<div class="post-metadata">

### Author: ![itmanager](https://avatars.discourse-cdn.com/v4/letter/i/edb3f5/32.png) [@itmanager](https://community.thunkable.com/u/itmanager)
#### Post date: [January 23, 2019, 7:07am UTC](https://community.thunkable.com/t/ios-extensions/3174/9 "2019-01-23T07:07:51Z")

</div>

Any news???

---

<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: [January 13, 2020, 9:29am UTC](https://community.thunkable.com/t/ios-extensions/3174/10 "2020-01-13T09:29:40Z")

</div>

The main problem with adding extensions and additional functionality is associated with Apple, because the employees of this company are not going to provide anyone with the opportunity to create high-quality applications for free. Do you want to create quality applications for free or on a commercial basis for iOS? Pay at the cash desk of Apple for Mac and for everything else.

Thunkable X provides the option to not pay for a Mac. Does this suit Apple? So far it’s fine, but will Apple be happy if Thunkable X is a very good platform with which so many people can create high-quality applications for free? No, because Apple, first of all, needs money, and the applications on the App Store are needed by this company in order to make money, and not in order to make the world happy with high-quality free applications.

I think that there is a way to add source code to the project instead of using extensions, which will not contradict Apple rules. But I’m also sure that despite following the rules, Apple reserves the right to reject applications that simply do not suit them. And there are always reasons for this.

---

<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, 11:46am UTC](https://community.thunkable.com/t/ios-extensions/3174/11 "2024-11-08T11:46:01Z")

</div>


