But Apple does filter apps. Wonder how great this feels when Apple decides to 
forbid you to sell your app, potentially after you've spent quite a 
considerable sum (and developer time needs to be billed too, that's one of the 
classical accounting errors of small business starters, the business needs to 
show a profit after the owner's work has been payed), now what?

You are forced to target jailbroken iPhones, which is in no way comparable to 
rooting G1s (the G1 image is mostly opensource, Apple's iPhone OS is not).

Reasons why being a "commercial" mobile developer sucks, business-wise: 
(uncomplete lists)

- iP: you are completely at mercy. Apple decides what to list, when to list and 
so on.
- iP: restocking fees seem to be a quick qay to go bankrupt, nice isn't it?
- An: no sales figures, so how should one even do a coarse calculation if the 
business makes sense?
- An: while not as crazy as the Apple relationship, you are still the insect 
cooperating with an elephant. Small changes in the environment by Google can 
ruin you easily.

While there are some "success stories" on the iPhone market, none have reached 
a point where they make more business sense than working as a consultant.

Plus how many apps on the iP make even 1000USD?

Andreas

Al Sutton <[email protected]> hat geschrieben:

>
>With Google there is no concept of "unpaid spare time", just project time,
>20% time and overtime :). From what I've seen Google have a "we own
>everything you do related to our any of " clause in their contracts (e.g.
>see clause 19 in
>http://google-hiring-experience.blogspot.com/2006/01/google-employment-contr
>act-28th.html) 
>
>Even if you see someone hacking at home as "unpaid time" why have Google put
>their name to and provide PR help to a single product developed by one of
>their employees in a field that the community is serving?
>
>In a later email that was sent before your reply I clarified that;
>
>I can't think of the last time I heard a developer say "Apple copied my app
>*after* it had been listed on AppStore"
>
>Al.
>
>---
>
>* Written an Android App? - List it at http://andappstore.com/ *
>
>======
>Funky Android Limited is registered in England & Wales with the 
>company number  6741909. The registered head office is Kemp House, 
>152-160 City Road, London,  EC1V 2NX, UK. 
>
>The views expressed in this email are those of the author and not 
>necessarily those of Funky Android Limited, it's associates, or it's 
>subsidiaries. 
>
>
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of Mark Murphy
>Sent: 09 April 2009 11:24
>To: [email protected]
>Subject: [android-discuss] Re: Google competing with devs...
>
>
>Al Sutton wrote:
>> (OI safe is an open
>> source free product, and although secrets looks the same Google is 
>> paying the for the development time on secrets whereas OI safe is 
>> written by volunteers in their unpaid spare time).
>
>And your proof of this is...what, exactly?
>
>What if the Googlers in question wrote their applications (Secrets,
>Panoramio, WikiNotes, etc.) "in their unpaid spare time"?
>
>> One thing I give Apple a lot of respect for is that they don't produce 
>> apps to compete with the developers they are trying to encourage to 
>> use their platform.
>
>The Konfabulator guys would beg to differ. Admittedly, it's not iPhone, but
>in the passage I quoted above, you didn't limit your scope to iPhone.
>
>--
>Mark Murphy (a Commons Guy)
>http://commonsware.com | http://twitter.com/commonsguy
>
>_The Busy Coder's Guide to Android Development_ Version 2.0 Available!
>
>
>
>
>
-- 
Sent from my Android phone with K-9. Please excuse my brevity.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to