tags:

views:

1216

answers:

3

I want to port an small open source AES encryption class to Android, and it would cut my work down a lot if the API of Android is as close as possible to the Java 6 API.

How much is implemented (or referenceable), as I have tried searching about this on google, and i have not yet come up with anything useful?

+4  A: 

Have you checked the Java library reference on http://developer.android.com/reference/ ?

Christoffer
The Android API isn't the same as Java API!
tuergeist
As Android is Java-based and it also uses Java's compiler, you can answer the question yourself. Try out your Java 6 code.
tuergeist
tuergeist: I thought the compiler was completely different since Android has its own byte code and interpreter?
kigurai
+1  A: 

IMHO In general Java 6 works. The compiler does the work for you.

Re self implementing encryption: Please try using Bouncy Castle. In general, self implementation of any known crypto algorithm isn't a good idea.

tuergeist
thanks for this. the bouncy castle implementation seems a bit overkill for what i'm trying to do. i am just planning to get my feet wet with android, by making a small file encryption app. not really sure how complex it will get, as my background is in web apps, not single-focus apps, and i haven't really done much java.
warsong
A: 

In general you shouldn't have a lot of problem as long as you're not using any graphics or sound-related libraries. Android does not support swing or awt.

Also, this isn't an android limitation, but you'll probably going to be having a lot of trouble with floats, since the platforms that android usually runs on (ARM) do not have a Floating point unit, so you might need to take that into consideration

Mohammed
I assume they can still DO floating point operations, they'll just be much slower than you're used to?
MatrixFrog