Hi to all
My question is related to how efficiently organize the code of an App. I will give you an example: in Windows, we have the possibility to put the code in various modules (of course), and in static or dynamic libraries. Static libraries are linked to the code, and I guess there is no big difference either in size or performance in the final module. But my question is related to the existence of Dll that may be loaded at runtime (in Windows). In this case the benefit is in terms of size may be notable, while the drawback is the loading time of the dll. Moreover, if the part of code of the dll is never involved during the use of the Program, because it is doing many tasks, which are not necessarily contemporary, we can have also benefit in terms of memory usage.
The App on which I am working is rather big and, besides already fighting with the actual Android limit of about 0.5 Gb, I begin to wonder myself whether I can try something to break the code in modules. Of course I already did it, but i suppose that, in practice, no benefit on having an enormous module or a big set of smaller ones. My question is only related to code, not on organization in pages, because, in practice, i just have two pages and the working one is only the second. For example, I am thinking that maybe putting some code parts, not always called, in services, may do something similar to the Windows Dynamic libraries. Thanks in advance for any comment.
My question is related to how efficiently organize the code of an App. I will give you an example: in Windows, we have the possibility to put the code in various modules (of course), and in static or dynamic libraries. Static libraries are linked to the code, and I guess there is no big difference either in size or performance in the final module. But my question is related to the existence of Dll that may be loaded at runtime (in Windows). In this case the benefit is in terms of size may be notable, while the drawback is the loading time of the dll. Moreover, if the part of code of the dll is never involved during the use of the Program, because it is doing many tasks, which are not necessarily contemporary, we can have also benefit in terms of memory usage.
The App on which I am working is rather big and, besides already fighting with the actual Android limit of about 0.5 Gb, I begin to wonder myself whether I can try something to break the code in modules. Of course I already did it, but i suppose that, in practice, no benefit on having an enormous module or a big set of smaller ones. My question is only related to code, not on organization in pages, because, in practice, i just have two pages and the working one is only the second. For example, I am thinking that maybe putting some code parts, not always called, in services, may do something similar to the Windows Dynamic libraries. Thanks in advance for any comment.
