Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to know what are pros and cons for using external libraries like these in application development.
It is possible using these libraries application may run well on one device but may not run on any other device, application performance, size of apk using these library?
And which one is good idea while developing application in Android studio to copy file in libs folder or add it in dependencies and stay connected to internet.
It's hard to tell the pros and cons when using an external library in Android app development. Most of the time, it depends on the real circumstance. If the library simplify your app development and it's specially optimized for Android, it's worth to try.
When it comes performance about external library, the document says we should be careful.
As put libraries in libs directory or referencing them from mavencenter/jcenter repository, the result is the same. It will be compiled to your app by android app tools finally. In order to simplify your life, referencing the libraries from an internet repository is a better choice. You don't have to worry the version and dependencies. Android studio now has adopted this way.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 14 days ago.
Improve this question
We have some Android Applications which share data models and other stuff. So my plan was to make a library for that which can be easily extended and implemented in these Apps and maybe also in future Apps.
What is the best approach for that?
For just testing around, I implemented a module to one of the Apps. But this has the problem that it is bound to this single project and its version control which makes it a pain in the b_ to maintain. Also its not practicable to work on because everyone has to have and work on this App project for library changes.
My thoughts were to separate them but how? I have researched alot and didnt find a way to create a standalone library. The only way Ive found so far was to create a whole new Android Project and manage the library in it and seperate it from the :app Module. I dont know but this doesnt feels straight forward.
What is a good way to manage a library which has its own version control and can be easily maintained from everyone? Is the own Android Project the way to go?
You can still setup a separated VCS for a module and maintain it in another repository. git-submodules is a way around it.
As you've mentioned, another approach is to create a new Android project for the library and distribute it separately. It's very straitforward way, but it's simple less error prone.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I already have a running prototype of my iOS app build using Apache Cordova, and I'm planning on using the same codebase for Android.
Should I fork the iOS repository and start customizing Android?
or
Should I keep Android related changes as a separate branch of the same repository?
What's are some of the best practices that are followed, and why?
If you want to re-use part of the code base, you could just add a directory for the Android specific code in your master branch.
If you'd rather have components, you could put the common code base in its own repo, produce a library (eg: a maven package that you would publish on an internal maven repo), and have an iOS repo and an Android repo, both of which would reference this library.
However, unless you have a very large codebase (or unless you don't plan to make modifications in this common codebase), I wouldn't recommend the library-approach, since it can become a pain to add and test a minor patch in the common code base.
Regarding the approaches you proposed:
a fork and a separate branch are more or less the same anyway (instead of having a branch android, you would have a branch fork/master)
With an android and an iOS branches, changing the common codebase would require an extra merge that you wouldn't need with a single branch. And you have the risk of a desynchronisation of this common code base between your branches if you don't have a strict workflow
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I have a relatively simple tkinter program that just uses Event, Button and Label objects. I would like to translate this to be usable on an android platform.
1) What python for android should I use? QPython, py4a?
2) And on that platform, what GUI module should I use?
I'd like a little bit of detail for why you think a specific module or app would be best, as I'm just getting into the android scene and want to make an intelligent jump.
Even for native purposes, most developers would advise you keep away from Tkinter. It's a dated and unintuitive library that often makes GUI creation and maintenance harder than it needs to be.
The main advantage of developing apps using a Python library and embedding in Android is cross-platform support.
These libraries will often allow you to port your app with ease to many different operating systems.
I will not answer which is "best" since this is an opinion-based question outside the scope of StackOverflow, however I will say it is (generally) easier to port from Kivy to android than it is in some other libraries (such as Qt). But take this with a grain of salt.
Most libraries nowadays offer advanced GUI capabilities built-in, and your choice will likely not limit you in that regard.
Either way, there is no direct/simple way to translate your Tkinter project to any of these, and you will likely have to rewrite it with the library you end up choosing.
I will add that if your intent is developing only for android, most would advise developing in a native Android language, such as Java or Kotlin, or using a development tool which makes use of such languages. This would result in smaller APK sizes and likely faster running times for your app.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have built a very simple android app (i.e., an app that essentially just shows pictures along with some quizes). I am curious what the cheapest way of duplicating my app on iPhone, assuming I can't do it myself?
In that case, you should develop this app in titanium framework that framework basically supports javascript type structure and provides platform to develop app in both platform ios as well as android.
You might want to take a look at the j2ObjC project from Google
It will convert existing Java code to objective-c.
I haven't tested it and don't know how well it does perform, but if the app is simple, it should do well
If your application feature has not required native framework then you can create your application in multi platform framework.
Apache Cordova is one of the reliable mobile application framework which is run on iOS, Android and many other operation system.
Also you can find much details on this Link.
So you can make you application with using such framework and deploy on any operation system.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
independent from the fact if it makes sense or not, if it is a good way to create Android apps or not: for (educational/personal/whatever) reasons I want to create an Android app with graphical user interface in C++ using the NDK.
What I found so far are some information about the NDK, how to create native libraries and how to access them out of Java applications. But what I'm really looking for are some information how to create a View and to add graphical user interface elements to that View out of my C++ NDK app.
Any ideas and hints how that can be done or where some more information/HOWTOs can be found regarding this?
Juce is a fantastic C++ UI framework that works well on Android.
It can be used under the GPL or a paid-for commercial licence. The community is fairly active and the author is very friendly and helpful. I found it relatively easy to build using the NDK tools on Windows.
Caveat - it seems Android isn't a high priority platform for them, so some things are missing at time of writing (e.g. support for hardware buttons). Still, in my experience, the UI framework does work very well on Android, and that's what your question is about.