I'm working on application which needs to implement In App-Billing payments and I was searching more info about it and find a library written by someone else and I'm curious about it. Is it good to be used and if anyone here already tried it. It seems like it's not so complicated to understand,but I just want to hear some information can I used it and is it stable enough. Here is the project code which I find :AndroidBillingLibrary.
So any suggestions / advices and information about that library is welcomed. Or anything else which will help me to understand more clearly in app-billing process in android (except the documentation in android.com) will be really great!
Thanks for any kind of help!
It very clearly states on the tin: 'This library is a very early release and it should not be used as production code'. So if you want to use it, you will have to understand how it works to be able to fix it when it breaks. You might as well write your own.
Read the official documentation, study the dungeons sample, try to understand and if you get stuck, post specific questions. Otherwise, just hire someone to do it for you.
Related
I need to testing for my application using Roboelectric with AndroidStudio,integration of Roboelectric is over,now i have to
network calls for which i used Spring.io,i need to test services,BroadcastReceivers and Views.
Please Suggest me some links or books,i already searched for that i didnot get documentation for Roboelectric.
Yeah, there is not much documentation about Robolectric. I had to search for examples all over the internet.
The official Robolectric site is a good way to start . Also the Robolectric blog has really nice examples . But what I found really helpful was this video . Colin Miller makes it look so simple.
I'm still looking for a book or something more formal, so to speak. So if you find something please let me know, I'll do the same. cheers!
I am considering buy wsclient++, anyone recommend this?
The demo project apparently generated the files, but I still got some erros, I dont know if is a library problem or because it is a demo.
Thanks
Ask the Support http://wsclient.neurospeech.com/support/, they should help you, if the want to sell this product. This support-request maybe gives you also an insight how good their customer care will be, if you buy this product :-)
I was doing the HelloTabWidget tutorial
http://developer.android.com/resources/tutorials/views/hello-tabwidget.html
and getting errors on the "TabHost tabHost = getTabHost();" statement. I thumbed threw the stackOverflow notes and it seems a few people were having the same problem, and a few received responses along the lines of "Note: Tabactivitity deprecated in latest versions, consider learning Fragments" and discovered I can use ... the v4 support library which provides a version of the Fragment API that is compatible down to DONUT. although I haven't quiet figured out how to do this.
My question is - If the function is deprecated, and causing newbies problems, shouldn't the tutorials be updates to use the new functions? Is their a polite/politically correct way to let the people in charge of the tutorials know that an update may be in order? Or maybe new tutorials exist, and I'm just looking at an old URL?
shouldn't the tutorials be updates to use the new functions
Who exactly are you asking this to? Us? Why would we know why google hasn't updated their docs/tutorials.
is their a polite/politically correct way to let the people in charge
of the tutorials know that an update may be in order?
I'm very sure that they know. They probably have more important things to do. There are TONS of tutorials around the internet. They don't need to update all their tutorials.
Or maybe new tutorials exist, and I'm just looking at an old URL?
Search google. There's TONS of blogs that will give you lots of examples. Including here at stack overflow.
I am starting getting to know android renderscript and i've read everything that is on the android developer site, but it seems that there is not enough documentation, examples.. I was wondering if there is maybe a book that also has a part with explanation and some renderscript examples. I want to learn about it in depth, so if someone can provide links for books, examples, tutorials (anything would be of great help) i will appreciate it. Thank u in advance!!!
We are working on this documentation gap and plan to have updated docs within the next few weeks; however, it will still be a work in progress. If you have specific things that you want to do, let us know. In the meantime, there are samples packaged with the SDK that might help you get started: http://developer.android.com/resources/samples/RenderScript/index.html
I've posted a couple of RenderScript articles/tutorials on my blog. If they're of use, let me know. I've been debating whether I should make more, but it's tough to gauge interest in RenderScript.
There's very little documentation on Renderscript at this moment in time. Google has published a few posts about it, including the following on the Android Developers Blog, but apart from that, the information available is very limited.
http://android-developers.blogspot.com/2011/02/introducing-renderscript.html
http://android-developers.blogspot.com/2011/03/renderscript.html
Some documentation is also available here:
http://developer.android.com/guide/topics/renderscript/index.html
You can also find some examples here:
http://code.google.com/p/renderscript-examples/
The Android team has promised to add more documentation at some point in time, and I'm hopeful we'll get some more information when Ice Cream Sandwich launches.
I want to prevent anyone from apk reverse compilation. We need to do something. I browsed on the internet, but I still don't know the operational steps clearly.
Who can tell me how to do it?
Anyone's help is so welcome!! Thanks!!
You need an obfuscator. If you are running .NET or Java, these should be easy to find.
There is nothing to prevent people from decompiling your code. All you can do is make it as nasty to read as possible. Don't do this in source (as you will not be able to modify your code yourself), use an obfuscator to do it as a post build step.
Google recommends ProGuard. See this link in the Android docs for more information.
It won't prevent people from disassembling your code (you won't be able to stop that - after all, the operating system needs to disassemble your code to execute it!), but it will make it very hard to see what's going on.