Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Closed 9 years ago.
Improve this question
I am working on phoneGap android application in which I want to display bold,italic,underline,text align etc features in textfield.I implementing this by using ck editor jquery but it works fine in browser but it not shows in emulator and device also.So please help me in implementing rich textfield in android phone gap.
I do not believe that CKeditor actually works correctly on android devices yet. While it does load, it has a number of quirks that prevent it from working "well".
In order to test for yourself, simply visit http://ckeditor.com/demo and play around with it.
I was involved with the IOS5 testing for CKeditor a few months ago - during that step-by-step testing I also sat down with 3-4 different android devices and ran the same tests I was running for IOS. Those tests did not turn out well, so I simply gave up. Those tests are outlined here:
http://cksource.com/forums/viewtopic.php?f=11&t=22880&sid=057e3d4af2a019cc2d22c177ec927b97
Possibly my experience is invalid because android devices vary wildly in their support for certain key features - but that is worth you knowing because you cannot plan on a widespread release as many devices (specifically Galaxy Tab) do not work well CKeditor.
If anyone has contradicting experiences I would love to hear them. Support was bad enough that I completely abandoned my android project in August and focused solely on IOS which has very good CKeditor support.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
I did not know where else to turn for this question
My present background is Android and Rails application development. I am building a social media type mobile app that allows for real-time messaging between users, and the creation/scheduling of events as well as a web component in rails.
In terms of launch, everywhere I look it notes not to launch to Android first, but focus on iOS, yet just about all of these sources are 2+ years old.
For the application that I have, generally described, is there any reason not to launch to Android first? Are the fears outlined in the articles outdated?
I'm working on a social network app for Android too and in my opinion you don't need to fear about selecting an OS for starting development. Start from where you are experienced. I'm good enough with Java and Android so I decided to start with Android. When I have a fully functional app than I will launch and start building the app for iOS.
You should focus on the OS that you like and you are experienced with. I think these articles are oldies. But the decision is up to.
You may want to read this article
Happy coding
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
Lenovo a6000 is not able to run material design code .
First of all, a question like this will provoke opinionated, heavily biased answers and provoke flamewar like discussions between religiously fanatic fanboy groups. It is not very wise to ask a question like this.
Furthermore, one single phone is never enough to really get your app tested. It gets you the impression how your app works on one device, but how it will work on all the others, you will never know. You will always need a variety of devices, and I am not just writing about phones, phablets and tablets, but also of different vendors. Because each vendor introduces "his" own peculiarities and quirks and you will notice that while running fine on a Nexus, your app might crash on an HTC or Samsung. Or while running nicely on those, it might not on a Huawei.
Why?
Because.
Because the vendor did something the others did not, and no one expected it. But your customers will hold you responsible for it. Because your app is crashing. And you don't want this.
So bottom line: There is no best phone for testing. Get a number of different devices from different vendors and test on all of them. Yes, it is expensive and tedious work, but you asked for it...and your customers will be thankful for a stable app. :)
Google nexus series is the best. Just use nexus for tests
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am seeing some errors on Android 4.3 which by numbers is the highest version, but then I see most of my installs are on 4.1, 4.0.3-4.0.4, 4.2 is the 3rd by installs.
So what is wrong with 4.3 (Jellybean)? I have some crashes that happen on it, but not other versions. Was Jellybean some buggy Android verison? Or what is wrong with it?
Unless you're a power user who installs your own ROMs, you are at the whim of the manufacturer to get OS updates. In many cases they have not been prompt to update (or even want to update at all).
This chart gives a good layout of what versions people are using in general on Android: http://developer.android.com/about/dashboards/index.html
Without a nexus you dont get vanilla stock android over the air OS or updates.
Some manufactures take a long time to update their phones and some phones from same manufacturer dont get updated. So so phones cant actually get the latest OS without custom rom etc. Even some top phones released today are not 4.3, and probably never will.
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
I'm an iOS coder and have been asked to write some cross platform code with Phonegap or Titanium. There's plenty of information out there about setting up development environments, etc... except I'm missing one crucial piece of information.
What mobile hardware should I buy? Now that's a pretty lousy stackoverflow question, so let's rephrase it to be useful.
What criteria needs to be examined in choosing an Android tablet for iOS/Android cross platform development with PhoneGap or Titanium?
The corollary question is also useful, what criteria needs to be examined in choosing iOS hardware for cross platform development with PhoneGap or Titanium?
A good general approach is to pick high volume devices with an eye toward diversifying hardware- so for example if samsung has a really high res phone, don't buy another really high res phone from LG or if all the available Android phones are high res, try to sprinkle one in that has a slide out keyboard. Don't worry about trying to test everything on every device, test things that should work the same across a small number of devices and then test the things that could be very different on a larger number of devices. Depending on your app there are probably a few things that you know could behave differently on different devices- focus on this. For example, we test the camera on all devices but we would only test something like an alert message on one device.
If you are looking to build for iOS and Android I would also recommend checking out Brightcove App Cloud - http://appcloud.brightcove.com. There are good testing/debugging tools and plugins are well-documented and fully supported.
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 9 years ago.
Improve this question
What are some things you wish you had known about Android when you first started out or before you published your first app on the market? I am nearing completion on my first and am starting to make sure I have crossed my proverbial Ts and dotted the Is
Save you keystore file.
If you lose it, you will not be able to update your app.
Use <uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/> to be compatible with 1.5 and newer devices.
Make your icons based on the Icon Design Guidelines.
Test your app on all Android versions before release to Market, or, if you're too lazy, just on:
1.5 (older one, lacks support of some classes that 2.x does)
2.1 (most modern devices)
2.2 (most current, not much devices for now, has some internal rendering changes)
Earlier than 1.5 are hard to find, so can be safely ignored.
android-remote-stacktrace is also very useful thing
Here's some things you can try:
Stress-testing
adb shell monkey -v -p your.package.name 500
It will help you to do some stress testing before publishing to Market.
Test your app for memory leaks. It's very easy to leak context. This post will help http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html.
Test your app on some device with Sense UI like EVO4G. Many things are different there.
Take a look at this https://stackoverflow.com/questions/2094588/android-development-tips-tricks-gotchas for some more pointers about Android development
Have a look at this blog. I have jotted down the problems i faced and some stuff i would like to pass on to new developers
http://seventhsoulmountain.blogspot.com/2014/01/gotchas-and-lessons-learnt-android.html