# Bugs on content format (Mobile)

**URL:** <https://forum.bubble.io/t/bugs-on-content-format-mobile/386903>\
**Category:** Mobile Beta - bugs\
**Created:** [December 7, 2025, 12:03pm UTC](https://forum.bubble.io/t/bugs-on-content-format-mobile/386903 "2025-12-07T12:03:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergiofojr](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sergiofojr/32/161736_2.png) [@Sergiofojr](https://forum.bubble.io/u/Sergiofojr)\
**Post date:** [December 7, 2025, 12:03pm UTC](https://forum.bubble.io/t/bugs-on-content-format-mobile/386903/1 "2025-12-07T12:03:51Z")

</div>

**Hello everyone, good morning!**

Since this issue has been known since **December 2024** — [[General Feedback] - Inputs ](https://forum.bubble.io/t/general-feedback-inputs/351000)— and we are now closing a full year with the same problem **without a solution** , I believe it is fair and reasonable to treat this demand with more attention.

Bubble is used in my platform by **2,000–3,000 daily users** , and the biggest differentiator of my SaaS, according to my customers, is the attention to detail in **UX and UI**.

How can I offer something that is supposed to be our strongest point (UX/UI) if the inputs simply do not format correctly on mobile (forcing me to create workarounds that shouldn’t be necessary), especially when everything works perfectly on web development? Besides causing extra stress for my support team, it leaves me with my hands tied. My SaaS relies heavily on inputs that use formats like **“R$”** and **“%”**.

I understand that Mobile is a **BETA version** , and naturally some bugs are expected. However, it feels like negligence when a known bug persists for **12 months** without being prioritized. I have seen other posts, I have spoken with the support chat, I have submitted bug reports — and yet, after a full year, this still isn’t being treated as a priority.

Please, provide a consistent and transparent update.  
We have been discussing the same issue for **12 months** , and it is becoming increasingly difficult to justify this limitation to our own customers

Thanks @Newed  
FYK @emmanuel @josh @nick.carroll @fede.bubble

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/f/c/fcd91ea6f2fdfddf652b84f0bbb55f0ffb80e296.png)

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/6/1/61a03df79ac11865aa8b20c942ef7c38cf9b158a.png)

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [December 11, 2025, 7:18pm UTC](https://forum.bubble.io/t/bugs-on-content-format-mobile/386903/2 "2025-12-11T19:18:05Z")

</div>

Shared this with the team. They are probably aware already but good to remind them, thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [December 21, 2025, 12:04pm UTC](https://forum.bubble.io/t/bugs-on-content-format-mobile/386903/4 "2025-12-21T12:04:11Z")

</div>

This topic was automatically closed after 14 days. New replies are no longer allowed.