3 ms·
App development could be as quickly as a few weeks. If the only "killer apps" we have seen in the past three years are the ChatGPT kind, I'm not holding my brea
by rs186 1y ago
App development could be as quickly as a few weeks. If the only "killer apps" we have seen in the past three years are the ChatGPT kind, I'm not holding my breath for a brand new "killer app" that runs only on iPhone 16+.
- greggsy 1y agoOn-device is a killer feature IMO
- rs186 1y agoIt's not a killer until it's verified to work, and makes a better product than those that use APIs. From a user's perspective, nobody cares about whether it's on-device or not unless cost is directly involved.
- dangus 1y agoThe user doesn’t necessarily care but I think on-device enables certain experiences that can’t be done if you involve a cloud service. For example, involving a network and data transfer will always toss in some latency that may not be acceptable or desired for a particular use case, even if you’re on a desktop plugged in with an Ethernet cable I also think that in the long term the hardware that individuals own is far more powerful than the typical compute that can be allocated to a user who is using a free or cheap cloud service. Comparing a rented VPS to a cheap $400 server in my closet is like night and day, the VPS is just not a lot of horsepower and the typical smartphone has a whole lot of computing power to work with. In a very near future when the chips are even more AI-optimized, data centers might not be the most efficient way to go about this. Example: imagine implementing an application like Final Cut Pro as a browser application where all the compute takes place on a remote cloud server. It’s just not plausible: too much data to handle, too much compute needed for processing, too much of a need for low-latency responsiveness of the app.