Is my work a good research work?
Good scientific research is anything that increases the knowledge of humanity. Sometimes that involves creation of new things, sometimes that involves putting together existing things in a way that creates a new capability.
What you have described might or might not be scientific research, depending on the particulars of the work.
- If there is an interesting reason why Android static analysis hasn't been done yet (e.g., something incompatible between Android's organization and typical static analysis approaches), then explaining that reason and how you overcame it can be the core of a good scientific paper.
- If, on the other hand, it's just technical drudge work (e.g., like rewriting an application from C to Java), then even if it is difficult and valuable it will not be particularly scientifically interesting.
Even if the application itself turns out not to be scientifically interesting, however, what you learn once you start applying static analysis to Android programs might well be...
In my opinion, academic research work should be focused more on learning in general and learning how to perform research correctly in particular, rather than on doing grandiose, novel or even "the right" research. This is especially applicable to the Master's level research, where implementation-focused work and theses are very popular (obviously, it is quite field-dependent, but here I imply the software engineering / computer science areas of research).
I don't see any reasons for why an good implementation-focused research work could not be published as a research paper in a solid journal. In fact, I have seen a lot of such papers (of varied quality), especially in the above-mentioned domains, published in respected peer-reviewed outlets.