Here is a suggestion for Google.
Pirates have very clear buying patterns. Most can be spotted easily.
Analyse the market for buyers who repeatedly buy apps and then get a
refund in under 5 minutes. Then block those users.
I can see these guys normally pirate 2 of my apps in the space of 5
minute
I see the download figures have dropped across all apps. Though that
is probably inline with the adjustment described in the blog post.
I believe the market still has "troubles" though - yesterday around
30% of users who tried to purchase my app cancelled - due to their
downloads failing.
On a ty
Actually it is nicely explained here:
http://developer.android.com/guide/topics/manifest/uses-sdk-element.html
On Thu, Jul 15, 2010 at 10:08 PM, Samuel Lawson wrote:
> When you compile you won't be able to use any APIs introduced after
> your target SDK.
>
> It won't
When you compile you won't be able to use any APIs introduced after
your target SDK.
It won't prevent your app from appearing on earlier devices, that's
purely down to the your minimum SDK chosen.
Of course make sure you test on the the minimum SDK you define - to
check your app behavior and chec
Why don't you just set your target sdk higher?
On Thu, Jul 15, 2010 at 6:38 PM, Pent wrote:
>> At any rate, the correct thing for an app developer to do is
>> explicitly state which features they care about, and you can there use
>> android:required="false" to tell Market not to filter your app b
5 matches
Mail list logo
