Real price of Android market transactions

by Yuri Ammosov » Fri, 13 Mar 2009 01:47:34 GMT


Sponsored Links
 Google claims it does not keep any revenue share save for a 30% carrier 
fee, however, with new Google Checkout fees 
( http://checkout.google.com/seller/fees.html ) the gross payback to 
developer becomes very different, in particular for lowest-priced apps.

For 0.99 apps

0.99 price to customer
0.30 carrier fee
0.29 flat Checkout fee
0.02 2% variable Checkout fee
0.61 total fees
0.38 developer's revenue
39% payback ratio

For 1.99 apps

1.99 price to customer
0.60 carrier fee
0.29 flat Checkout fee
0.04 2% variable Checkout fee
0.93 total fees
1.06 developer's revenue
53% payback ratio

How does this compare to Apple AppStore and third party Android apps? 
Are we in market or well below the market?

PS. Third party store owners interested in joint promo opps feel free to 
contact me directly.

(this might be a duplicate)

--~--~---------~--~----~------------~-------~--~----~



Real price of Android market transactions

by Incognito » Fri, 13 Mar 2009 06:49:17 GMT


 Below market.





Google claims it does not keep any revenue share save for a 30% carrier 
fee, however, with new Google Checkout fees 
( http://checkout.google.com/seller/fees.html ) the gross payback to 
developer becomes very different, in particular for lowest-priced apps.

For 0.99 apps

0.99 price to customer
0.30 carrier fee
0.29 flat Checkout fee
0.02 2% variable Checkout fee
0.61 total fees
0.38 developer's revenue
39% payback ratio

For 1.99 apps

1.99 price to customer
0.60 carrier fee
0.29 flat Checkout fee
0.04 2% variable Checkout fee
0.93 total fees
1.06 developer's revenue
53% payback ratio

How does this compare to Apple AppStore and third party Android apps? 
Are we in market or well below the market?

PS. Third party store owners interested in joint promo opps feel free to 
contact me directly.

(this might be a duplicate)





      


--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Real price of Android market transactions

by bouvetloz...@gmail.com » Fri, 13 Mar 2009 15:47:23 GMT


 Do you really have to pay the Checkout fees?
--~--~---------~--~----~------------~-------~--~----~



Real price of Android market transactions

by Yuri Ammosov - Sadko Mobile » Fri, 13 Mar 2009 16:00:08 GMT


 There is nothing on Checkout that suggests you do not have to.

On Mar 13, 10:47 am, "bouvetloz...@gmail.com" <bouvetloz...@gmail.com>


--~--~---------~--~----~------------~-------~--~----~



Real price of Android market transactions

by madcoder » Fri, 13 Mar 2009 21:22:09 GMT


 See the post here:




Real price of Android market transactions

by Streets Of Boston » Fri, 13 Mar 2009 22:32:15 GMT


 Yep,

For Android apps/games/etc, you pay 30% of your set price as a fee.
That's it.



> 



Other Threads

1. How can the vold detect the SD card insert/remove?

Vold use socket(PF_NETLINK, SOCK_DGRAM,NETLINK_KOBJECT_UEVENT)
(vold.c) to receive messages from kernel about add/change/remove
modules. When user insert sd-card, kernel create device object with
name /sys/devices/platform/.../mmcblk0 and send broadcast message to
user space...




-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Device Or Resource Busy on RFCOMM reconnect

I'm developing an application that interfaces with an RFCOMM endpoint.
Through bluetooth, my Droid phone connects to this device, initializes
it, and happily sends and receives data.

A problem I have encountered however is when I walk away from the
device (while it's sending/receiving) and the bluetooth connection
goes stale. I easily detect this in my code by various exceptions
thrown by the inputstream/outputstream/socket. When this happens, I
immediately "disconnect" from the endpoint by doing the following:

try {
  if (instream != null ) instream.close();
  if (outstream != null ) outstream.close();
  if (mobdSock != null ) mobdSock.close(); // this is the socket.
} catch... etc.

So after performing the above steps to officially "disconnect" the
dead connection I thought the connection is clean and ready for a new
connect()...

But what happens is when I come back into range of the device and try
to connect, I am unable to reconnect, no matter how many times I try.
connect() throws this exception: java.io.IOException: Device or
resource busy

The only way I can then reconnect to the device is to disable
bluetooth on my droid, then re-enable it. Then my app is able to re-
connect just fine.

BluetoothDevice -> BluetoothAdapter -> BluetoothSocket -> InputStream/
OutputStream.

I'm currently tearing down the connect from the socket to the right
(see above). Should I be tearing it down all the way down to the
adapter instead? or the device? By setting those to null so GC can
clean them up? This is the best idea I can come up with but it doesn't
feel right.

Thanks
Brad

-- 

3. Jual android di bandung

4. Issue with HelloWorld.

5. Adding additional activities to a project

6. Scrolling list of clickable 'rows'

7. TableLayout