# Critical Bug Report & Platform Limitations: Impossible to Implement a Functional Custom Video Player

**URL:** <https://community.thunkable.com/t/critical-bug-report-platform-limitations-impossible-to-implement-a-functional-custom-video-player/4044102>\
**Category:** Issues / Bugs\
**Tags:** help, bug, web-viewer\
**Created:** [July 31, 2025, 1:18pm UTC](https://community.thunkable.com/t/critical-bug-report-platform-limitations-impossible-to-implement-a-functional-custom-video-player/4044102 "2025-07-31T13:18:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![linfanziaguaritavy0p](https://avatars.discourse-cdn.com/v4/letter/l/b5ac83/32.png) [@linfanziaguaritavy0p](https://community.thunkable.com/u/linfanziaguaritavy0p)\
**Post date:** [July 31, 2025, 1:18pm UTC](https://community.thunkable.com/t/critical-bug-report-platform-limitations-impossible-to-implement-a-functional-custom-video-player/4044102/1 "2025-07-31T13:18:04Z")

</div>

Hello,

I am writing to report a critical, blocking issue that prevents the implementation of an essential feature for my application: a fullscreen, audio-enabled intro video without the default player controls.

After an intensive and thorough troubleshooting process, we have concluded that the goal is unachievable due to critical bugs and inherent limitations of the Thunkable components.

* * *

#### **Detailed Goal**

The objective was to use the **Web Viewer** component to display a custom HTML page that would:

1. Play a video hosted on Cloudinary in fullscreen.

2. Not display the native progress bar or player controls.

3. Start with audio after a user interaction (a tap on the screen).

4. Send a `postMessage` to the app upon video completion to navigate to another screen.

* * *

#### **Troubleshooting Path and Attempted Solutions**

We have systematically tested every possible approach, encountering critical failures at every step:

1. **Attempt 1: Thunkable’s Native Video Player**

2. **Attempt 2: Web Viewer with External Hosting**

3. **Attempt 3: Web Viewer with a `data:` URI (The Definitive Test)**

* * *

#### **Technical Conclusion**

The following analysis summarizes the situation for your technical team:

- **Summary of Issues:**

- **Conclusion and Question:** These exhaustive attempts suggest inherent limitations of the Thunkable platform. Given that the native Video Player component is unsuitable due to bugs and that the Web Viewer blocks all viable methods for deploying a custom player, **what is the officially supported and stable method to achieve a professional, custom video player implementation on Thunkable?**

We await your feedback and a practical solution to this blocking problem.

Thank you for your time.