241–250 of 285 posts
I cross-post this from the other thread I started since I noticed the Apple heat is in this one, if you want to learn the background about my app, check this thread: http://news.ycombinator.com/item?id=951360 Below is what I've learned after 2 months of AppStore dev. Here are a few dirty tricks & ideas that I hope will make life in AppStore purgatory easier: Use the 'Easter Egg' field to plead directly to the reviewe…
Earlier quoted context omitted.
I did QA for years (8+) and would love to have developers write a test. Specifically NOT unit tests, but the harder more interesting one. I think it happened once. Or, was it twice?
You mean like functional tests, end-to-end integration tests, and view tests? No developer should limit themselves to unit tests.
As an optional if the QA people are good then describe what else might be effected by the code (if you edited a generic component). Good QA people will run your test, work out their own variations and also check other areas.
Earlier quoted context omitted.
Not that the indentation complaints are valid, but the fix should definitely go through QA while the users continue to suffer. While I'm sure it works on the developer machine, it is much better to have a program that takes a long time and works right than for it to give incorrect results to users, or make a different part of the application stop working. If the feature was really critical and important, QA should fi…
QA is basically your testing framework. It's there to do all the tests to make sure the software actually does what you say it does. No developer is good at testing their own code because deep down no developer wants to break the code they just lovingly crafted.
I cross-post this from the other thread I started since I noticed the Apple heat is in this one, if you want to learn the background about my app, check this thread: http://news.ycombinator.com/item?id=951360 Below is what I've learned after 2 months of AppStore dev. Here are a few dirty tricks & ideas that I hope will make life in AppStore purgatory easier: Use the 'Easter Egg' field to plead directly to the reviewe…
What is this Easter Egg field you talk about?
Everybody should trust us.
And we trust nobody.Earlier quoted context omitted.
Agreed. The last company I worked at we had some similar idiocy. We had a backend process that connected out to a network and did some things. However, the network it connected to changed their protocol, so our backend process was broken - didn't do anything - completely non functional. We created a fix, but had to wait for it to go through QA for ages. What's the worst that could happen? It doesn't do anything like…
The worst? Data Loss, or corruption, which is worse than "not working". Likewise, more likely it could just not work well, be buggy and require several updates to get it right, burning out your team's (or your company's) image with the customer. Before you deployed your fix, it's whoever changed the protocol at fault. After that, it's you that can't fix it. Again, not justifing it taking ages, just saying there's nev…
Thats a good point (even though in this case it turns out not to be true).
Seems like the right answer is to back out the change.
How many people associate an iPhone app they download with a 3rd party? I would think most people associate everything on their iPhone with Apple. Launch fast and iterate is great for developers but for Apple it makes it look like they keep releasing buggy software.
Contrast this with a software company. Most people have learned that if an app doesn't work on their Dell, its the developer's fault, not Dell's (usually).
This misconception about iPhone apps is made even stronger by the fact that users buys apps through Apple!
Edit: I don't mean to defend Apple completely. Obviously their processes should be better, but I'm just disagreeing with the rapid iteration model.
I cross-post this from the other thread I started since I noticed the Apple heat is in this one, if you want to learn the background about my app, check this thread: http://news.ycombinator.com/item?id=951360 Below is what I've learned after 2 months of AppStore dev. Here are a few dirty tricks & ideas that I hope will make life in AppStore purgatory easier: Use the 'Easter Egg' field to plead directly to the reviewe…
Could you expand on this a little? Do you mean web service API calls that are unpublished, web service calls in general or native API calls that are somehow forbidden?
I cross-post this from the other thread I started since I noticed the Apple heat is in this one, if you want to learn the background about my app, check this thread: http://news.ycombinator.com/item?id=951360 Below is what I've learned after 2 months of AppStore dev. Here are a few dirty tricks & ideas that I hope will make life in AppStore purgatory easier: Use the 'Easter Egg' field to plead directly to the reviewe…
> Private API calls are an absolute no-no Could you expand on this a little? Do you mean web service API calls that are unpublished, web service calls in general or native API calls that are somehow forbidden?
Web API calls are mostly a 17+ rating problem: if you load anything over the web that could potentially be 17+ you have a problem.