Content
@
0 reply
0 recast
0 reaction
🪱
@worm.eth
This is the weirdest thing that Warpcast does. No other app does this - why not just let the App Store do its thing?
13 replies
0 recast
21 reactions
Richard🎩
@rliriano
My understanding is @warpcast is updating the app faster than what it takes Apple to receive the update to then put it on the App Store. Would be cool if it auto updated within the app. cc @dwr.eth
1 reply
0 recast
3 reactions
derek
@derek
I believe it’s likely an over-the-air update via React Native, and therefore needs to reload the JS Bundle which is non-trivial to do without a hard close or manual restart. It is indeed because they ship more frequently than they’d prefer to go through the Apple review process. cc: @worm.eth
1 reply
0 recast
3 reactions
🪱
@worm.eth
This doesn’t change my general feedback - updates should be invisible to users!
1 reply
0 recast
1 reaction
derek
@derek
Yeah it’s the tension between invisible or more-frequent updates. Can’t easily have both in the Apple ecosystem.
1 reply
0 recast
0 reaction
🪱
@worm.eth
Every other app just does it automatically
2 replies
0 recast
1 reaction
derek
@derek
FWIW, I totally agree with you on the sentiment. But there are tradeoffs the team has made to move faster. And I’m all for it tbh. Warpcast is not as mature as other apps, so speed is on their side.
0 reply
0 recast
2 reactions
derek
@derek
Agree, but other apps don’t update as frequently as FC team does, or they just go through the Apple process (which can be painful). Weeds: FC also *can* do some auto updates, but some updates (any that mess with the underlying Swift code) need to be manually reloaded. I’m sure @v could provide better insight.
1 reply
0 recast
1 reaction
