New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce required API level #27
Comments
Note that Scanner for Zotero managed to do just this-- and it didn't entail much: https://github.com/jmschanck/Scanner-For-Zotero/commit/a96efd8a9c2f355becc92620498f7681a88c3bfd |
Step one: Reduce required version to 1.6 by making some small changes. Step two: Learn how to do fragments and such to support 3.x nicely. There will probably not be a tablet-style version for 2.x tablets like the Nooks. Sorry, but they don't support the tablet-oriented libraries that 3.x brings, so it'd be a hacky solution at best. |
I definitely agree that lowering the bar would open up the app to people, and would love to see this. |
This would take reworking many of the dialogs in Zandy, so it's slipping to an undetermined future milestone. It may prove possible to do as part of writing a fragment-based UI for tablets, so there's still some hope. |
The compatibility library we're using for tablet support is dropping Android 2.1 support, and we're going to follow, unless someone steps up to do this separately. I still think Android 2.1 would be doable, but there are more urgent priorities. Interested devs are welcome to reopen this and try. |
Closed in fa53e20 |
The APK currently requires API Level 8 (Android 2.2), but I'm pretty sure there's not much I'm doing that requires that. I know that dialogs can only be passed bundles in API 8+, but that might well be the only thing holding me back. Moving down to 2.1 or even as low as, say, 1.6, would be great and open up the app to even more people out there with older devices.
Anything aiming for 3.x will probably just share basic logic, but be a separate APK, since the user interface and the libraries used to build it will presumably be different for Honeycomb tablets.
The text was updated successfully, but these errors were encountered: