6 ms·
Obviously the article is a complaint from an app developer, but... sorry, I'm on Google's side here. Rushed, rapidly-updating, poorly-reviewed games with unvet
by ajross 7y ago
Obviously the article is a complaint from an app developer, but... sorry, I'm on Google's side here. Rushed, rapidly-updating, poorly-reviewed games with unvetted malfeatures are a plague. The last thing the smartphone community needs is "more apps faster".
I think a soft 3-day review period is very reasonable, even if it comes at the cost of making launch marketing harder for developers.
- dfabulich 7y agoOP here. We're happy to endure a three-day review process, but if it's going to take that long, then there needs to be a way to schedule an app release. Today, Google has a "timed publishing" system for app updates, allowing you to submit an app update today and schedule it to go live on a future date (after successful review). We need the same system for new app releases. Apple, which also has a multi-day review process for new apps, allows you to submit an app for approval and then hold it for manual release. After approval, you push the button on release day, and the app goes live immediately. Also: surprising us with this on release day is really unprofessional of them. The "we'll take more time" warning banner doesn't show up until after you submit the app. There was no way to know we had to submit early until it was already too late to act.
- squiggy22 7y agoStarted dipping my feet in app development recently. To get an app onto an Internal track for testing purposes..you still need to get 'reviewed'. literally a hello world app needs human review that takes 3 days. That blows my brain. Not open to the web. just testers. 3 days. painful. and imo. broken.
- dfabulich 7y agoLuckily, you only need to get internal track approval the first time. After that, you can deploy changes to your own team with fast, automated review. But, as my conversation with support showed, even after getting internal track approval, you'll need to wait another three days when you want to go live for production approval. ("It should be slightly quicker, but again we recommend three days just to be safe")
- iainmerrick 7y agoThere’s still a review process for the “internal” track even for an established app, and sometimes it gets held up. I think “internal” is a misnomer, it doesn’t seem to be handled any differently from a closed alpha channel.
- jiveturkey 7y agohow can they know? any app published on play store should have to be reviewed. if you just want internal testing, not open to the web, sideload it.
- colechristensen 7y agoYour post would benefit from focusing on the two real problems here * Lack of timed publishing feature * Lack of messaging about review until after submission The message isn't clear and people seem to be reacting to the three day process (not the problem) instead of the messaging and features around it.
- cannam 7y agoI thought the post was pretty clear on both of these things. I'm surprised that all the top-level comments here (at the time I write) are addressing only the longer review time - it seems clear enough that the real problem is that it's impossible to schedule a release properly.
- gray_-_wolf 7y agoIt's clear after reading the article, but imho the news title gives different impression.
- Deimorz 7y agoSo many people comment--on everything, not this post specifically--without reading anything more than the title of the HN post. They basically treat the title as a "topic suggestion" instead of reading the article itself. It's a pretty annoying behavior because it means that discussions often end up wildly off-topic or with a lot of comments missing the point, or just re-stating the exact same things that the article already said (often because people ask questions that the article answered, but they didn't read it). Unfortunately there's not really any good way to fix it. We had a big discussion about this same issue on Tildes recently too: https://tild.es/gjb https://tild.es/gjb
- gtirloni 7y agoHow about using a title that points to the real problem? "Google needs scheduled new app releases". Seems like a pretty good way to "fix" this, but I guess it wouldn't drive much traffic.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- jayd16 7y agoExpecting to flip a switch for an app rollout is an anti-pattern. There's going to be a pretty slow propagation no matter what the policy is.
- harrisonjackson 7y agoVery true. Even Apple's manual release can take 24 hours to be searchable in the app store. They do make this clear during the release process.
- zwily 7y agoBut at least you can have a “not before” policy, which is something you can work with in your marketing plan.
- djsumdog 7y agoWhat if there is a security update? I mean it sounds like this only applies to new apps, but if this gets extended to updates, you could have vulnerabilities out in the wild pending review.
- ldiracdelta 7y agoExactly. Hit this issue this week. I pushed out a change that had a bug, and the fix took 3 days... spent those days learning how to to do out of band updates from our own server in case hot fixes are needed.
- Mirioron 7y agoA 3-day review period isn't going to change anything here. You'll still have rushed, rapidly-updating and poorly-reviewed games.
- Gustomaximus 7y agoThis shouldn't make things harder for marketing. Have plans drafted and set dates after approval. As a marketer these 'launch the day the product is ready' goals don't usually get the best results. Often you burn power unnecessarily as you set activities up and then last minute delays are needed. This can loose money, goodwill with external parties and enthusiasm from the launch team. Or generally force to do things faster than you should properly plan and organise. I always found this fast launch a bit illogical. You get one launch. Teams sometimes spend years developing a product but don't want to wait a couple weeks/months for a better launch once a product is ready.