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.
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 7 years ago.
Improve this question
I want to develop application for Android and iOS.
It will be simple application with some data of users and some achievement animations.
It will comunicate with our servers, where will be used REST as backend.
I need the application to be secured. There will be stored very sensitive data.
I think application won't need much performance.
I'm going to be project leader, so I have to find programmer. So if I use framework, then the programming language will have to be in good performance/price ratio.
It's difficult to answer your question due to lack of information, but I have gained some experience regarding this topic from the past year.
The choice of your frameworks depends on time/cost, resources and know-how. I suppose your question is about whether to use a webframe including webprogramming, or native iOS and Android implementation.
The big advantages of using a Webframe are:
Can easily be included on both platforms Only has to be implemented
once (with a view platform specific adaptions e.g. access to camera
etc.)
No additional know-how is required (just JavaScript and HTML)
The implementation is easy and development fast Subsequently the development time is reduced
The disadvantages are:
Webframes are slow
If there are animations like transitions it could be laggy
User triggered events could also be delayed. (just a few milliseconds, but it could be very annoying.
This could conclude in a total useless app, because the userexperience is very bad.
If you want a throughout solid app which offers a flawless userexperience I highly recommend a native implementation. But you have to consider, this affords experienced Android and iOS programmer, and is associated with more development time and subsequenlty more costs.
I recommend to implement a simple prototype which includes the animations and the main features. If the userexperience is good then go for it.
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'm a WPF and WP8 developer and I'm planning to develop all my current apps for android too. I did some research and read a little about android development. From what I've read, Android's XML is terrible compared to XAML. The tags are long and terrible (For example, why couldn't they just have Width instead of android:layout_width ?) And the most annoying part was that there is no equivalent for data binding.
So, I looked into alternatives and came across Xamarin, which seems a better. But I have a few questions I was hoping someone would help me with.
My biggest question is should I go for Xamarin or go ahead making native android apps in java? Is there any disadvantage on using Xamarin? Because there is a good thing about it that I can reuse most of my code..
Is there data binding like functionality in it?
Does Xamarin support all features that a native app would? Will I be able to get Material UI design templates in it?
Also, if you have any other advice or suggestions do let me know.. Thanks
My suggestion would be.
1)
Take it easy. Android development is not that bad.
It is true, you do not have data binding facilities as you have in WP but that is not end of the world.
Android xml is simple and it beautifully solves the issue of different screen sizes and types.
You have to write more code in android than in WP. WP came after android which allowed Microsoft to come up with better development patterns for rapid development.
2)
Big no for Xamarin. Xamarin reduces your options because it relays on android library wrappers in c#. Only benefit of Xamarin is to have common business logic. that is normally 5% percent of any project. In most cases you would find yourself in very tight situation; for instance, if there is any good 3rd party android library that you want to use in your project then you have to wait Xamarin wrapper for this library in order to use it.
3) Not always, you would find restrictions
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 am concerned about the SDLC of android apps and the etropy that to program an android app that would come under software engineering principles.
To clarify like we have life cycle of developement of all softwares products , which rule the principles / foundation of the software building i need to know what are the keep factors / principes of android developement lifecycle can not find them anywhere
To make it More Clear what things i am concered of are :
Conceptualization
Requirements and Cost/benefits Analysis
Detailed Specification of the Software Requirements
Software Design
Programming
Testing
Maintenance
and models that should be applied to android development
Linear or Waterfall model (which was the original SDLC method)
Rapid Application Development (RAD)
Joint Application Development (JAD)
Prototyping model
Fountain model
Spiral model
Build and fix
Synchronize-and-stabilize
Especially What are Testing Techniques for android the one with Eclipse Juinit Testing Doesnot seems to work well
To be Honest there is not SDLC mentioned by Google for Android Developement.
all they have given you is the best practises which you can find under this
Android Developement Best Practises
Secondly there was an article related to mobile apps development which will gide you somewhat of software developement lifecycle of mobile apps
Mobile Apps SDLC
http://www.propelics.com/6-tips-for-getting-started-with-mobile-app-development/
A common consensus appears to be "very short". Most apps, unless they have an exceptionally large user base, tend to last only a very short while (1-12 months). A lot of mobile developers tend to favour the "Release updates as frequently as possible" approach, with new iterations of apps appearing sometimes weekly.
Another approach is to develop as little as possible, wasting as little resource as possible on any single project. Apps that are developed this way tend to have one or two bugfixes, and are then left to die off in their own time.
With new iterations of Android appearing more frequently than most people update their handsets, most developers tend to focus on a broad compatibility range.
So, to round that off:
Not very long at all.
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 need to write a client side application which communicates to a WCF service.
The app is actually targeted for multiple platforms.
Internet Browser.
Android.
iOS
Windows Phone.
The client side is rich on UI.. should contain animations and "fireworks"..
In the past, Flash used to be the generic 'Glue' to hold all that.
But These days, I keep seeing and reading about HTML5 hype..
I also heard and read a bit about Xamarin but will not dive into it before I get some confirmation that it can deliver what it promises.
So, My questions are as follows:
What would be the technology to use in order to develop client side?
Html5 or Xamarin - or should I just stick to flash?
do note - this is not a request for opinions - or in other words:
I'm looking for answers of experienced developers who already done something like that and can tell me of a sure path to success.
Xamarin and visual studio - is it correct that this will allow me to develop everything on VS.2012/2013 IDE and will be able to output packages per OS?
Keep in mind I'm MS oriented dev.
Thank you.
You mention candy crush.
The realistic answer in business today is simply develop the iOS, Android, and anything else natively. It's the only thing that really works.
Trying to save a few dollars on 'cross-platform' is useless.
For 2D or 2D games specifically, you should use Unity3D, which is the overwhelming market dominator, currently, for games production.
In general there are any number of better-or-worse "cross-platform" things like xamarin, appcelerator, etc etc.
But the overwhelming factor in your project will be, you need to forget about a server side and change to parse.com. That time-saving will utterly overwhelm any "minor" decisions about what to program the different platforms with.
FYI Unity3D works with c#. Android is Java. iOS is objective-C.
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.