0 reply
0 recast
0 reaction
15 replies
4 recasts
28 reactions
1 reply
0 recast
0 reaction
1 reply
0 recast
0 reaction
As a user, it's immediate availability of data, actions, customisation, integrations with other services for apps. For frames, similar but hyper focused on one feature.
As a dev, frames are easier to build and roll out. However it gets trickier when you have a bigger frame and cognitive load is a real challenge. Imagine a frame with 30 screens. Maintaining can become difficult but not only that, it's the user retention too. I found that simpler frames that do just "one thing" tend to work best for now.
When a frame reaches this maturity in utility, it might be time to extend it into an app/web app, where the user has more reach to the other features without being locked in a small space. Plus, you can integrate it with other apps in your device, enhancing its utility.
An app would be action -> outcome -> extend this data to share, combine, store, automate, etc.
If there was a way to build open apps without relying on Apple or Google it would be great. That's one of the limitations over Web apps and frames 1 reply
0 recast
1 reaction