I’m currently hosting my app’s APK file on my own website, and I’m looking for best practices or recommendations to ensure users get fast and secure downloads directly from the app or from an update prompt.
Is there anything specific I need to consider regarding link structure, permissions, or compatibility with Kodular’s built-in components for APK installation?
Would appreciate any technical feedback or alternative solutions others have successfully used!
Hello, I think you want to get update message in app yes? İf it is true then you can use firebase to get update message in app. But if you don’t want to use paid things just let me know and I will help you about it
Maybe you can upload your apk file to Github. Because it is more secure and fast way to download you file
@jane2 which kind of update do you refer, there’s force update and choose update,
Force update won’t allow the user to use the app unless he/she get the latest version of the app
Choose update let the user to choose between updates or keep using the old version
I recommend Firebase for comparing new version of app with the current version by storing your app details
You can fetch these info when Screen1.Initialize
If you are currently have this method in your app, then explain more what kind of fast and secure updates you want?
Also you can share your updated blocks if you’re not understanding something
Thank you for your suggestion! You’re right — I’m looking to notify users about new updates directly in the app. I’ve considered Firebase for this, especially for version checking and update prompts. However, I’m also exploring non-paid or more lightweight alternatives to keep things simple. If you know of a reliable free method for version tracking and notifications without Firebase, I’d definitely appreciate your input.
Thanks — it seems like GitHub is a common recommendation, and I can see why. It’s reliable and simplifies access management. I’ll test how it handles direct download links for APKs and see how well it plays with Kodular’s download and install components. If you’ve implemented this setup, let me know if you faced any challenges with file permissions or MIME types.
Good question — I’m currently leaning toward an optional (choose update) model where users are informed of new versions but can continue using the current one if they prefer. That said, I’m also keeping the door open for a force update option for critical releases. I’m planning to compare app versions using a remote config like Firebase or an external JSON file. Any suggestions for best practices or cleaner implementation would be welcome.
Sure I had created a system like yo want to do and I used my free extension for it if you wanna go with it you can check from the link below
Also I have another alternative
You can check both of them and if you don`t understand anything just let me know I will help you
With my extension you must create a json file like this and upload it to github
You can copy and edit the config.json file
{
“app_version”: “3.2”,
“update_message”: “Bəzi xətalar aradan qaldırıldı!”,
“update_link”: “https://yourdomain.com/update_page.html”
}