Bugfixes
Last week, we focused heavily on resolving issues related to Platformer’s Telegram application launcher—and made significant progress.
While we addressed some critical problems within the launcher itself, we also identified and resolved issues tied to both Telegram for macOS and Telegram Web K. These platforms either don’t support certain Mini App methods or handle them incorrectly. In short, the problems stem from long-standing bugs within the clients themselves.
Since one of the launcher's goals is to shield developers from platform-specific inconsistencies, it now handles these issues gracefully—so you don’t have to.
If you’re curious about what exactly behaves incorrectly in the Telegram clients, here’s a breakdown:
— Telegram for macOS: The client emits an event called
content_safe_area_changed instead of the expected safe_area_changed when the web_app_request_safe_area method is called. If you’re using @telegram-apps/sdk and mounting the viewport, your app may freeze. Additionally, the client does not emit the theme_changed event in response to the web_app_request_theme method.— Telegram Web K: This client does not support the
web_app_request_content_safe_area or web_app_request_safe_area methods at all.Improvements
— The applications list UI has been slightly redesigned, including a hint about the maximum number of apps allowed.
— You can now delete apps directly from the app information section.
— The app managers list has been reworked for better clarity.
— A new hint has been added to the app URLs page explaining how they function.
— Test group creation and update UIs have been improved. You can also now delete test groups.
We’ll continue focusing on UI/UX improvements over the next week or two to enhance your experience. After that, we’ll be sharing more about our future plans.
Thanks for building with Platformer! 🦄