# December 18, 2025 / 🎁 Fibery iOS and Android apps, Custom Database access, Stripe integration, Architect mode

**URL:** <https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183>\
**Category:** Changelog\
**Created:** [December 18, 2025, 12:52pm UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183 "2025-12-18T12:52:38Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\
**Post date:** [December 19, 2025, 3:32pm UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/21 "2025-12-19T15:32:30Z")

</div>

What an amazing release this week, awesome job Fibery team!! It might seem small compared to the other features this week, but I’ve been really appreciating this tabs upgrade, it feels so much better to work with.

One small tab-related wishlist item I have for future tab improvements is the ability to load a tab in the background. If I middle-click or ctrl-click to create a new tab without going to it, it won’t load that page until I click on it and I have to wait the 2-3 seconds for the page to load. Even just loading the name on the tab would be nice.

---

<div class="post-metadata">

**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\
**Post date:** [December 19, 2025, 7:17pm UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/22 "2025-12-19T19:17:57Z")

</div>

> [@mdubakov](#):
>
> Discover it in Experimental features and find out what it does by yourself

This is actually quite useful, and a fairly clean solution.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [December 20, 2025, 3:51am UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/23 "2025-12-20T03:51:24Z")

</div>

Great release! I am unreasonably pleased to see all the fixes in Rich Text, hah. But for the love of god can I have _some_ way (besides right-clicking, apparently) to close an entire “tab set” in the desktop app? I continue to hate the dual-tab display in the tab bar, or at least the dual close-button function. Do people really prefer it that way? I don’t get it. But at least I should be able to hold e.g. Cmd or Ctrl or something when clicking Close and have it close both. Conflating “tabs” and “open/close” and “back/forward” is a little nutty if you ask me.

---

<div class="post-metadata">

**Author:** ![alex](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex/32/52_2.png) [@alex](https://community.fibery.io/u/alex)\
**Post date:** [December 20, 2025, 9:21am UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/24 "2025-12-20T09:21:48Z")

</div>

I remember your issue. At the moment, this is just a visual update of the tabs. We will make it possible to close them with a single click. If there is more feedback about this behavior, we will remove it, it was an experiment that may be rolled back.

Note: even Google Chrome released similar behavior for the panel view about a week ago.

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [December 22, 2025, 11:27am UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/25 "2025-12-22T11:27:19Z")

</div>

> [@mdubakov](#):
>
> You may think that last release of the year should be somewhat significant. Unfortunately, this is not the last release of the year.

Looking forward to coming Thursday as I think it should be somewhat significant 😁

This week’s one surely was significant as well. Mobile, Custom Database access… great stuff!

---

<div class="post-metadata">

**Author:** ![ebell](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ebell/32/1293_2.png) [@ebell](https://community.fibery.io/u/ebell)\
**Post date:** [December 26, 2025, 8:43pm UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/26 "2025-12-26T20:43:42Z")

</div>

> [@mdubakov](#):
>
> These are good news, but we have to replace Pinned filters and it is not easy. As a result, we will **❌ unpin all _Pinned_ filters that have OR condition in the filter setup** next week.

I have a lot of Pinned filters with an OR condition. Is there a way to identify and fix all the views where these will be disabled?

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [December 26, 2025, 9:07pm UTC](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183/27 "2025-12-26T21:07:15Z")

</div>

> [@ebell](#):
>
> Is there a way to identify and fix all the views where these will be disabled?

What fix would you plan to make if it were possible to identify them?

The pinned OR filters will be unpinned but otherwise unchanged.

[Previous page](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183.md?page=1)
