Running an app under development on a real device impairs its performance?

Asked

Viewed 115 times

6

I’m worried about running my app in development on my device. Could someone tell me if this undermines performance, leaves a lot of junk, leaves doors open and vulnerable on it?

  • 2

    You are the programmer, you dictate what your software will do, regarding memory junk you must know how the application lifecycle works. here is a link http://www.devmedia.com.br/understanding- the cyclo-of-life of an application-android/22922, there is a lot of information on google and on the android’s own api about life cycle and regarding vulnerabilities, I say again you make the app, you must know what is codando, and android is mt strict regarding restricted access, vc always have to inform in manifest.xml features that you will use, ex. camera, sd access, net, etc.

  • Thank you so much, Juarez ;)

1 answer

6


At first it does not harm anything directly. But...

Your concern makes sense, if the application has problems it can at least leave the device vulnerable if it allows somehow to be accessed externally directly or, more rarely, indirectly.

Note that this risk is not so great. And generally speaking applications cannot do as much damage as is possible on a computer with more freedom of action of the applications (within the traditional API). Nothing can access the app that easily. And as far as I know the vast majority of applications developed expose little arbitrary external access.

So it’s good to know that there are no guarantees, but you also don’t have to worry that any little wrong thing that’s done will create a big problem. In general more advanced technologies will give more chances for vulnerabilities. If you’re going to use more advanced things, of course you need to master their use. Normally I would say that the domain is necessary to do anything in software, but I’ve seen that the current trend is everyone go out doing what they don’t know without a lot of worry about risks.

It is clear that some precautions need to be taken, you need to keep a closer eye on the entire application usage cycle while it is under testing.

Nor will I try to say that there are application monitoring techniques to understand everything that is happening with it. This alone is an advanced technique.

I imagine you will use Java to develop (think about Kotlin). This is a language that helps not to make a number of mistakes and leave the application vulnerable in various ways. But it’s no miracle, if you don’t use proper techniques You can compromise security.

But know that the apps for this platform are usually active, that is, they take the action out. Rarely do they let outside sources take action. So this helps a lot. Of course, you can accidentally release external access. But it is very difficult to do this. It is often difficult to do it by wanting to, imagine without wanting to.

Completion

  • The risk exists but it is small, in general very small.
  • Pay attention, study to understand what you are doing.
  • Don’t let the trial app run without a monitor until you have confidence that nothing is wrong.
  • Avoid using what you don’t know enough and ask for help when you need it.
  • Knowing that there are minimal risks, make sure that there is no critical data and that it cannot be lost, such as internal or external resource access passwords.
  • Very well explained! Thank you for the reply, bigown! ;)

Browser other questions tagged

You are not signed in. Login or sign up in order to post.