Why Android market is still bad news for devs ...

by SoftwareForMe.com SoftwareForMe.com » Fri, 30 Oct 2009 04:56:49 GMT


Sponsored Links
 I agree that it is a little disappointing that there is no better protection
scheme, and that the losses hurt.

A quick story: our app, PhoneMyPC, a PC remoting app is a combination
application and hosted service. The phone and PC use our servers to
cooperatively get connected for each remote control session. This makes
PhoneMyPC ideal for people inside corporate firewalls, or who just don't
want to bother configuring for RDP or VNC.

We are nearing the end of a [protracted] Beta program. In the beginning, we
were hosting on port 443. Several weeks ago we switched to a different port
(temporarily), and kept both services running while users downloaded the new
release.

Most people moved to the new server within a week, but a large body (half of
all connections using our service) never moved at all. After more than two
weeks, we discontinued service on the old port, and there has not yet been a
single support contact as a result.

We made the decision to disconnect the old service even though it was still
being well used because we discovered our app being sold illegally on one of
the websites talked about in this group.

So, our "retention for pay" rate is also about 70%, yet we believe as many
as half of the people using our application (or at least possessing it) have
acquired it outside of the Android Market (and hence are not automatically
getting updates).

For our purposes, Google could trivially enable us to protect our resources
by adding any phone identifier into the Google Checkout records, such as
phone number or IMEI, so that we could tie phones running our app back to
thei purchase records.

Scott,
SoftwareForMe.com


On Thu, Oct 29, 2009 at 8:12 AM, admin.androidsl...@googlemail.com <





-- 
Warm regards,
The PhoneMyPC Team

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



Why Android market is still bad news for devs ...

by SoftwareForMe.com SoftwareForMe.com » Fri, 30 Oct 2009 05:32:20 GMT


  agree.

I was thinking Phone# is better than IMEI, because 99% of people take their
phone numbers with them.

But, I thought if someone got a new number, I could query for sufficient
details to "re-enabled" from the old checkout record.

Actually, it seems the best would be simply embedding the Google Checkout
transaction ID in the APK somehow, or otherwise making it available.

Scott,
SoftwareForMe.com

On Thu, Oct 29, 2009 at 2:04 PM, Streets Of Boston
<flyingdutc...@gmail.com>wrote:



--
Warm regards,
The PhoneMyPC Team

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


Sponsored Links


Why Android market is still bad news for devs ...

by Sean Hodges » Fri, 30 Oct 2009 06:26:22 GMT


 On Thu, Oct 29, 2009 at 9:31 PM, SoftwareForMe.com SoftwareForMe.com



Woh there. Drop that percentage by a good amount SoftwareForMe.com...

Just like you, I take my number with me. But the majority of people I
know don't. I'm not saying 99% of people DON'T keep their numbers -
just suggesting that my friends, family and colleagues can't all
squeeze into that remaining 1% :)

I still don't see the appeal for DRM, there are plenty of other
options - licence keys, periodical payments, and pay-for upgrades...
All of which avoid having to double your support efforts just because
people like to change their phones and email addresses.

I consider the Android Market as a "app shop"; it is a place to get
your software noticed and shipped. Not as a means to an end for
developers when considering piracy protection, distribution methods,
and payment options.

Having said all that, improvements to the market will always be
welcomed. I just think the issues listed against the current AM should
not be a big deal to any serious developer who doesn't whittle their
time away making the next fart soundboard app for 5. Yes, the Android
Market is insufficient in certain areas, but anyone serious about
selling mobile apps will also consider options outside of the Android
Market.

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



Why Android market is still bad news for devs ...

by Sean Hodges » Fri, 30 Oct 2009 06:32:56 GMT


 On Thu, Oct 29, 2009 at 10:24 PM, admin.androidsl...@googlemail.com



You have a point here. I am one of the users that can't buy from the
Android Market. If the app cannot be purchased from something other
than Google Checkout, then I seek alternative apps. Many others I
know, however, would rather just jump to the nearest torrent site and
get the app illegitimately.

