Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

As my applications finally come through the testing process, I am noticing that along with the now supposedly improved speed of submissions (over 90 days for some of mine), I am getting alot of notes in the passed with notes and other issues sections that seem to me to be either extremely picky, just plain wrong, or known issues.

For instance, one note I recently got was "There is no visual warnings for low battery". There is a known issue on the T720 where low battery warnings subsequent to the first one will not suspend the app and will not display a warning. Also if you happen to be rapidly pressing the keys that respond to this message (as in a normal shoot em up gameplay...well.....I did my part..I am suspending...if you keep hitting the key it's not MY fault..)

IMHO it is NOT appropriate to be putting this kind of information in the documentation that goes to the carriers.

Will a new carrier be smart enough to understand that displaying low battery warnings is not the responsibility of my app?

Here is another one: "The documentation states that the application does not auto save either user initiated or auto save when in fact the game does both" For my app this is simply not true. This game has absolutely no auto save or save feature, and cannot be exited and then re-entered and resumed from a saved game.

Shall I waste time trying to fight every one of these 'notes' that is appearing?

I got one note telling me that because the user was pressing the shoot key so rapidly, they may inadvertently respond to an incomming SMS message with ignore (which is the select key apparently). So what!? This is a GAME! You want me to not use the select button?

Ugh! I guess I am just in a pissy mood today...but it was bad enough having to rush many of these things through True Brew with the 2 weeks notice on policy change we got months ago, but now to have these different and often wrong or irrelevant notes coming through.....aaaarg!

I hope the carriers do not start rejecting apps for this type of stuff...

I ignore all the notes. I've never had a problem getting a game on a carrier because of notes. %99 of notes are total nonsense.

I ignore all the notes. I've never had a problem getting a game on a carrier because of notes. %99 of notes are total nonsense.

Quote:Originally posted by flarb
I ignore all the notes. I've never had a problem getting a game on a carrier because of notes. %99 of notes are total nonsense.
Thanks.

Quote:Originally posted by flarb
I ignore all the notes. I've never had a problem getting a game on a carrier because of notes. %99 of notes are total nonsense.
Thanks.

my theory is the more time a tester has been working at NSTL, the less notes you get in your test results.
I've gotten a lot of phone bugs reported in my notes as well, but life goes on.
NSTL will take care of them if you ask them (I sometimes do if its "passed with notes" because of a phone bug), but considering things are backed up they might not get to them.

my theory is the more time a tester has been working at NSTL, the less notes you get in your test results.
I've gotten a lot of phone bugs reported in my notes as well, but life goes on.
NSTL will take care of them if you ask them (I sometimes do if its "passed with notes" because of a phone bug), but considering things are backed up they might not get to them.

From what I have seen notes don't usually prevent an app from being picked up by a carrier. An important use of the notes is for the carriers own tech support. Each carriar has to plan on dealing with support calls related to BREW apps and haivng these notes is important documentation.

From what I have seen notes don't usually prevent an app from being picked up by a carrier. An important use of the notes is for the carriers own tech support. Each carriar has to plan on dealing with support calls related to BREW apps and haivng these notes is important documentation.

Quote:my theory is the more time a tester has been working at NSTL, the less notes you get in your test results.
Absolutely that's how it feels. Some of the notes are simply ridiculous and plain out incorrect, indicating that the tester has had no experience at all and understood neither the application nor the handset limitations in many cases. In other cases it seemed as if the testers felt they were misunderstood game designers and had to impose their opinion on you. Either way they are doing absolutely nothing for anyone.
Typically what I do is if I get notes back, I add comments to the submission documentation of future versions, adding these particular points as "Unexpected application behavior by design" in the documentation so that at the very least they won't show up in the next round of certifications.

Quote:my theory is the more time a tester has been working at NSTL, the less notes you get in your test results.
Absolutely that's how it feels. Some of the notes are simply ridiculous and plain out incorrect, indicating that the tester has had no experience at all and understood neither the application nor the handset limitations in many cases. In other cases it seemed as if the testers felt they were misunderstood game designers and had to impose their opinion on you. Either way they are doing absolutely nothing for anyone.
Typically what I do is if I get notes back, I add comments to the submission documentation of future versions, adding these particular points as "Unexpected application behavior by design" in the documentation so that at the very least they won't show up in the next round of certifications.