I'm contacting users by changing comment of the app (this causes that
my comment goes to the top and users may read it). You can also spend
some characters of description but it is too small for it.
Both ways are just workarounds.
I also would like the feature to contact users (especially users t
Did they indicate what they would react to?
I just published my first app last week, and I've been really
frustrated not being able to respond to users comments! I was really
surprised at the lack of functionality in the Market for developers.
On May 21, 5:09 am, Tomáš Hubálek wrote:
> BTW: In
BTW: In different thread they said that the'll not react on petitions,
but I still think that this petition is good thing.
On 17 kvě, 11:42, rob irondad wrote:
> Hello, fellow developers,
>
> Just a quick update on the petition that was posted 3 months ago now,
>
> As of now it has been signed by
Well this petition was really about the Market specifically but I
agree with your remarks.
For what it's worth, IMHO, I believe some of the points in the
petition could be fixed quickly (for instance: the description length
limit), but for some (perhaps good) reason, nothing is happening.
Thanks.
On Mar 15, 3:25 pm, Greg Donald wrote:
> One thing, please add a mention about the lack of landscape oriented
> screenshots. I've yet to build anything portrait oriented, so every
> one of my Marketplace listings is affected by their lack of foresight.
The petition can no longer be updated :)
-
Just wanted to add my vote to this also. I have submitted our app to:
- Ovi Store
- Windows Mobile Marketplace
- iPhone App Store
- Samsung App Store (WM)
- Android Market
And not to start a riot here, but all of the above has better
functionality than the Android Market. Longer descriptions, more
I just signed. A must for anybody who has an app out with even just
modestly complex functionality.
Over the last weeks I've seen a shift to comments that are
predominantly negative in nature now.
There seems just no way any more to convey to users to visit the
accompanying web site and RTFM.
So t
Thank you for the advice! The "share this app" is an awesome idea ;)
My apps are little so features and bug fixes normally only take a few days,
instead of 14 days :)
But will give that a try if that's how Market defines Just in.
On Sun, Mar 14, 2010 at 6:15 PM, Yahel wrote:
> > But how do oth
> But how do other users discover my apps if the apps NEVER show up in the
> Just In category?
They do appear in the just in category when you first release them and
then every time you submit a new version as long as there was 12 days
minimum between two releases.
If you feel like releasing to o
But how do other users discover my apps if the apps NEVER show up in the
Just In category?
BTW, I don't think a 7-day release cycle is too often.
On Sun, Mar 14, 2010 at 12:04 PM, Yahel wrote:
> Your users don't have to wait 12 days.
>
> They are notified directly on their phones when there is
Your users don't have to wait 12 days.
They are notified directly on their phones when there is an update of
your app.
That's why Maps tells you you are going to annoy your current user if
you push non-vital updates too often just to try to get to the top of
the "just-in" list.
Yahel
--
You re
12 days now? I'm updating apps to push out new features, not to just to get
on top of the list.
My apps are actually suffering because of this stupid update cycle. Some
bug fixes and features I added in have to wait till the end of the cycle to
release in hope it gets to the top of the list.
Th
Wow,
When I signed I was the second name on the list, and now 1 000 :D
I thought it was just me.
Maybe with that kind of number Techcrunch could be interested.
I can see the headline : "The Android developer Revolt of 2010"
:D
Yahel
--
You received this message because you are subscribed to
You updated too soon. You'll have to wait at least 12 days to get into
the "just in" category.
Updating just to get into that list is going to annoy the heck out of
your users. Doing so on a regular basis will probably result in a lot
more uninstalls than happy users. Just keep that in mind.
-Joh
Hello again everybody.
I've made a new revision of the document, which I think you'll agree
has a nicer tone.
Please tell me what you think and I'll publish this so everybody can
sign it.
=> http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
PS: my messages have not yet been approved so I still c
Hello everybody.
I've posted a couple of messages to the other list but I am subject to
moderation as well right now.
I just wanted to say that if anyone wants to edit the current draft,
I'll be happy to 'invite' them through Google docs' collaboration
features. Just send me your email (has to be
Yeah, I finally realized I hadn't posted there before (odd, but true)
and that was probably what was going on.
I'm being patient -- I was just letting y'all know, since I had posted
here that I had posted there...trying to minimize the confusion.
Al Sutton wrote:
> Bob,
>
> If it's your first pos
I agree with most of your points but agree with some others that you
need to edit it for length and tone down the negativity.
Also, how about ability to receive emails for each sale made or daily
stats as an option?
On Feb 21, 7:43 am, Rob Irondad wrote:
> Hi fellow developers.
> I've come up
Bob,
If it's your first post to the list you'll have to wait for the
moderator to approve it. It will come through, but even moderators get
the weekend off :).
Al.
On Mar 1, 2:41 am, Bob Kerns wrote:
> I responded to you, Mark, and Al over there yesterday, but nothing has
> shown up. Perhaps I'
I responded to you, Mark, and Al over there yesterday, but nothing has
shown up. Perhaps I'm on moderation separately over there, as I've
not posted there before.
I'd rewrite the messages, no doubt better the second time, but that
would probably be incredibly confusing... :)
Bob Kerns wrote:
> T
+1
Good list. Some stuff less important and rather nice-to-have while
others are should-have-had-this-a-year-ago.
On Feb 21, 2:43 pm, Rob Irondad wrote:
> Hi fellow developers.
> I've come up with this text for a petition (warning: long):
>
> http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
>
>
Reply posted on [android-discuss]
On Feb 28, 12:34 am, Mark Murphy wrote:
> Rob Irondad wrote:
> > I just published a "final draft". Feedback / comments still welcome.
>
> >http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
>
> Please use a proper list for this sort of discussion, such as
> [andro
On Feb 27, 8:30 pm, Streets Of Boston wrote:
> And only a fraction of the 30% cut goes to Google for payment
> processing and running the martket infrastructure. The lion's share
> goes to the various carriers.
I use the Market almost always over Wi-Fi. Where does the carrier fit
into that pictur
Thanks, John, I think this is a lot more helpful -- even if I don't
entirely agree.
But I'm following Mark's lead and posting my response over on android-
discuss.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send
Point by point, here are my suggestions:
>> 1. A real website...
While I agree with the basic assumption, there are at least two other
places you can link to apps: http://www.androlib.com and http://www.cyrket.com
- While these are not official Android sources, they do use the market
API (unoffic
Rob Irondad wrote:
> I just published a "final draft". Feedback / comments still welcome.
>
> http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
Please use a proper list for this sort of discussion, such as
[android-discuss].
I'll be posting a reply to one of Mr. Kerns' posts over there shortly.
This assumes facts that, as near as I can tell, are not in evidence.
In fact, I expect they hold these cards rather close to their chest.
But we don't need to know. The point to be made here is simple (and
this could be more clear, I think):
This 30% -- which we assume is profitable in some way t
I don't, in fact, understand their predicament.
I presume they have one. They haven't communicated it, so I won't
pretend to understand it.
I'll settle for helping them understand my predicament, and hope they
can use that effectively in balancing their predicament.
Could you please identify in
And the good aspects of the current market would be? Besides not
having an Apple-style lock-in?
Seriously -- if I were a Google engineer, I would be a little offended
by your message. Personally, I give them more credit for being adults,
and not needing their feelings protected.
Nobody is calling
Thanks for the feedback.
Is there any way you both (John Coryat and 'Streets of Botston') could
provide me with an annotated version, with your suggestions on how to
make it sound better?
You can send me a mail to rob.iron...@gmail.com.
I don't think the current tone is that harsh, but I understa
Regardless, you won't get anywhere with demands, threats and being
angry. You need to work with the Android team not against them. The
best way to do that is be friendly, suggestive and show that you
understand their predicament.
I, for one, will not support such a document in the current form.
-
I have strong criticism to your criticism :D
We NEED a good tool in order to make the best of(and for) the android
platform.
Not we WANT !! We NEED !
And if google and the Android Team want to make it a success then THEY
HAVE to move.
The current market is a joke, and I'm very sad to learn from
Well said!
I agree with the gist of the document; many, but not all of the points
mentioned in the document are valid, but the 'demands' set a negative
tone, other parst are quite accusatory and the document should be
reworded to have 'suggestions' instead and convey a willingness to
cooperate.
An
I just read your "final draft" document and I have a strong criticism
as to the wording.
A petition like this is supposed to garner support for your ideas, not
alienate the very people who it's aimed at. The preamble of this
document is too negative, accusatory and essentially would derail the
ver
I just published a "final draft". Feedback / comments still welcome.
http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
--
Rob
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegr
@OP
> 5. Multiple versions of an app
Didn't notice it first time. Aren't we already able to target our apps
to specific API levels? Did that once, seemed to work.
@Ken H
> This is very frustrating to me too, but I think this is a stupid/lazy
> user issue, not Google's fault.
Google can't change th
Thanks for your replies everybody.
I'll try to incorporate all the feedback I received before publishing
the document to the place where we can sign it.
I hope we can agree on a final version soon - let's say, by this week-
end. If so I'll publish it Sunday then.
--
Rob
--
You received this mess
Tim et al,
I read both the petition and your piece, while I do agree with the
other poster that the maintaining of multiple versions is not my own
preference to approach the fragmentation, I think the petition raises
good points and Tim, I read through your whole post and could NOT
agree more to w
This is a good start. There are a few other features that would be
incredibly useful.
1) Better market search (as already suggested by Tim H.), including
autocomplete and commonly misspelled etc
2) Promo codes to give out to users and reviewers for free app
downloads
I also agree that we need a b
Thanks for your feedback.
Just a few comments:
> The "Visit the developers web page" is clickable. I think if your
> asking for clickable links "inside" your description then that may be
> asking too much. I mean if you want to say more then do it on the
> webpage.
Then the phrase "developer's w
I agree that the petition should be phrased a little more 'nicely' -
it shouldn't sound like a complaint form, even though it is ;)
On Feb 22, 11:20 am, Streets Of Boston
wrote:
> About the 325 char limit:
> Maybe i'm a little slow, but I discovered just recently that you can
> put a little more
I know ;)
I've done the research and published the work arounds :)
-Tim Strazzere
On Tue, Feb 23, 2010 at 2:46 PM, brucko wrote:
>
> > So throwing a T-Mobile sim card inside the Nexus One will net T-Mobile
> > with those fees. If you load up an Archos and use the Market Enabler,
> > T-Mobile
> So throwing a T-Mobile sim card inside the Nexus One will net T-Mobile
> with those fees. If you load up an Archos and use the Market Enabler,
> T-Mobile might get those too, depending if you use those tmobile
> "credentials" to access the market.
>
> The market is filtered by your carrier, then
Any android device, phone or not can have the market it on it. People
from other countries can also purchase paid applications if their
country has not yet been enabled.
This was the concept behind the "Market Enabler" and the research done
behind it. It's my understanding that the carrier that th
What carrier does that go to on nexus and such? Those devices don't have
assigned carriers, and the software load is created by google. (That 30% was
explained as incentive/payment for shipping the market, passing
compatibility tests, etc.)
On Tue, Feb 23, 2010 at 11:36 AM, Streets Of Boston wrot
Hekki wrote:
> Are you sure about the carrier thing ?
Yes.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy
_Beginning Android_ from Apress Now Available!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" gro
When you consider what 30% is of the average app, it amounts to 30 to
60 cents. Credit card processors charge a per transaction fee that
even large users are subject to. This varies from 10 to 30 cents.
Also, the credit card companies get somewhere between 2.1% and 4% as a
transaction fee. Since th
1. A real website
God, yes. Why is there not one?? There's Cyrket and AndroLib, but
Google should have done this first.
3. A way for developers to reply to comments
This is very frustrating to me too, but I think this is a stupid/lazy
user issue, not Google's fault. It's just as easy to email th
Disconnect wrote:
> Google has been very vague about where that 30% goes when you're on a
> nexus, adp, etc.
Yes, that's true.
Better yet, what about devices that just simply aren't phones?
Admittedly, I'm not aware of a non-phone with the Android Market on it
yet, but I presume it's only a matte
Well,
This is what Google told us at the Android Developers Lab. The bulk of
the 30% goes to the carriers, a fraction of this 30% goes to google to
run Google Checkout and the payment processor.
I guess the bulk of the 30% that goes to the carrier is an incentive
to have Android Market (and not o
Google has been very vague about where that 30% goes when you're on a nexus,
adp, etc.
On Tue, Feb 23, 2010 at 10:37 AM, Hekki wrote:
> Hi,
>
> Are you sure about the carrier thing ?
>
> I don't see when they are involved :
>
> Clients only use the carrier as a dumb pipe here to get internet
> a
Hi,
Are you sure about the carrier thing ?
I don't see when they are involved :
Clients only use the carrier as a dumb pipe here to get internet
access, they pay using google checkout which have their credit card
information(much like itunes does).
So google handle the payment itself.
When is t
Yep, you're correct.
Google gets only a small portion of the 30% to cover the costs of the
payment transactions. The bulk of the 30% goes to the carriers. At an
Android Dev Lab Google told us Google's share just covers their cost.
On Feb 22, 9:16 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> You
Thanks for the feedback.
I didn't know about the carrier's cut, this is interesting.
I still want to remind readers that the service is not free because I
think it is an important 'detail', but I'll rephrase this sentence to
make it more accurate / fair to Google.
--
Rob
On Feb 23, 3:16 am, "Map
I am not sure how many of us agree on item (1) in the petition. But I found,
google should really improve on the market website. I wanted to write an
android app. There is no way to know if the application already exists in
android market. What I see is list of featured paid/free apps. It does not
You might want to drop the "let's not forget" clause as it's something
that wouldn't help any petition and could keep people from agreeing
with you.
Google doesn't get 30% of your app sales, the carrier's cut, taxes,
fees for the merchant account and other costs eat that up to probably
zero profit
Brilliant idea! I wish google could seriously consider improve Android
market soon.
Thanks!
Alex
On Feb 21, 6:43 am, Rob Irondad wrote:
> Hi fellow developers.
> I've come up with this text for a petition (warning: long):
>
> http://docs.google.com/View?id=dd9hmc43_0c9zh58gd
>
> You're all welc
On Feb 21, 1:43 pm, Rob Irondad wrote:
> I've come up with this text for a petition (warning: long):
Excellent idea. I've pondered this myself, but hadn't gotten around to
doing anything (too busy working on my apps ;^). I think it
potentially has legs, especially if followed through:
- First, w
Thanks for the feedback!
I've updated the doc with the 350/325 chars correction.
I'll continue to update it with your feedback for a few days, and then
I'll publish it so everybody can sign.
PS: I too am afraid this might be useless, but at least when somebody
complains about the Market you can g
About the 325 char limit:
Maybe i'm a little slow, but I discovered just recently that you can
put a little more text into your app's description using FireFox than
when using IE.
IE adds 2 characters for each newline (\r\n), while FireFox only adds
1 char (\n only).
(and in FireFox, the screensho
For me the most important thing lacking is communication. Recent
Market updates, plans for the future? If they told us they're working
on features X and Y, and expecting to release an update by date Z, I
wouldn't worry so much. Or if they told us "we WILL NOT add features X
and Y because of Z". But
Hi,
Good initiative !
I would shorten the all thing so that it is read by more people. You
can for example leave everything that we all know and doesn't add to
the idea : " (you couldn't include a screenshot in your app's
description before then)."
But it's a good idea and it would be time for g
62 matches
Mail list logo