The solution is to offer other ways to buy the app, and advertise
them. Alternative markets are one way, and direct selling is another.
Hopefully the Android Market will improve it's International payment
process, but even then it is not a good idea to rely on a single
distribution method.

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



Why Android market is still bad news for devs ...

by Felipemnoa » Fri, 30 Oct 2009 07:56:12 GMT


  also agree. 
It wont stop piracy but it will no longer be as simple as copy and paste. Now
if somebody wants to pirate your app they will need to spend hours.

On Oct 29, 2009, at 5:31 PM, "SoftwareForMe.com SoftwareForMe.com"
<softwareforme....@gmail.com> wrote:

I agree.

I was thinking Phone# is better than IMEI, because 99% of people take their
phone numbers with them.

But, I thought if someone got a new number, I could query for sufficient
details to "re-enabled" from the old checkout record.

Actually, it seems the best would be simply embedding the Google Checkout
transaction ID in the APK somehow, or otherwise making it available.

Scott,
SoftwareForMe.com

On Thu, Oct 29, 2009 at 2:04 PM, Streets Of Boston <flyingdutc...@gmail.com>
wrote:

I wouldn't use IMEI or phone-number.
App purchases are linked to a google account. If a user switches to a
new phone, they'd need a new activation and this can mean support
headaches for the app developer.

Google should give us a good way to identify the user as he/she is
tied to his/her google-account that was active when the app was
downloaded from the Android Market. It should not be the account-name
itself (privacy) but some proper hash of it that remains unique.

On Oct 29, 4:56 pm, "SoftwareForMe.com SoftwareForMe.com"
<softwareforme....@gmail.com> wrote:




--
Warm regards,
The PhoneMyPC Team






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



Why Android market is still bad news for devs ...

by Pierre Henry Perret » Fri, 30 Oct 2009 13:01:35 GMT


 Yes TransactionID , or sort of...

We have done here at Echovox, a LinkProvider that enables code confirmation
sent by SMS.

This could be of great help here.

--
Pierre-Henry Perret
mob1: +41 (0) 76 769 80 76 (Suisse)
mob2: +33 (0)6 85 86 75 26

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



Other Threads

1. Is there some plan to support USAT for 3G

Hi there,

I have seen on the cupcake roadmap that the release includes a SIM application 
toolkit (STK) :

    " This feature will enable the SIM to initiate actions for various 
operator-specific value-added services. "

        1.     http://source.android.com/roadmap
        2.     http://source.android.com/roadmap/cupcake
Is there any plan to support USAT (USIM Application
Toolkit), the SIM Application Toolkit for 3G (commonly referred to as STK).

My target is to use a Generic Bootstrapping Architecture (GBA) for a network 
authentification.

 
SIM Application Toolkit (commonly referred to as STK) :
            http://en.wikipedia.org/wiki/SIM_Application_Toolkit
            http://bladox.com/devel-docs/gen_stk.html
            http://en.wikipedia.org/wiki/USIM_Application_Toolkit
 
USAT (USIM Application
Toolkit) :
3GPP TS 31.111 Universal
Subscriber Identity Module (USIM) Application Toolkit (USAT)

http://www.3gpp.org/ftp/Specs/html-info/31111.htm
 
Thanks ins advance for your reply.

Best regards


Thierry GAYET
NextInnovation.org
+33(0)663.849.589


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

2. Notepad tutorial and the case of the missing setListAdapter() method

I am working through the Notepad tutorial and am noticing my project
will not compile.

The last line of the fillData() method in the Notepadv1.java file
references this method.  I have searched unsuccessfully to find it.
Can someone provide me insight about where this method is so I can get
my project to compile?

Thanks

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

3. AChartEngine - a charting library for the Android platform

4. How can I install Hello world project to G1 phone? How can I install using Eclipse with ADT??

5. Is there an easy way to make EditText look like TextView but still behave like EditText?

6. Is there an easy way to make EditText look like TextView but still behave like EditText?

7. Multiline text input