If your app needs to launch on a specific day (it doesnt), it should have been uploaded and field tested at least a couple of weeks in advance.
If your app needs to launch on a specific day (it doesnt), it should have been uploaded and field tested at least a couple of weeks in advance.
In the past, we've handled this by submitting the app for review 24 hours in advance; luckily, that turned out to be just enough time to make our app go live this afternoon.
Google offers a “timed publishing” feature, but it only works for app updates, not for new apps. If Google is going to put apps through a multi-day review process, we need timed publishing for new apps as well.
And a quick word on soft launch periods: It’s ok, it’s not the worst thing, but it’s not preferable itself. Hence the need for a timed release tool.
Wow that's pretty presumptuous of you.
Or maybe it absolutely does? There are so many valid business reasons for deadlines whether due to contracts, school years, laws, whatever it is. Likewise that an app can't launch until a certain date due to licenses, agreements, tie-ins, servers, etc.
That's silly. Coordinated marketing around app releases is a big deal, and plenty of teams are cramming in features and bugfixes till the last minute.
~~~
The only thing a student can do is choose when to submit. Therefore the upload time should either be
1. given, (what a nice prof!)
2. unsurprising (i.e. on par with similar UX's of the age)
3. fuzzy (12:03am is okay, 8:57am is not)
4. determinable (e.g. via overwritable submission and a success notification)
There are a handful of important, ambiguous, and strict deadlines in the real world, so if that's what the prof is trying to teach, bravo. Or if they're trying to get students to do the test in #4. But that's rarely what's going on.
Disclaimer obviously I was one of those… X~D