I have an existing PHP MySQL web app that I want to make an android app for to look up account info, get status info for work orders, upload photos, etc.
I'm new to Android Dev and found a site phpforandroid.net that says I can use PHP to build android apps. 6 years ago I did a basic Java class n learned a little about Java, but not much.
I want to have a login to the app, then present a menu to drill further into heir account info.
My first choice would be PHP if the database interaction can happen, but I don't really know. Anyone else gone down the PHP db driven route, or is Java the way I should go? Any tutorials you would recommend?
What are the community thoughts? THanks.
Why don't you build a smartphone compatible website (i.e. with jQuery Mobile)? You could use your existing PHP knowledge and the app would run on any descent smartphone, not only Android.
How about a mobile version of your web app? You could make it work on other phone platforms, you'd have full control over the code, instant updates without bothering the end user.
Related
I have never made an app before but I’m currently relearning Java with hopes to make an Android app soon. However a key part of my app would rely on borrowing data from another app, namely the Digital Wellbeing app by Google. I essentially want to build an app that will take user’s phone usage data and do cool stuff with it. Is this possible?
I'm a newbie android developer and we have a website that sells some stuff (using a payment gateway), you can also login on the site using credentials, facebook, or google+ login. Now we have a need for an android and iOS app. What is the best approach to port the site functionalities to Android or iOS app? What are the issues I need to consider when I choose one approach? What would be the best approach: native, hybrid (phonegap, xamarine etc.) or using wrapped (using webview as far as I know)? I'm especially interested in the user login part (because I want the user to be able to login to his account if it exists and if not to create it using the website API endpoint - this is how I imagine it), how to solve that when choosing between these approaches? Any suggestions (answers, comments, links, books) would be helpful.
Thanks
My sugestion is to do native, always can reach more performance in multi thread ,high concurrency transactions and heavy applications.
For android, you can build from source an application, and export the html/css content to the smartphone using android.webkit.WebView. Take a look:
https://developer.android.com/reference/android/webkit/WebView.html
I think is a excellent solution for your problem.
I am developing an iOS app using firebase, but I also want to create a java desktop application that accesses the same realtime database that the app uses. Is this possible to do? I feel as if this should be able to work because firebase works for Android apps which are written in Java. If this is possible, please give some details on how to go about doing this. Also, I am asking this in regards to the new and revamped firebase website that Google just recently announced.
Firebase has a server SDK for Java that should also work in a desktop Java application. The code is very similar to the Android Firebase code so you'll see familiar classes like DatabaseReference or ValueEventListener.
I have basic knowledge of Java but have never developed for Android.
A friend asked me for an app that seems easy enough to develop but I would need some help for Android.
All the app needs to do is send a text field (for example license plate number) to a predetermined SQL Server database.
Is this easy in Android as it sounds?
Thanks in advance. Cheers.
Darko.
That should be easy, but does it need to be a full-blown Android application for that?
Sounds like a simple webpage with an input-field and a submit button would do the job as well.
If you're familiar with using databases from Java the task is very simple. Just write the code that sends a string to a database. The exact same code you would use on a desktop Java application will do.
The rest is a matter of defining your user interface and obtaining the string. There is a good basic tutorial you can use on the Android developers web site: http://developer.android.com/guide/tutorials/notepad/index.html.
The number of code lines in the whole application will be in the range of a couple of dozens.
It sounds like you want the license plate information stored in a separate server, but if you also wanted to store some information on the device itself there is a simple Notepad tutorial provided by the Android Developers site that explains how to setup and utilize an SQLite database on the device. This by no means would replace the functionality of a server, but is another Android feature that is at your disposal.
I have read the Blackberry documentation and it is possible to push a notification from a webapp. I am planning to create a Blackberry application that compliments to our webapps. But I am still left in the middle whether to develop a webapp or native Blackberry app. I have also look at how a webapp runs on Blackberry browser and it looks smooth.
From your experience does the native app offer something that the webapp doesn't? Bonus question, is Facebook and Twitter app on Blackberry a native app or a webapp? If it is a webapp, is it possible to make a launcher for the application on Blackberry?
Thanks for your help.
Facebook and Twitter are on both types. The web apps are just a website formatted for a small screen so anything you do in say asp.net will show on a blackberry web app if you program it to. The native app just feels like part of my phone. You can save data on the phone so if your app is a relating to news or something that would be stored I can read it offline or slow connectivity (camping, rural areas, etc...). It can also interact with other feature that blackberry offers such as contacts, email, media player, etc...
If you would like to save anything for the user to view without pinging the internet a native app would be preferred.
It's possible to create a launcher but I haven't created one so I'm not sure of the details. I would assume it's just an app that opens the browser to your URL.
One more thing about a web app would be if your application stores users settings (twitter auth key, etc...) they would need to be stored on your server and not the users phone adding more expense and maintenance.
Good Luck.
Widget is not supported for device software less than 5 , you combine both of web and native development by using browser field ,but you need to consider that its Java Script support is poor
Let's not forget that the blackberry browser is really bad as well. I don't know any BB users who would want to use a web application because of that.
When it comes to native apps, you have some choice however and you are not restricted to java (depending on which OS version you want to target). In addition to the mentioned Java, you can use Widget (link for resources) that behaves like a native app, but can be accessed like a web app.
I was just at innoTech and they had a whole session on this topic. But instead of recaping it let me just post the funny video they showed at the end which sums it all up.
Mobile Dev Rap Battle: Native Code vs. Web Apps