Linked by Thom Holwerda on Tue 15th Oct 2013 21:53 UTC
Google

The stock launcher in Android 4.4 is getting a version number bump - from 3.x to 4.x - and it's also renamed to Google Experience. On top of that, something interesting is happening.

There's another interesting thing happening here. If you take a look at stock Android 4.3, you will see that the current launcher's package name is com.android.launcher. The new one is com.google.android.gel. Now look at Google's current selection of apps in the Play Store. Almost all of them start with "com.google.android" instead of "com.android."

[...]

I'm not saying with 100% certainty that we're going to see the launcher released to the Play Store, but to me, it certainly looks like it. At least eventually and not necessarily with KitKat.

Other currently integrated parts of Android also receive the name change in their packages. It seems like Google is finally doing what it should have done ages ago. If you can't get device makers and carriers to update Android, just put as much of Android as possible in the Play Store. If this also allows crapware-riddled devices from e.g. Samsung to be converted to proper stock, then that's a big plus too.

Please let this be true.

Thread beginning with comment 574786
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Developer Experience
by FunkyELF on Wed 16th Oct 2013 12:06 UTC in reply to "Developer Experience"
FunkyELF
Member since:
2006-07-26

- Provide a NDK that isn't a second class citzen

- Maybe bring Dart or Go to Android as well


I'm all for adding new languages but they should be able to be compiled like renderscript is, into an agnostic llvm bytecode.

Look at all the ARM specific stuff that won't run on Intel based Android.

Reply Parent Score: 2

RE[2]: Developer Experience
by ddc_ on Wed 16th Oct 2013 12:30 in reply to "RE: Developer Experience"
ddc_ Member since:
2006-12-05

I'm all for adding new languages but they should be able to be compiled like renderscript is, into an agnostic llvm bytecode.

NDK could just build packages for all supported architecture. IIRC go readily comes with compilers for multiple architectures.

FWIW Google could even accept packages in a "fat" format and split them into per-architecture Play packages during verification stage.

Reply Parent Score: 1

RE[3]: Developer Experience
by reduz on Wed 16th Oct 2013 12:59 in reply to "RE[2]: Developer Experience"
reduz Member since:
2006-02-25

NDK Already supports that since a long time, just throw your .so in the respective architecture dir and you can make a simple .apk that works on arm and x86, or even armv7 and armv6 together.

Reply Parent Score: 2

RE[2]: Developer Experience
by moondevil on Wed 16th Oct 2013 13:08 in reply to "RE: Developer Experience"
moondevil Member since:
2005-07-08

Look at all the ARM specific stuff that won't run on Intel based Android.


By default, when using the NDK toolchain binaries are produced to all supported processors.

As for Renderscript, I don't know anyone using it, because it is not portable across mobile platforms.

Reply Parent Score: 3