saves time, easy to implement methods.. will make your app looks good , but you will gain less knowledge
its up to you if you want to use libs, if you think you can achieve something without the use of libs then do some coding , if its really hard or impossible to implement without lib then consider to use one
saves time, easy to implement methods.. will make your app looks good , but you will gain less knowledge
its up to you if you want to use libs, if you think you can achieve something without the use of libs then do some coding , if its really hard or impossible to implement without lib then consider to use one
Thanks for your response. I never said I want to avoid using Libs. On the contrary I want to understand the inner working of B4A for my better understanding.
the lib will be packaged along with all the app used resources like image files, etc..
you need to weight out the need of a lib...
for instance, there's a few libs that will increase your APK a few MB in size, even if you just need one single method from it, so you need to figure out if a "javaObject" alternative is a better compromise...
the lib will be packaged along with all the app used resources like image files, etc..
you need to weight out the need of a lib...
for instance, there's a few libs that will increase your APK a few MB in size, even if you just need one single method from it, so you need to figure out if a "javaObject" alternative is a better compromise...