Talk:Android software development
|WikiProject Software / Computing||(Rated B-class, Mid-importance)|
|Material from Android (operating system) was split to Android software development on 13 May 2011. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted so long as the latter page exists. Please leave this template in place to link the article histories and preserve this attribution. The former page's talk page can be accessed at Talk:Android (operating system).|
"The Simple Project"
It doesn't make much sense to have Basic4Android lumped under "The Simple Project" and then say that The Simple Project is no longer active while Basic4Android is very active. Why not change the heading to "Basic4Android"? 126.96.36.199 (talk) 12:27, 15 February 2012 (UTC)
This section needs to be both brought up to present and altered in tone from an advocatory "explaining away" of fragmentation issues to an objective reporting of the current state of affairs. Uptake of new Android versions is paralyzed due to manufacturer-specific implementations which can't be upgraded independently by users. Fragmentation is so severe that app and even Web developers are compelled to put extraordinary resources into testing and still can't reliably support all devices.
http://arstechnica.com/gadgets/2012/03/android-fragmentation-also-a-challenge-for-web-developers/ — Preceding unsigned comment added by 188.8.131.52 (talk) 15:43, 7 June 2012 (UTC)
- This is relevant to 0.9% of the customer base only. "Severe" is quite an overstatement. I have a few things to say about this.
- Web developers have been encouraged for years to use ems instead of pixels. Different screen sizes are not a problem except for the most ancient of websites.
- Android toolkit resizes at different resolutions.
- Resources in apks are at different resolution. (ldpi, mdpi, hdpi and xhdpi)
- The PC market is way more fragmented.
- As a developer I think this section is a load of selectively-researched FUD. It should go.--davidh.oz.au 05:20, 9 June 2012 (UTC)
the HyperNext issue
this section should be generic and include all such, including Caede at caede.curl.com G. Robert Shiplett 12:12, 5 November 2012 (UTC)
Merge ADB and Fastboot
- Done. Also merged in the article "Fastboot". If this article (Android software development) ever gets too large, the entire section "Software development tools" can be summarized and spun off to a new separate article. (I refactored the title of this talk section to include the subtitle: "Merge ADB and Fastboot".) Sparkie82 (t•c) 04:37, 28 December 2012 (UTC)
a handset emulator?
no mention of android studio?
http://developer.android.com/sdk/installing/studio.html#Updating — Preceding unsigned comment added by 184.108.40.206 (talk) 13:09, 12 February 2014 (UTC)
- There's already a separate article, Android Studio. — Dsimic (talk | contribs) 21:27, 12 February 2014 (UTC)
"officially supported": Eclipse or Android Studio ?
I am a little bit puzzled: In Sec. 1.1 someone says: "The officially supported integrated development environment (IDE) is Eclipse using the Android Development Tools (ADT) Plugin, though IntelliJ IDEA IDE (all editions) fully supports Android development out of the box" but when I visit the "Building Your First App" intro on https://developer.android.com/ it refers me to the community edition Android Studio. I am a newbie in Android development, so I would appreciate any clarification. Additionally Android Studio is labeled on its download page as "The official Android IDE" on 14. Jan. 2015. Treutwein (talk • contribs)
IDE on Android?
- There are unofficial Android-based dev tools. AIDE is one. I'll look for coverage and see if something can be added to the article. Reach Out to the Truth 04:17, 7 April 2015 (UTC)
- I agree that this encyclopedia article could use a few more words about developing software for Android directly on the Android device itself.
- This article briefly mentions "on Android itself, ... software development is possible by using specialized Android applications." with references to AIDE and JavaIDEdroid.
- Other tools for developing software for Android directly on the Android device itself include: the Spartacus Rex Terminal IDE (Wikibooks: Android/Terminal IDE); Python on Android; Scheme for Android; GNU Forth for Android; etc.
- Is there a good compromise between not mentioning any of these tools vs. listing all these tools and a bunch of detail on each one?
- On the one hand, I don't want to leave people who read this article, like the above commenter, with the incorrect impression that software to run on Android *must* always be written and compiled on some "full-size" computer.
- On the other hand, I don't want to go into so much detail on so many "developing on the Android device itself" tools that we give the incorrect impression that software to run on Android *is* usually written and compiled on the Android device itself.
- Does that help? --DavidCary (talk) 05:16, 19 December 2015 (UTC)
SCSK (Tokyo) CAEDE cross-platform framework
SCSK (Tokyo) CAEDE cross-platform framework not even mentioned although based on MIT's Curl expression-based programming language developed as a web alternative to LISP.