PipeKit
Remotely trigger Swift functions and replay iOS sessions
Start new thread
Al Moutasem Nabil

PipeKit - Remotely trigger Swift functions and replay iOS sessions

by•
PipeKit is in private beta. Trigger remote actions, compose flows, and replay sessions on production iOS devices, without shipping an app update. Join the waitlist.

Add a comment

Replies

Best
Al Moutasem Nabil
Maker
📌
Hey PH! I'm Almoutasem, a Senior iOS Developer working on enterprise POS apps serving 30,000+ restaurants. I built PipeKit because I was tired of waiting days for App Store review just to toggle a feature or debug a production issue. PipeKit gives you three things: 1. Remote function orchestration: Annotate your Swift code with @Rewire and @FlowEntry macros, then trigger or compose those functions remotely from a dashboard. No app update needed. 2. PipeFlags: Feature flags built for mobile. Toggle features on or off instantly for specific users, segments, or rollout percentages; without redeploying. 3. Session replay: Full video, touch tracking, network logs, and console output captured on production builds. See exactly what your users see. Security was a priority from day one, only pre-registered functions can execute, no arbitrary code injection. It's built for teams who ship often and debug in production. iOS (Swift/SwiftUI/UIKit) is live now. Android with Kotlin is coming soon. Would love your feedback, what would you want from a tool like this? Happy to answer any questions!
Martí Carmona Serrat

Really interesting approach to remote function triggering. How do you handle versioning when a user updates their app but the remote dashboard still references old @Rewire annotated functions? Nice work!

Al Moutasem Nabil
Maker
@mcarmonas Thanks Martí! Great question. The SDK sends a manifest of all registered @Rewire functions (with their signatures) on every session start. So when a user updates their app, the dashboard automatically reflects the new set of available functions — any removed or renamed ones get flagged as “stale” and won’t be triggerable. If you push a remote override targeting a function that no longer exists in the client, it’s simply ignored at the SDK level with a logged warning. No crashes, no side effects. Thinking about adding optional semantic versioning per function down the road for teams that want more granular migration control, but for now the session-based manifest sync keeps things clean and zero-config.