Understanding Apple’s Restrictions on Live Activities & Dynamic Island When I wrote the previous thread, I didn’t know it.
Hey everyone,
I wanted to share something I recently learned about
Apple’s restrictions on certain iOS features, specifically
Live Activities and
Dynamic Island. Initially, I wasn’t aware that Apple imposes strict limitations on how these technologies can be implemented, but after diving deeper, it makes a lot more sense now.
Apple’s Control Over Live Activities & Dynamic Island
Apple ensures that
Live Activities (which provide real-time updates on the Lock Screen and Dynamic Island) can only work via their own frameworks, primarily
ActivityKit and
WidgetKit. This means that
third-party development tools like B4I don’t have direct access to them unless Apple allows it explicitly.
At first, I was looking for a way to integrate these features into B4I, but now I understand that Apple restricts their usage to
Swift and SwiftUI, making it
impossible to implement them natively in B4I without bridging through an external Swift framework.
Possible Workarounds?
Given these restrictions, it seems that the
best way to interact with Live Activities in B4I would be:
-
Building a Swift framework that handles Live Activities and interacts with B4I via NativeObject. 2-
Using notifications & floating views to create a similar experience.
This definitely changes how I approach integrating iOS-specific features in B4I. While we can't use
ActivityKit natively, understanding these limitations helps set realistic expectations.
Has anyone successfully integrated something like this with a custom Swift framework? I’d love to hear your experiences or possible alternatives!
