MobileRead Forums - View Single Post

kenjennings · 02-02-2011, 04:42 PM

Don't know what the delay is. I'm running out of reasonable guesses to the cause.

As a developer type of person I wouldn't care if the SDK (APIs) have to change for 2.2. If something I write for the edge breaks on the next Android release then I'd just rebuild it (assuming the SDK was provided again.) Developers deal with it just fine with other Android devices So, fear of version changes shouldn't be reasonable.

I don't care if the build method for apps using eInk may require technical, manual tweaking. Developers are not users. Fear of non-coder end-users inundating the Help desk over the SDK is likely not reasonable.

Most of the SDK stuff would be the standard Android docs. The rest of it to access the eInk screen can't possibly be so complicated that it takes months to write.

So, I'm running out of reasonable explanations for the SDK delay.

02-02-2011, 04:42 PM	#4
kenjennings Edge User	Don't know what the delay is. I'm running out of reasonable guesses to the cause. As a developer type of person I wouldn't care if the SDK (APIs) have to change for 2.2. If something I write for the edge breaks on the next Android release then I'd just rebuild it (assuming the SDK was provided again.) Developers deal with it just fine with other Android devices So, fear of version changes shouldn't be reasonable. I don't care if the build method for apps using eInk may require technical, manual tweaking. Developers are not users. Fear of non-coder end-users inundating the Help desk over the SDK is likely not reasonable. Most of the SDK stuff would be the standard Android docs. The rest of it to access the eInk screen can't possibly be so complicated that it takes months to write. So, I'm running out of reasonable explanations for the SDK delay.