Yes, you are correct, Pakkly adds a thin wrapper to your executable which is built with Rust to be as lightweight and fast as possible. This wrapper adds virtually no overhead besides taking up a bit of memory (around 8mb).
Update checking only happens on startup, currently. Your app performance will not be affected. In case the server is not responding during startup Pakkly will continue, after a brief delay, executing your app. The startup update check will fire at most once every 60 seconds (In case someone starts your app in quick succession).
Update notifications are planned, but these will be optional, and will never stop your app for you.
Kids these days - calling 8mb “a bit of memory” :) (yes indeed it’s not that much these days but I remember when 8mb was enough to run a multitasking OS with a ton of high-end applications.
Right? I left it out of my recent thread about BREW development, but we were actually worried because our first app took up 120KB of phone storage space!
back then IT was not the workhorse of 95% of modern life, and only a handful of physicists needed computers for very niche usecases that needed next to nothing in resources
You can run a fully functional voip and chat client within that order of magnitude (Ripcord) whereas the 'real client' (Discord) doing the same thing is 10x that.
Don't downplay the resource wastes on nothing of value.
I'd understand if this were about something taking half a giga of ram like too many applications do nowadays. But this is a wrapper adding 8mb of ram. Your efforts should be re-directed somewhere else.
Update checking only happens on startup, currently. Your app performance will not be affected. In case the server is not responding during startup Pakkly will continue, after a brief delay, executing your app. The startup update check will fire at most once every 60 seconds (In case someone starts your app in quick succession).
Update notifications are planned, but these will be optional, and will never stop your app for you.