http://www.theregister.co.uk/2010/07/26/android_billing/
Now Google will be allowing phone operators to accept payments for
developers apps that are bought using the Google app market. The same
phone operators who take a 70% cut of sales instead of a 30% cut
that's taken by Google, Apple, and Microsoft.
|
|
0
|
|
|
|
Reply
|
scarface_74 (203)
|
7/27/2010 9:40:18 PM |
|
On Jul 27, 2:40=A0pm, KDT <scarface...@yahoo.com> wrote:
> http://www.theregister.co.uk/2010/07/26/android_billing/
>
> Now Google will be allowing phone operators to accept payments for
> developers apps that are bought using the Google app market. =A0The same
> phone operators who take a 70% cut of sales instead of a 30% cut
> that's taken by Google, Apple, and Microsoft.
um, neither the article you linked to, nor the blog post that links
to, mentions a 70% cut- are you just assuming that it'd be a 70% cut?
if not, got a link? carrier billing, in general, is an improvement
for the customer imo.
|
|
0
|
|
|
|
Reply
|
ed
|
7/27/2010 9:58:03 PM
|
|
On Jul 27, 5:58=A0pm, ed <n...@atwistedweb.com> wrote:
> On Jul 27, 2:40=A0pm, KDT <scarface...@yahoo.com> wrote:
>
> >http://www.theregister.co.uk/2010/07/26/android_billing/
>
> > Now Google will be allowing phone operators to accept payments for
> > developers apps that are bought using the Google app market. =A0The sam=
e
> > phone operators who take a 70% cut of sales instead of a 30% cut
> > that's taken by Google, Apple, and Microsoft.
>
> um, neither the article you linked to, nor the blog post that links
> to, mentions a 70% cut- are you just assuming that it'd be a 70% cut?
> if not, got a link? =A0carrier billing, in general, is an improvement
> for the customer imo.
This is how carriers generally operate......
http://www.businessinsider.com/the-real-reason-wireless-carriers-love-andro=
id-google-is-paying-them-to-2010-3?utm_source
(Carriers used to charge developers 50% or more from the apps they
sold on dumb phones like the Motorola Razr; that's revenue that the
iPhone App Store and others wiped out, which is one reason carriers
got scared of App Stores. But if Google is funneling that revenue
along to the carriers, it's going to make them happy.)
---------
You already see that once Carriers get their hands on Android devices
and without Google fighting them what they are doing to the devices
--- locking them down, forcing irremovable crapware, etc. Do you
really think they are going to settle for a 30% cut or try to go back
to the good old days?
|
|
0
|
|
|
|
Reply
|
KDT
|
7/27/2010 10:29:38 PM
|
|
On Jul 27, 3:29=A0pm, KDT <scarface...@yahoo.com> wrote:
> On Jul 27, 5:58=A0pm, ed <n...@atwistedweb.com> wrote:
> > On Jul 27, 2:40=A0pm, KDT <scarface...@yahoo.com> wrote:
>
> > >http://www.theregister.co.uk/2010/07/26/android_billing/
>
> > > Now Google will be allowing phone operators to accept payments for
> > > developers apps that are bought using the Google app market. =A0The s=
ame
> > > phone operators who take a 70% cut of sales instead of a 30% cut
> > > that's taken by Google, Apple, and Microsoft.
>
> > um, neither the article you linked to, nor the blog post that links
> > to, mentions a 70% cut- are you just assuming that it'd be a 70% cut?
> > if not, got a link? =A0carrier billing, in general, is an improvement
> > for the customer imo.
>
> This is how carriers generally operate......
>
> http://www.businessinsider.com/the-real-reason-wireless-carriers-love...
>
> (Carriers used to charge developers 50% or more from the apps they
> sold on dumb phones like the Motorola Razr; that's revenue that the
> iPhone App Store and others wiped out, which is one reason carriers
> got scared of App Stores. But if Google is funneling that revenue
> along to the carriers, it's going to make them happy.)
>
> ---------
>
> You already see that once Carriers get their hands on Android devices
> and without Google fighting them what they are doing to the devices
> --- locking them down, forcing irremovable crapware, etc. =A0Do you
> really think they are going to settle for a 30% cut or try to go back
> to the good old days?
i don't deny that the carriers undoubtedly would like more of a cut.
but you apparently have nothing to support either the 70% cut you
quoted, nor anything to support that the android market cut is going
to change? did you just make all that up?
|
|
0
|
|
|
|
Reply
|
ed
|
7/27/2010 10:39:35 PM
|
|
In article
<1eac3eb7-d8e9-4e24-bd2a-80eea532b979@f15g2000vbq.googlegroups.com>,
KDT <scarface_74@yahoo.com> wrote:
> http://www.theregister.co.uk/2010/07/26/android_billing/
>
> Now Google will be allowing phone operators to accept payments for
> developers apps that are bought using the Google app market. The same
> phone operators who take a 70% cut of sales instead of a 30% cut
> that's taken by Google, Apple, and Microsoft.
It is increasingly clear that Google's _sole_ strategic goal with
Android is to piss in Apple's cornflakes, to make sure Apple is never in
a position to lock them out of some large fraction of the smartphone
market. They don't really care what else happens. Horrible
fragmentation? Fine. Hardware vendors who know nothing about software
platforms screwing up user experience? Whatever. Carriers inserting
themselves into revenue streams they have no business being part of?
Sure. Companies cutting deals with Yahoo after building devices around
Google's free software? OK.
As long as carriers and established handset push enough Android units to
prevent Apple from achieving the same kind of dominance they did with
music players, Google doesn't seem to care what else happens.
The big question is, if Google manages to undermine Android's quality
throughly enough, will it even matter in the long run how many companies
they have pushing handsets? I really have no idea.
--
"The game of professional investment is intolerably boring and over-exacting to
anyone who is entirely exempt from the gambling instinct; whilst he who has it
must pay to this propensity the appropriate toll." -- John Maynard Keynes
|
|
0
|
|
|
|
Reply
|
ZnU
|
7/28/2010 1:55:24 AM
|
|
In article
<9c58dc03-a289-47ca-9e36-a61ef7483582@f6g2000yqa.googlegroups.com>,
ed <news@atwistedweb.com> wrote:
> > > >http://www.theregister.co.uk/2010/07/26/android_billing/
> >
> > > > Now Google will be allowing phone operators to accept payments for
> > > > developers apps that are bought using the Google app market. �The same
> > > > phone operators who take a 70% cut of sales instead of a 30% cut
> > > > that's taken by Google, Apple, and Microsoft.
> >
> > > um, neither the article you linked to, nor the blog post that links
> > > to, mentions a 70% cut- are you just assuming that it'd be a 70% cut?
> > > if not, got a link? �carrier billing, in general, is an improvement
> > > for the customer imo.
> >
> > This is how carriers generally operate......
> >
> > http://www.businessinsider.com/the-real-reason-wireless-carriers-love...
> >
> > (Carriers used to charge developers 50% or more from the apps they
> > sold on dumb phones like the Motorola Razr; that's revenue that the
> > iPhone App Store and others wiped out, which is one reason carriers
> > got scared of App Stores. But if Google is funneling that revenue
> > along to the carriers, it's going to make them happy.)
> >
> > ---------
> >
> > You already see that once Carriers get their hands on Android devices
> > and without Google fighting them what they are doing to the devices
> > --- locking them down, forcing irremovable crapware, etc. �Do you
> > really think they are going to settle for a 30% cut or try to go back
> > to the good old days?
>
> i don't deny that the carriers undoubtedly would like more of a cut.
>
> but you apparently have nothing to support either the 70% cut you
> quoted, nor anything to support that the android market cut is going
> to change? did you just make all that up?
First, he didn't "quote" anything. This was his claim:
The same phone operators who take a 70% cut of sales
He supported that by linking to an article that claimed:
Carriers used to charge developers 50% or more from the apps they
sold on dumb phones like the Motorola Razr
While 70% isn't specifically mentioned, it is certainly contained
within the "or more" part of the above substantiation. So it's either
an exaggeration, or KDT has personal non-linkable knowledge about
carrier cuts.
But it's painfully obvious that he didn't "apparently have nothing".
--
Sandman[.net]
|
|
0
|
|
|
|
Reply
|
Sandman
|
7/28/2010 8:55:41 AM
|
|
"ZnU" <znu@fake.invalid> wrote in message
news:znu-CAC351.21552327072010@Port80.Individual.NET...
> In article
> <1eac3eb7-d8e9-4e24-bd2a-80eea532b979@f15g2000vbq.googlegroups.com>,
> KDT <scarface_74@yahoo.com> wrote:
>
>> http://www.theregister.co.uk/2010/07/26/android_billing/
>>
>> Now Google will be allowing phone operators to accept payments for
>> developers apps that are bought using the Google app market. The same
>> phone operators who take a 70% cut of sales instead of a 30% cut
>> that's taken by Google, Apple, and Microsoft.
>
> It is increasingly clear that Google's _sole_ strategic goal with
> Android is to piss in Apple's cornflakes, to make sure Apple is never in
> a position to lock them out of some large fraction of the smartphone
> market. They don't really care what else happens. Horrible
> fragmentation? Fine. Hardware vendors who know nothing about software
> platforms screwing up user experience? Whatever. Carriers inserting
> themselves into revenue streams they have no business being part of?
> Sure. Companies cutting deals with Yahoo after building devices around
> Google's free software? OK.
>
> As long as carriers and established handset push enough Android units to
> prevent Apple from achieving the same kind of dominance they did with
> music players, Google doesn't seem to care what else happens.
>
> The big question is, if Google manages to undermine Android's quality
> throughly enough, will it even matter in the long run how many companies
> they have pushing handsets? I really have no idea.
Apple will never dominate this market segment - too many good competitors.
|
|
0
|
|
|
|
Reply
|
XX
|
7/28/2010 11:05:00 AM
|
|
On Jul 27, 6:39=A0pm, ed <n...@atwistedweb.com> wrote:
> On Jul 27, 3:29=A0pm, KDT <scarface...@yahoo.com> wrote:
>
>
>
> > On Jul 27, 5:58=A0pm, ed <n...@atwistedweb.com> wrote:
> > > On Jul 27, 2:40=A0pm, KDT <scarface...@yahoo.com> wrote:
>
> > > >http://www.theregister.co.uk/2010/07/26/android_billing/
>
> > > > Now Google will be allowing phone operators to accept payments for
> > > > developers apps that are bought using the Google app market. =A0The=
same
> > > > phone operators who take a 70% cut of sales instead of a 30% cut
> > > > that's taken by Google, Apple, and Microsoft.
>
> > > um, neither the article you linked to, nor the blog post that links
> > > to, mentions a 70% cut- are you just assuming that it'd be a 70% cut?
> > > if not, got a link? =A0carrier billing, in general, is an improvement
> > > for the customer imo.
>
> > This is how carriers generally operate......
>
> >http://www.businessinsider.com/the-real-reason-wireless-carriers-love...
>
> > (Carriers used to charge developers 50% or more from the apps they
> > sold on dumb phones like the Motorola Razr; that's revenue that the
> > iPhone App Store and others wiped out, which is one reason carriers
> > got scared of App Stores. But if Google is funneling that revenue
> > along to the carriers, it's going to make them happy.)
>
> > ---------
>
> > You already see that once Carriers get their hands on Android devices
> > and without Google fighting them what they are doing to the devices
> > --- locking them down, forcing irremovable crapware, etc. =A0Do you
> > really think they are going to settle for a 30% cut or try to go back
> > to the good old days?
>
> i don't deny that the carriers undoubtedly would like more of a cut.
>
> but you apparently have nothing to support either the 70% cut you
> quoted, nor anything to support that the android market cut is going
> to change? =A0did you just make all that up?
So do you really think that Google is not going to still want their
cut for running the Market on top of the carriers cut?
|
|
0
|
|
|
|
Reply
|
KDT
|
7/28/2010 11:30:56 AM
|
|
In article <u9U3o.3855$mW5.582@newsfe14.iad>, "XX" <zs@orangegrove.org>
wrote:
> "ZnU" <znu@fake.invalid> wrote in message
> news:znu-CAC351.21552327072010@Port80.Individual.NET...
> > In article
> > <1eac3eb7-d8e9-4e24-bd2a-80eea532b979@f15g2000vbq.googlegroups.com>,
> > KDT <scarface_74@yahoo.com> wrote:
> >
> >> http://www.theregister.co.uk/2010/07/26/android_billing/
> >>
> >> Now Google will be allowing phone operators to accept payments for
> >> developers apps that are bought using the Google app market. The same
> >> phone operators who take a 70% cut of sales instead of a 30% cut
> >> that's taken by Google, Apple, and Microsoft.
> >
> > It is increasingly clear that Google's _sole_ strategic goal with
> > Android is to piss in Apple's cornflakes, to make sure Apple is never in
> > a position to lock them out of some large fraction of the smartphone
> > market. They don't really care what else happens. Horrible
> > fragmentation? Fine. Hardware vendors who know nothing about software
> > platforms screwing up user experience? Whatever. Carriers inserting
> > themselves into revenue streams they have no business being part of?
> > Sure. Companies cutting deals with Yahoo after building devices around
> > Google's free software? OK.
> >
> > As long as carriers and established handset push enough Android units to
> > prevent Apple from achieving the same kind of dominance they did with
> > music players, Google doesn't seem to care what else happens.
> >
> > The big question is, if Google manages to undermine Android's quality
> > throughly enough, will it even matter in the long run how many companies
> > they have pushing handsets? I really have no idea.
>
> Apple will never dominate this market segment - too many good competitors.
That's not a bad wild ass guess, but another not bad wild ass guess is
that when/if the iPhone becomes available on more carriers in the US, it
might.
--
Lloyd
|
|
0
|
|
|
|
Reply
|
Lloyd
|
7/28/2010 12:47:30 PM
|
|
On Jul 28, 4:30=A0am, KDT <scarface...@yahoo.com> wrote:
> On Jul 27, 6:39=A0pm, ed <n...@atwistedweb.com> wrote:
> > On Jul 27, 3:29=A0pm, KDT <scarface...@yahoo.com> wrote:
>
> > > On Jul 27, 5:58=A0pm, ed <n...@atwistedweb.com> wrote:
> > > > On Jul 27, 2:40=A0pm, KDT <scarface...@yahoo.com> wrote:
>
> > > > >http://www.theregister.co.uk/2010/07/26/android_billing/
>
> > > > > Now Google will be allowing phone operators to accept payments fo=
r
> > > > > developers apps that are bought using the Google app market. =A0T=
he same
> > > > > phone operators who take a 70% cut of sales instead of a 30% cut
> > > > > that's taken by Google, Apple, and Microsoft.
>
> > > > um, neither the article you linked to, nor the blog post that links
> > > > to, mentions a 70% cut- are you just assuming that it'd be a 70% cu=
t?
> > > > if not, got a link? =A0carrier billing, in general, is an improveme=
nt
> > > > for the customer imo.
>
> > > This is how carriers generally operate......
>
> > >http://www.businessinsider.com/the-real-reason-wireless-carriers-love.=
...
>
> > > (Carriers used to charge developers 50% or more from the apps they
> > > sold on dumb phones like the Motorola Razr; that's revenue that the
> > > iPhone App Store and others wiped out, which is one reason carriers
> > > got scared of App Stores. But if Google is funneling that revenue
> > > along to the carriers, it's going to make them happy.)
>
> > > ---------
>
> > > You already see that once Carriers get their hands on Android devices
> > > and without Google fighting them what they are doing to the devices
> > > --- locking them down, forcing irremovable crapware, etc. =A0Do you
> > > really think they are going to settle for a 30% cut or try to go back
> > > to the good old days?
>
> > i don't deny that the carriers undoubtedly would like more of a cut.
>
> > but you apparently have nothing to support either the 70% cut you
> > quoted, nor anything to support that the android market cut is going
> > to change? =A0did you just make all that up?
>
> So do you really think that Google is not going to still want their
> cut for running the Market on top of the carriers cut?
if i had to guess, i would suspect that google and the carriers would
split their cut. we'll see though. but you certainly don't have to
things up in the mean time (about the numbers, or about what i think).
|
|
0
|
|
|
|
Reply
|
ed
|
7/28/2010 3:24:32 PM
|
|
ed <n...@atwistedweb.com> wrote:
>
> what do you think supports the 70% figure? =A0"50% or more..." =A0that's
> seriously weak support- to the point that i say it's no support at
> all.
YMMV. It should hardly be surprising to a reasonable individual that
there may perhaps be information availble to some of us that isn't
necessarily unlimited public knowledge. For example, there's NDA's
(Non-Disclosure Agreements) which often may include a provision where
one isn't free to mention if an NDA applies or even exists on a
subject (until its expiration, for example).
As such, someone might point to some topic and suggest that August 2nd
might have some significance, and you won't find out why today...but
you very well might find out on August 3rd. Or perhaps even further
removed than that.
As such, the cited reference that does clearly say "50% or more", does
IMO lend credence, even without it being exactly the same number
because if utterly nothing else, the reference at least doesn't
contradict the statement. Yes, there's still uncertainty remaining,
but there's not a red light, either.
-hh
|
|
0
|
|
|
|
Reply
|
hh
|
7/28/2010 9:49:31 PM
|
|
On Jul 28, 3:00=A0pm, Sandman <m...@sandman.net> wrote:
> =A0ed <n...@atwistedweb.com> wrote:
<snip>
> Well, what you say is support or not isn't all that interesting to me
> at all, really.
we're clearly not understanding each other, yet again, my comments are
not interesting to you, and i'm not that interested in what you have
to say either, so let's just end this conversation.
and as previously suggested, maybe we don't have conversations at all,
eh? ;D
<snip>
|
|
0
|
|
|
|
Reply
|
ed
|
7/28/2010 10:10:16 PM
|
|
In article
<38b99b2b-9431-4697-b739-bd48a1719d43@x21g2000yqa.googlegroups.com>,
ed <news@atwistedweb.com> wrote:
> > Well, what you say is support or not isn't all that interesting to me
> > at all, really.
>
> we're clearly not understanding each other, yet again, my comments are
> not interesting to you
What you claim is support isn't interesting to me, no. Especially when
you use that to disregard obvious support.
I'm just pointing out your incorrect statements, and ironicaslly -
when you base your argument on your perceived implication of another
poster (that was really fun) and I'm also obviously teaching you the
English language.
--
Sandman[.net]
|
|
0
|
|
|
|
Reply
|
Sandman
|
7/29/2010 8:56:42 AM
|
|
ZnU <z...@fake.invalid> wrote:
> =A0KDT <scarface...@yahoo.com> wrote:
> >http://www.theregister.co.uk/2010/07/26/android_billing/
>
> > Now Google will be allowing phone operators to accept payments for
> > developers apps that are bought using the Google app market. =A0The sam=
e
> > phone operators who take a 70% cut of sales instead of a 30% cut
> > that's taken by Google, Apple, and Microsoft.
>
> It is increasingly clear that Google's _sole_ strategic goal with
> Android is to piss in Apple's cornflakes, to make sure Apple is never in
> a position to lock them out of some large fraction of the smartphone
> market. They don't really care what else happens. Horrible
> fragmentation? Fine. Hardware vendors who know nothing about software
> platforms screwing up user experience? Whatever. Carriers inserting
> themselves into revenue streams they have no business being part of?
> Sure. Companies cutting deals with Yahoo after building devices around
> Google's free software? OK.
>
> As long as carriers and established handset push enough Android units to
> prevent Apple from achieving the same kind of dominance they did with
> music players, Google doesn't seem to care what else happens.
>
> The big question is, if Google manages to undermine Android's quality
> throughly enough, will it even matter in the long run how many companies
> they have pushing handsets? I really have no idea.
This might shed some light:
<http://mobile.venturebeat.com/2010/07/28/android-wallpaper-app-that-
steals-your-data-was-downloaded-by-millions/>
YMMV, but it is a pretty ringing endorsement for Apple's approach,
despite the so-called 'evils' of the 'Walled Garden'.
-hh
|
|
0
|
|
|
|
Reply
|
hh
|
7/29/2010 1:22:32 PM
|
|
|
13 Replies
140 Views
(page loaded in 0.167 seconds)
Similiar Articles: Getting rid of libstdc++? - comp.unix.programmerThe reason it is now defined is that the ... whenever the ABI changes, the gcc developers change name mangling as well, so as to avoid ... few C++ namemangled names and the needed ... Casting between 64bit and 32bit - comp.unix.programmerAnother way to avoid warning is to convert in following manner ... of this decision one can say Windows tried to keep ... (But that still means there's really no reason for ... How best to detect duplicate values in a column? - comp.databases ...... delete the one I want and keep another that ... to a 2-inch-wide column to avoid ... request new features, as the developer thinks of things to change for whatever reason ... Intel Visual Fortran Error Message - comp.lang.fortranHello, I' working on another of a large collection of ... you don't have to memorize a list of keywords to avoid ... this immediate issue, and I hope you can help me keep ... SAS and SATA (arrays) on one controller (LSISAS1068)? - comp ...Keep up the act, you're quite convincing. ... > In addition, another reason, is we were forced to not mix SAS ... about a time 10 years ago or so where I needed to ... Uninitialized variables, why do they equal their name? - comp.lang ...Just wondering what (if any) technical reason is behind ... I'll make this easier so that, if he forgets some needed ... far as advocating enabling NOVALUE or even just avoiding ... Web-Safe Fonts? - comp.fontsAfter all, it's _you_ who decide to keep the font ... to do, but then _no_ font-family setting is needed. ... not available, or just won't be used for one reason or another?). Misuses of RTTI - comp.lang.c++.moderatedOnly use RTTI if you have a very good reason to do so and ... Just like you should avoid using goto statements in ... Goto and RTTI are not the tools to keep at the very top ... The nightmare begins... - comp.databases.filemakerI just keep telling myself "baby steps, baby steps". I've almost always avoid programming ... had a client who needed that level of reliability, but some developers I ... why fopen64()? - comp.unix.solarisThe reason for this is that such files might be ... been converted to use off_t whereever it may be needed ... direct use interfaces are primarily for library developers ... DSP Job opening in Sacramento, CA - comp.dspTo keep in mind the reality. As I said in my ... And another reason could be that you already have, for ... handgun, in Placer County California, and all I needed ... improve strlen - comp.lang.asm.x86Another example is barrel shifts, and shld ... the 5% too frequently, even better, avoid ... Number of > registers needed is small here, too. All the more reason that counting ... Sampling: What Nyquist Didn't Say, and What to Do About It - comp ...So the CMR fonts are embedded as needed to make the ... This is another one of those things where I think ... is /slightly/ too wide for comfort, but I'd avoid two ... RESIGNATION OF STEVE JOBS!! - comp.sys.mac.systemThis is just a switch to another CPU. > The Mac now is ... When a supplier fails to at least keep up with current ... It is one of the prime reasons I personally avoid ... Swing uses bad features - comp.lang.java.guiThe reason is in the order in which calls are made: 1 ... anyway initialized to null, so it is better to avoid ... Furthermore you may just call another super constructor ... Mobile - Facebook DevelopersKeep them there by letting them connect with their ... into your mobile web app across all iOS and Android ... out some of the great mobile experiences that developers ... | Android DevelopersIf it starts another activity, that activity is ... to the application, is created when it's needed and ... does not get removed if it crashes for some reason. android ... 7/21/2012 9:45:29 PM
|