With all of the new apps being released, some may call this the Golden Age of PortableApps. However, with this rush to release Apps, careless errors are being made. References to Base applications, Paths not updating as you change PC's, Settings being left on host PC, and other mistakes. To fix this, I think a list of requirements to be checked one by one is necessary. I will add and change this list as needed.
-No traces of app is left on host PC
-No remains of base application are remaining
-Application works when the drive letter changes
-App has been compressed
-All the rules of PA format are followed
What do you think?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
This was already mentioned in another thread, and it's not really beneficial because the app can be any one of small stupid (silly) mistakes. It's best just to test it for a good 15 minutes yourself, and then post a pre-release.
The thing is, these errors dont affect ussage of the app. I think that after the app goes through its main testing, a checklist must be gone through, maybe run a batch script? I know of a script to check for traces of an app that was used as a base, there are programs to look at program proccesses, and compressing an app before release is easy. Manual checking is still required, I'm just talking about this to double check for errors.
Simplifying daily life through technology