I am learning java and developing on Android, and then I thought about one question. How to understand that the technical characteristics of the smartphone will support my program? How to understand what specifications a smartphone needs in order for it to work? Where you can read about it in depth or tell the experts themselves?

    2 answers 2

    For an Android developer, such things are not very important. You should be guided only by the version of android. Well, if you do something with the use of NDK, then you should still look in the direction of the processors. And the rest is not so important.

    • I just have the android 4.1.2 smartphone myself, 1 GB RAM and I myself want my smartphone to work with my programs too) - Max
    • Yes, everything will work. I have a smartphone for tests on 2.3. And everything that is supported on it, everything works. The main thing is to write so that there are no memory leaks. - pavel163
    • and you said that if with NDK, then look towards the processor. What to watch? - Max
    • NDK is c ++. Different processors have their own characteristics of work. And for them the code is written in different ways. For example, there is a library Realm. It is written on the pros. And when you connect it, the application starts to weigh 10 megabytes more. This is all due to the fact that it pulls the code under different processor architectures - pavel163
    • @ pavel163, well, why are you talking about the features of work right away. When developing native applications, this is not so important. Especially since we are talking about four typical architectures for phones. What is important is simply the realization that there are different ABI and for each one there must be a native library compiled. - user1056837

    It is better not to think whether a particular smartphone will “pull” or not your application, but to write applications in such a way that there are no obvious performance drawdowns.

    Those. use standard approaches for searching, sorting, storing data. Do not try to write bicycles yourself; ensure that resources are used optimally, etc.

    In fact, you just need to include common sense and not a crutches.

    PS Another good idea to read about ABI - this is the various architectures. But this is important when including (developing) native libraries.