Android: build native GUI app with NDK? [closed] - android

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.

Related

Is it possible to make an android app using only imported languages, and if so, how? [closed]

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 last year.
Improve this question
Just out of curiosity, is it possible to make an entire android app using android studio by importing SwiftUI and coding it with that instead of Kotlin/Java? I'm really curious because I just spent an entire semester at school learning SwiftUI and now we're doing Kotlin, and it would be a funny, interesting, and fun challenge if I could try to use a language meant for IOS to code an Android app. If somehow it's even somewhat possible, how could it be done, and would you have to still code some in Kotlin/Java or could it all be SwiftUI?
SwiftUI is a library that Apple ships with its operating systems. You cannot use it to develop an Android app because the library is not available on Android devices.
It might be possible to use Swift, the programming language, to develop some parts of your Android application, because it is possible to compile Swift code and the Swift standard library for Android. However, I don't really know any of the details and I'm sure it will be a difficult endeavor if you're just learning how to program.

is it safe and good practice to use third party libraries for React Native UI? [closed]

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 am new in React Native. I am making hands on demos to learn react native.
I go through basic components and style. Facebook is not provieing all rich component for making rich UI. But many third party library like react elements and native base provides many rich UI componants. So my concern is that is it safe to use those controls? are they can conflict with inbuilt control?
Safe? How much do you trust the authors. I would not include a library that isn't a well known open source library or from a major corporation you trust without reading every line of it to check for malware.
Conflicts won't be a problem. Its not like any of them replace other Components. How well they work will vary from library to library, of course.
Edit: A warning I just thought to add- do not assume a React library will work in ReactNative. React libraries tend to embedd HTML in the render() function, that doesn't work in ReactNative and will cause crashes/red screens of death.

Native or framework programming for my app? And if framework, which one? [closed]

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.

Advice for moving from WP8/WPF to android development [closed]

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

Tkinter to android translation [closed]

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.

Categories

Resources