[Q] Understanding feasibility of Blackberry/RIM running Android apps in Playbook? - General Questions and Answers

I am doing some research on the feasibility of RIM's rumored "ambition" of running android apps within the Blackberry Playbook.
As many of you know, this has been "discussed" on several blogs over the past several weeks (can't post links as a new user): news.cnet.com/8301-13506_3-20031474-17.html
this is where my question to the developer community comes in: what do you guys think of this venture? Will the experience be seamless? would it require extra effort for you to get an Android app to work on a Blackberry device (whether it be a tablet or a smartphone)? Would be curious from a developer point of view how you guys view this transition. Finally, what do you think the user experience would be like with a RIM device? would it be seamless for users in terms of experience. There are news reports that blackberry won't be using dalvik to try to pursue this transition, so im curious also if this changes things:
appleinsider.com/articles/11/02/10/rim_playbook_to_run_android_apps_but_fears_oracle_lawsuit.html
Curious to get thoughts...thanks

Related

[Q] Which Android phone with front-facing (secondary) camera to buy?

Greeting to fellow developers,
First thing's first: I'm a programmer, experienced in Java, C,C++ (mainly MSVS, unix/linux), and a few other (i.e. no longer fashionable) programming languages ... And I'm planning to start developing Android based Apps. Currently I'm in the phase of selecting the most suitable phone for my future endeavours.
The Question: What is the best, most suitable, Android phone which fulfils following criteria:
[1] is based on Android OS
[2] has a front-facing, i.e. secondary, camera. This is a must (!!!)
[3] is suitable for development & testing front-facing camera Apps. A must (!!!)
[4] would also be suitable for development of other Apps
[5] phone has to have a company promise of at least 12 months of security updates and updates on newer Android OS vers. (Due to ongoing developing, App debugging, etc.)
Where I come from (Slovenia-land) following are the phones which are available and achieve upper five features: Samsung Galaxy S, Samsung Galaxy S 2, Samsung Nexus S, HTC Sensation, HTC Desire S, LG Optimus 2X, Samsung I8000 Omnia II, .... (These are all phones available through telecommunications companies - i.e.: by investing into a 24 month usage plan. There's also a few other, promised, scheduled to be pushed on the market, phones. But without any certain launch dates, there's no point in me mentioning them!)
What I'm looking for is an advice from seasoned developers, who are / were already developing front-facing-camera Apps, which Android phone is best for me to buy (to be used for a whole App life-cycle: learning, developing, testing, updating)? Due to Android phone fragmentation this choice is really mind-boggling me, and is very difficult for me to make, and I would really not like to buy two or more phones right from the head-start. - For the past few months I've been reading a lot about Android development, and the thing that frightens me most is Android fragmentation. The way I understand negative effects of this fragmentation is: Let's say I develope an App, which exploits some front-facing-camera functionality (like a new skype, fring, or sth. like that), and start marketing it on various Android App Markets. Which phone is best for me to buy, to be able to avoid, those "doesn't work on my htc", "doesn't work on my gingerbread SGS", etc. negative Customer Experience and Evaluations? ... In short: I'd like to buy an Android phone w/ an Android OS, that would ensure me a developed App on that phone, is giving me confidence and peace of mind, that my App will work on all, or at least most, front-cam Android phones. I'm looking for an advice on which phone to invest in, so that my developed App will work on all, or at least most, Android 2.3.* (or later ver.) phones?
Currently I'm rooting for a Nexus S, but have read a few negative evaluations about them on Cnet and Google Customer Support forums . And I'd really not like to buy a $600 phone, which front camera or Wi-Fi doesn't even work the way it's supposed to! ...
I hope I'm not asking sth. that's not even remotely possible? And most certainly I hope I'm not shooting goats? ... Like I said, I am experienced in desktop Java, linux, etc. development, ... but the World of Android development is totally new for me! But I don't the have money to buy all of the latest front camera Android Phones out there.
I've searched this forums extensively, but found no answer to my thoughts and questions! I've also asked on fellow developer forums, got a few weak answers, but no strong ones. As You can see, I have a few blind spots in my knowledge ... And hopefully w/ Your help, I can fill these spots!
Thank You very much for any advice!
-- Lucky Star
Anyone? ... .. I'm just looking for an advice on which front-cam Android phone is best for me to buy for development purpose (to ensure that my App will work on all Android 2.3.* phones, i.e. best phone to fight Android fragmentation) ... Any kind of advice will do.
Thank you for your help.
Have a nice day,
-- Lucky Star
I think your best choice is the Nexus S as it is the official Google puppy and very easy to develop for.
Why is the Nexus S, as you say, "very easy to develop for"? - Is the development process on e.g.: SGS2 more difficult than Nexus S? They are using same OS, same SDK. SGS2 only has different UI.
2nd Question: How do I ensure my developed Apps on, let's say, Nexus S will indeed work on all, or at least most, front-cam Android 2.3.* phones?
Thanks for any and all advice!
Keep em' coming!
-- Lucky Star
+1 i am i also seekin a good suggestion
Bump ...
Come on people ... There must be some enthusiast on XDA developing Apps and exploring Android's FFC functionalities?
Still in search for a good advice ...
Many thanks!
Sgs 2.
Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.

[Q] Android App Emulator

I'm much like several of the people who bought TouchPads in the recent firesale. I absolutely love WebOs and the device in general but the thing that's bothering me is that the app selection is absolutely horrible! I know that there is an Android App Emulator on the PlayBook, is it possible for something like that to show up on the TouchPad? I love WebOS and I don't really want to give it up for only Android. I'm sure tons of people would really like something like this on their new Touchpads. Thanks!
Sounds like a great idea hmm...
I agree. I think that porting Dalvik to WebOS might be the best move to give us the Android apps and still let us easily use Linux, including ubuntu apps.
Well the problem would be the license..
lol...good point
license issues?
I thought it was opensource/freeware? How else could Cyanogen, etc., do what they do?
is it possible to port alien dalvik to the TouchPad? We should get some developers on this.
FAILHARD said:
is it possible to port alien dalvik to the TouchPad? We should get some developers on this.
Click to expand...
Click to collapse
You took the words right out of my mouth!!
I'm actually trying to find developers for the exact same thing. It should be doable. Alien Dalvik was made in Qt which was ported to WebOS so in theory it's entirley doable. the only question is if there are any developers free to take it on that aren't currently working on a full Android OS port.
I'd really like to get a development team set up for this because alot of people would like to keep WebOS and just have a larger app catalog.
Yeah, exactly what I was thinking. We should look for a dev who could possibly have experience it Qt, though that's not completely necessary. If we gain more support, I'll post a dev thread.
I can't offer anything other than Beer/Pizza money but this is a great idea. WebOS is generally well reviewed and not looked at as a problem so much as a benefit. The OS is solid. The App Catalog is not.
Android Emulator :-D
I would love see a emulator on my TP. I would like to be able to place Android on the device I still much prefer the UI and design on WebOS even though Android is far more capable.
I'm happy to donate to this cause should someone take it up
alien dalvik is not open source, however, dalvik in general as well as the whole android os is under the apache license, this can be modified, forked and reworked (such as myriad turbo/alien dalvik) without having to release the source, its obviously possible... But you know what would be easier, porting android as a whole... Even dual booting would be easier.
Well the allure of this is having the superior Android app selection on the arguably better tablet experience of WebOS. If that were made possible - I wouldn't care about having Android on the device.
I couldn't agree more. As an OG Pre owner I love webOS but couldn't fight everything I can do with Android.
If I could get all my Android apps and keep my TP the way it is would be perfect.
The problem with porting Android right now is we have to use 2.3 which is for phones and not 3.2. I would rather either wait for ICS/4.0 for a port or just get the app market working.
Sent from my PG86100 using XDA Premium App
That settles it there are enoght people interested in having a standalone WebOs android app emulator without having full android.. I'm starting a development thread, doing some preliminary work, and going to look for a few interested developers to work with on getting this going. My touchpad comes tomorrow so then i can really get into it..
Thanks Roto I was just about to do the same.
also, Roto post a link
Up. Beer on me
Here is the link to the development thread.
http://forum.xda-developers.com/showthread.php?p=16904876#post16904876
Failhard since you and I were the first to put in work on this idea i'd like you to help me head the project and find volunteer talent if you're up to it.
I took a look into what goes into a Dalvik port... it's TOTALLY doable just a matter of time and effort..
Unfortunately after i return to college in a week time will be in short supply for me so ALL help is appreciated!
I had never used WebOS before getting a tablet this last weekend. I have been an android fan for smartphones for now (I am willing to move to something better when it is available, otherwise stick to what works). I am a web designer/user interface designer and since starting using WebOS this last weekend, when it comes to the OS and its default apps that come with it, it is clear WebOS has the best user interface of the tablets (I used both iOS and Android OSes 1.5-3.2, Windows 7 tablets don't really count as a tablet OS and that is clear when using it on tablets).
The Android Emulator would be a great idea, but if you want quick development specifically for WebOS, we need to get a program created that can easily and painlessly port android apps to WebOS apps. Also it will take HP courting and reassuring the big players like Netflix, Hulu, Corporate IT Software Development companies that WebOS is viable and have continued support.
HP/WebOS only has a short amount of time to really establish itself. Next summer is rumored to be Windows 8 release and Windows 8 tablets coming. If Windows 8 can create a good tablet interface (WebOS is the one to beat imo atm as it has the number 1 interface), plus it's strong backing of games, program/application support and being able to integrate phone, xbox, tablet, and PC (Desktops and Laptops). Windows 8 is the biggest threat to anyone in the tablet market at the moment imo and they have been very successful in many of their endeavors as of late ("don't poke the sleeping giant" comes to mind, google and Apple have done that).
Due this short Window of time (pun partially intended), we have to establish WebOS as a main competitor to Google and Apple and prepare it for the onslaught of Windows 8. We need to work as a community to get things rolling and we need to push HP to court the big players in the industry to produce apps and content for WebOS and to continue further development on the operating system on their end. If we as a community and HP execute right, it will be a very exciting year coming up.

[Q] How To Get Free Phones for App Development?

I recently posted a thread on how I can start programming geared towards the mobile platforms.
I would like to develop apps for more than one mobile platform. However I just have access to an Android device (SE Xperia X10), iPhone 4, and an iPad 2.
Smartphones are not like candies, that you can go pickup at a cheap store.
I mean how and where can I and other people who want to develop apps for specific platforms get free phones for testing and using the apps we develop?
The emulator that is included with the SDKs are not always the best way to test.
Any suggestions? All help is appreciated
EDIT: Forgot to mention that recently Windows Phone called over WebOS developers to develop applications on the WP platform, and Windows gave the developers free devices. But there are not many WebOS devs out there..
The best and fastest way to require a "demo" phone is doing the following.
Just get in touch with the companies that are creating the phones.
Explain your development and give them a nice overview on what your app is, what it does and how things go.
Make sure you don't demand a phone but wish to test run it on certain specific devices with key features that are a "+" in your app.
I think you'll have a chance to receive a demo phone.
Btw don't expect you'll be able to keep that phone forever.
I recently contacted HP to request an Elite-book from them for business usage.
Explained the plans and deals and after a few days i received one.
I need to return it by end of this year.(aawww )
Did same thing for some phones for my company
I think it depends on what you wanna test and how high your requirements are.
Also i think it's best to mail on behalf of someone working in the industry or on behalf of a company.
They had my company info in case of argument.
Sites like XDA got enough rep to request them and be trusted.
Individual guy asking for a phone is "50/50" chance. (depends on the person processing your mail and your info & app your working on)
One thread is enough: http://forum.xda-developers.com/showthread.php?t=1237030

Android in the enterprise

Hello all,
So I've been tasked to look into the viability of using Android devices within an enterprise environment and I figure I kick off my research by reaching out to the forums.
I've looked at some whitepapers and management platforms such as GOOD and MobileIron. This is just the start as I'm also looking at an acceptable device and OS version. As a big Android fan, I would like every to use a Galaxy Nexus, but I know that is not happening.
I wanted to know if anyone on this forum actually has Android rolled out throughout their enterprise or even using their personal devices to connect to their corporate network.
If anyone has comments, or information I can look into, please let me know!
Well we are doing a project now at my work to install mobileiron. Mostly for IOS but you can add any mobile device to it. There are alot of Mobile device management (MDM) on the market. The difference with android thats alot of this things depend on your android version, if u have a 1.5 u can forget most things. But a galaxy nexus is a sure bet !
sergeant_bob said:
Well we are doing a project now at my work to install mobileiron. Mostly for IOS but you can add any mobile device to it. There are alot of Mobile device management (MDM) on the market. The difference with android thats alot of this things depend on your android version, if u have a 1.5 u can forget most things. But a galaxy nexus is a sure bet !
Click to expand...
Click to collapse
Nice to know that Mobileiron can support multiple devices, as we do have a few iOS devices are in our network. As for the Android version, I'm looking at version 2.2 and higher. So far 4.0 is only readily available on the Galaxy Nexus, but the Nexus S is another device I was looking into.
In2uitiv said:
Hello all,
So I've been tasked to look into the viability of using Android devices within an enterprise environment and I figure I kick off my research by reaching out to the forums.
I've looked at some whitepapers and management platforms such as GOOD and MobileIron. This is just the start as I'm also looking at an acceptable device and OS version. As a big Android fan, I would like every to use a Galaxy Nexus, but I know that is not happening.
I wanted to know if anyone on this forum actually has Android rolled out throughout their enterprise or even using their personal devices to connect to their corporate network.
If anyone has comments, or information I can look into, please let me know!
Click to expand...
Click to collapse
I don't know if you have closed out your investigation on this. I have just seen your post, and I am very interested. I currently use my Android devices to connect to my corporate network via VPN, but I can only access resources only after rooting the devices. Why? Accessing resources (e.g. the ERP) requires that I make entries of IP addresses in the hosts file of the device - much like on the Windows PC. However, the hosts file cannot be edited, unless the device is rooted - which could invalidate the warranty. My company has carried out extensive studies, and I am sad to say that this problem does not exist with iOS. This is the singular reason my company is now leaning towards the iOS (iPhone, iPad) as replacement for the Blackberry.
So, if Google really wants Android to find a place in the enterprise, it must deal with this hosts file issue, or borrow a leaf from iOS.

[Q] Ubuntu or Android for a 3rd world tablet-based education project?

Hi all
MY QUESTION
How much work is it to get Ubuntu working on a cheap tablet, (in terms of weeks and stress/reliability)? I'm about to spend a year writing tablet software that needs cheap hardware. If I find a capable Android tablet going cheap, is it reasonable to consider getting Ubuntu working on it, instead of restricting myself to the Android OS to use cheap tablets? Would Ubuntu C++ apps still kill performance? (Ubuntu will save me lots of development in other ways.)
ALL comments pleease, however brief and knee-jerk.
BACKGROUND (all feedback gratefully received)
I'm at the design stage of a project to use tablets to improve education in poor countries. Extremely briefly, the tablets will use elements of social media to enable children to collaborate remotely and asynchronously on projects, and game aspects to get the kids excited, who have probably spent the day working on the fields, and to welcome kids with special needs. The system will enable education to continue in complex emergencies, such as droughts and conflicts. Currently most kids drop out after grade one as the education they're offered is so poor. Tablets can support teachers and enable kids to get more out of their classroom and homework time.
The system needs some clever back-end engineering to operate a local social network if there is no internet connection. (I'm thinking something like NodeJS acting as both a p2p client and a server.) It also needs to run on cheap devices, if it is to be adopted by third world Ministries of Education.
I am currently torn between Android and Ubuntu for tablets. Android will presumably be the cheapest platform for the foreseeable future - tablets now go for as little as $40 wholesale. However Ubuntu for tablets now offers the ability to bring a proper IT education to these children, as they can learn office software, desktop OS, etc. Ubuntu also provides source code I can customize, eg, GCompris, Tux4kids, KDE and Epoptes. I can see Ubuntu on other tablets here, but it seems the Nexus 7 is the cheapest tablet I can currently get Ubuntu on and performance is still an issue. Is that fair to say?
I can write everything using C++ and OpenGL to squeeze as much as possible out of every processor cycle. I have been a developer for 15 years, but am pretty ignorant when it comes to hardware/OS level.
My alternative is using something like Titanium and Unity, (I don't think HTML5 will perform well enough), so I have a bit more platform flexibility, at the price of having to develop everything from scratch, and using technologies for the back-end stuff that aren't as ideal, (such as Android Java and/or Titanium JS). But perhaps that keeps more options open for me?
My feeling is I should go for Ubuntu, but the price needs to reliably reach considerably below $100 to become a nationwide system in a poor country.
Obviously any comments or thoughts on any aspect very gratefully received. Don't restrict your comments to my question - I want all your wisdom!
Huge thanks for reading all this and any contributions
Chris
Re-post
perhaps you would get more of a response if you made this a bit shorter, and re-posted on ubuntu.stackexchange.com, android.stackexchange.com, and programmers.stackexchange.com
Also, perhaps a little off topic, but have you considered using coffeescript? :cyclops:
Thought it might be a stackoverflow question, this forum is amazing for tablet OS dev though. As ever I blather on too much...people have complained in the past.
All three? Wouldn't that be bad netiquette?
That's kind of a tricky question because technology is always evolving and prices fluctuate so much that in a year you might be able to get a device for half the price. I'm not knowledgeable about the new Ubuntu options but if your gut says go Ubuntu, than do it.
Thanks, I'd love to say gut instinct served me well, and I'm all for intuition, but I wouldn't trust it enough to dedicate 6 months of development on its hunch. However these replies and the act of writing the question has crystallized my view a little so I now have more targeted questions.
found this excellent guide on the hassles of porting an OS to a new device...
http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
and this
http://stackoverflow.com/questions/...droid-kernel-porting-from-one-device-to-other
So looks like a month, best case, with expert developers and a device well-known for being hackable. So to port ubuntu to a $40 device, I'm thinking three+ months, plenty of risk, and much pain.
Some other interesting posts:
A little gritty detail on porting kernels: http://stackoverflow.com/questions/...droid-kernel-porting-from-one-device-to-other
A tutorial on building (compiling, not developing) a kernel: http://forum.xda-developers.com/showthread.php?t=2110842
The best post I found on porting ROMS: http://forum.xda-developers.com/showthread.php?t=1941239
Porting modules from within kernels: http://forum.xda-developers.com/showthread.php?t=1751966
Porting cyogenmod, (a ROM, not a Mod, as anyone on this forum probably knows): http://forum.cyanogenmod.org/topic/15492-general-cyanogenmod-porting-discussion/
A new kernel developer: http://forum.xda-developers.com/showthread.php?t=2173411
A vocab for noobs like me: http://www.talkandroid.com/guides/beginner/android-rom-and-rooting-dictionary-for-beginners/
I was wrong. Ubuntu Touch is based on the CyanogenMod kernel, which is widely ported.
From Canonical's FAQ on the bits of CyanogenMod used: "The kernel and a few low level drivers for network, video, audio and some other hardware features are taken, all the higher level parts have been taken out. On top of this the whole Ubuntu is started in an chroot environment." ( https://wiki.ubuntu.com/Touch/FAQ#How_is_Ubuntu_Touch_connected_to_Android.3F)
As a result it has already been ported to about 40 devices, and porting to a further 30 is work in progress, listed here: https://wiki.ubuntu.com/Touch/Devices
CyanogenMod officially supports 172 devices, and unofficially supports another 59.
Officially supported devices: http://wiki.cyanogenmod.org/w/Devices
Unofficially supported devices: http://wiki.cyanogenmod.org/w/Unofficial_Ports

Categories

Resources