I was wondering, for integrating MIXARE into my Android app. I came across the post
http://damianflannery.wordpress.com/2011/06/13/integrate-zxing-barcode-scanner-into-your-android-app-natively-using-eclipse/
but i got a question that is, do my phone or tablet need to be installed with MIXARE ? or i will be just launching the functions of mixare in my app ?
Apologies if you guys don't quite understand my question.
Nevertheless i still hope to have some answers.
Thanks.
The instructions given do NOT require that other software be installed on the device - the library referred to is an android library which is installed on your development machine are including in your application as part of the distribution (i.e in the APK).
If you choose this route be sure to test on some devices which DO have the other app installed because if you get the intent filters even slightly wrong it will fail in this case.
However this is NOT the best solution: there are several different reasons why it is better to install the Mixare application and use the intent system to access it from your code, possibly the best of these is that it allows the user to keep the latest version of the external app updated. The author of your link clearly indicates that the only reason he chose this path was because within his enterprise solution no access to the play store was permitted.
Related
I did some research and i can't find a proper custom marketplace solution for Android, i would like to know if someone knows any, with the possibility of being hosted and maintained by us, and fully customizable.
I read about F-Droid but it doesn't seems to be very customizable, as far as i know.
Thank you all.
Well you have a few options. We built our own app store at the last contract I was in. From a file storage it was pretty straight forward. For Android we just supported unknown devices at first, but later switched to integrated MDM(Mobile Device Management) system. I can't remember exactly which one we landed on in the end.
However, for the iOS side we had to build SSL pointers that are nested in a manifest file that points to the IPA. For Android, we just had to sign and place the APK. For Web packages, we hosted an internal NPM server.
For the packages we used Apache Archiva, but that is not the same thing, so just tossing that out there if it matters at all to you.
Lastly, we built an Angular based web interface to handle Authentication and displaying of available apps/versions. Lastly we built an app to put on the app store that others would install that would keep up with our services to know what was installed, needed upgraded, or uninstalled.
However, this took a team of engineers over a year to get done.
So let's talk free options. Just google Android Market Place self hosted alternatives. Last year at the CES I met with Aptoid and they were deploying many self hosted, self managed options that would fit your need very nicely. I don't remember the exact pricing though.
So bottom line is, depends on how fancy you want to get and if you have time to build your own, or if you want to buy/subscribe to one out of the box.
Hope that helps.
I've asked this question before but it was seen as a broad question. So I'm asking a more specific question about that topic now.
I want to build an Android app with ability to play Sega Genesis ROMs. Obviously it needs a Sega Genesis Emulator. Based on what I've seen in other android apps with Game Console Emulators, I've figured there's no need to write an emulator from scratch. For example this app has emulators for more than 10 Game Consoles and obviously they haven't spend years to write +10 emulators from scratch and put them in an app just to distribute it for free.
So I'm guessing there's a way to use (include) an already written Game Console Emulator in an Android application. Is that right? And if it is, how can one do that?
I've search A LOT and found nothing about it. Maybe this process has a special name that I don't know and I should search with that name.
This is too broad a question, but I can point you in the right direction:
Android allows for native C++ development using the NDK. Get it, learn it, love it.
Then you can either use a C++ emulator Core that is open source and include it in your app, or you can just build your own version of an existing emulator and fork it to your liking.
For your example (Sega Genesis), you could use SDL and DGEN: combining the two will yield an android-compatible Genesis emulator.
Okay, here's where I'm at. I used Eclipse to import the code for the SMS/MMS app that is on Android devices. The code on GitHub is at https://github.com/android/platform_packages_apps_mms.git. I used the Import -> Git in Eclipse. Got the code into the environment. Had to manually paste the AndroidManifest.xml file into the project, and also copy over source and resource directories.
Basically, I want to get the Eclipse project to a point where I can run it on my device and it behaves JUST like the built-in app. THEN, I can modify it for my specific needs hopefully. I don't want to have to write all the SMS/MMS functionality from scratch if I can avoid it.
NOW, the problem is: A LOT of unresolveds. I keep reading various places where people are saying that some of the packages aren't REALLY in the SDK and are internal... Why the heck call it an "open source platform" when the source isn't available for the built-in apps that Google provides?! (If this is in fact the case). Further, why would they provide the code on GitHub for the MMS app if in fact not all the code is available and you can't compile it? Seems a little ridiculous to me.
I have read some answers to previous posts where I was just sticking my "toes into the water" so to speak, and people are saying that a lot of these packages are part of the firmware? Seems like there should be some base code for a texting/mms app out there somewhere.
Anyone know of any? (Open source, free, SMS/MMS Android code that I can easily obtain and that don't suck, if in fact I can't use Google's code?)
Thanks,
John
Mms as well as other system apps use private or hidden APIs that are not available through the SDK.
This has nothing to do with not being an open source platform, as you mentioned, but with the fact that you are trying to build the application in a way that is not supported and nobody says it was.
If you want to modify and build Mms, do it as part of the firmware build, using make, not importing the project to be built by the SDK in Eclipse.
The stock MMS app built into a device's original firmware, signed with a private key, and is able to use some private API.
Third party apps can't use the private API for various reasons, one being security. All the source is open if you wish to view it.
You can definitely build your own firmware, or ROM, as some call it, and run your own modified MMS app on it.
I don't know if you can make and install your own MMS app. You can find out by looking through the Play Store for similar apps or looking at the Android developer documentation to see what permissions and API are provided to third party apps.
I want to modify the core applications like Settings.apk and install on my own android phone.I don't want to publish it on market. I have following doubts
Where can I get source code for core applications?
What are the things I need to do this?
Please tell me steps to do this.
You can get the source code here: https://android.googlesource.com
Keep in mind that the packages there might not be the ones on your phone as each vendor can provide a replacement of their own, the Camera for instance is almost never the google app.
You will also have to decide which version you want since each OS version has revisions that take advantage of newer API's etc.
As far as what you need pretty much the same thing you need to build android apps, eclipse, the sdk, tools etc. http://developer.android.com
You will of course have to remove the application from your phone before installing the new one since your signing certificate will not match. There can be difficulties when you swap out your own version so be sure to save the original.
I have an app in Android Market which is a standalone app that's essentially a full conduit to an SQLite Database(add, change, delete, inquiry). Some of my potential clients have asked to see a sample of my work, but they don't have an Android device.
Other than just showing them screenshots etc., is there a way I could have them go to a website where they can actually run it & check it out.
I'm thinking there would be a programming element involved (convert app to a mobile website essentially?), hence posted this question here.
Not quite sure where to get started. Any help would be appreciated.
You can use one of the patterns like MVC/MVP/MVVM to create your core library and then develop additional UI variants for different clients: Android, java applet etc.
Alternatively you can develop a mobile web site as you suggested and use simple android app to navigate built-in browser to it. This might be somewhat transparent to most users. I think Android MSN client uses such an approach.
I see 2 relatively easy options.
Give them an .apk designed to only
run on the emulator (you can check
the ID, the emulator ID is 00000...)
and they can boot up an emulator and
run it. If you're worried about them
reverse engineering your .apk you
probably shouldn't go down this
route. Or if you don't want them to
have to install the emulator
Set up a virtual machine and let
your clients remote desktop into it.
Give them permissions to only run
the emulator or however you want to
set it up