But how can you not remember if I've me that the sound? How can you not remember I logged in? With a handful of ultrabasic bugs it feels like they just didn't even try.
If they are network issues why do I get stuck in a try again later screen were the only thing I can do is force quit the app?
It's a lazy as hell and Nintendo should be ashamed that someone's dragging their name down like that.
The real killer? I love the idea of this app. I'd probably end up spending a bunch of money on it if I kept it around for a couple months, because I don't have the time I need to play it the free way. It's fun (or it at least scratches that grindy type itch), and it's the only game I've ever been able to play with my partner. I'm on the verge of uninstalling right now though, because every time I get the chance to play, the app dies in my hands.
This doesn't just happen when in "catch a pokemon" minigame mode. This happens at all screens. The game was programming to expect full, 100% network connectivity, and if it loses that for even a brief moment, the whole thing comes crashing down, requiring a full kill and reset.
Can someone explain this? Isn't the value of a game in the playing of it? If a millionaire could pay to have hundreds of Pokemons spawning in their living room so they can get more points than anyone without leaving the house, what would be the point? If you're having fun playing with your girlfriend, but don't have much free time, why would paying to catch up matter? Did they design it to be limited gameplay, where you only get a teaser if you don't play it all the time, requiring that you buy things in order to get any real gameplay time out of it?
to it I'd add that this is also the difference between the $20/hour programmer and the $200/hour programmer -- speaking in broad strokes, knowingly, and if you'll indulge me charitably. Because the difference between the commodity "let's ship something!" programmer/engineer and the one who truly knows his/her stuff, and who truly thinks about and knows about and cares about the edge cases, the big picture, the total system, all possible states in the state machine space, is what justifies those differences in (ostensible) upfront cost.
If you only want "the user is in location X and so icon Y should be rendered on their screen at point P" then you can get that pretty cheap, at globalization-plus-crowdsourced-plus-cloud-reduced prices
But if you want that above but also, with good performance, correctness, stability, scale, all edge cases handled reasonably and gracefully, and in v1.0, and well documented, and with good English, and maturity, curtesy, legality, i18n, etc... well, then you're going to pay. Or you should expect to pay. There's no such thing as a free lunch. Ever. If you think you have a free lunch, or a reduced cost lunch, then all it means is that somebody else off-stage is paying for that difference. And that difference may come back to bite you.
You could have a hundred "$200/hour programmers" on the team for this app, but if management says they need to ship three weeks early to catch the buzz, or something like that, it doesn't matter. We can't say the developers were bad. I mean it's possible, given how poorly the game handles network disconnections, among other bugs. But unfortunately we don't live in a utopia where the guys writing the code get to decide when they want to release. Or if features get added in the last minute. Etc.
in many situations, an owner/manager/lead is making decisions where, frankly, the company has no revenue so they know their ostensible default spending path is equivalent to a ticking time bomb.
or... they don't truly know whether or how well the engineer can deliver, yet they do know for sure definitively what their dollar spend will be. thus, the results we see.
But TBH, that is probably not about how much the engineering team is paid, it's about what culture they have. Nintendo's console development teams would never ship something with this many catastophic bugs. Niantic has probably decided that the way they're doing things is "industry standard" (within the context of mobile and their particular silo) and does not need substantial improvement.
Edit: How poor is this code, you ask? It does not let me rename my Pokemon. A race condition occurs where it tries to pop up the Android keyboard and close it at the same time.