Aurora Mobile App Launch Preparation
Turn a meeting into clear tasks, decisions and a summary — nothing gets lost.
Sample of a real output
Summary
The Aurora team worked through the final details before the mobile app launch. They decided to push the public launch back by a week to allow for beta testing and to increase the launch marketing budget. Concrete tasks were assigned across development, marketing, and support, with deadlines by the end of the month.
Detailed minutes
Development status and release date
Mark summarized that the app is 90% complete, with the onboarding flow and push notifications still left to polish. The main open issue is stability on older Android devices, where beta testers occasionally see the welcome screen freeze.
After discussion, the team agreed to move the public launch from June 20 to June 27. The extra week of buffer is meant to cover one full beta testing cycle with real users and to fix reported bugs before the app reaches the App Store and Google Play.
Marketing and budget
Lucy presented the launch plan: an email campaign to the existing database, paid social media advertising, and a collaboration with three micro-influencers. After debate, the original budget of CZK 150,000 was raised to CZK 200,000 to also cover short videos for launch week.
Petra from customer support pointed out that the FAQ and response templates need to be ready before the initial surge of questions hits. It was agreed that support would get access to the beta build this week so they can collect typical user questions in advance.
Tasks
- Fix the welcome screen freezing on older Android devices and ship it to the beta build.
- Break down the CZK 200,000 marketing budget line by line and submit it for approval.
- Prepare the FAQ and response templates for customer support based on questions from the beta.
- Set up the collaboration with three micro-influencers and align their post timing with launch week.
- Assemble the beta tester group and send out invitations with bug-reporting instructions.
Decisions
- The public launch is moved from June 20 to June 27 to allow one full beta testing cycle. 💬 from transcript: „"Let's give it the extra week so we don't ship it broken and ruin the first impression."“
- The launch marketing budget is increased from CZK 150,000 to CZK 200,000. 💬 from transcript: „"Okay, I'm approving two hundred thousand, but I want it broken down line by line."“
- Customer support will get access to the beta build still this week. 💬 from transcript: „"Agreed, we'll release the beta to you by Friday so you have time for those templates."“
Key insights
- Stability on older Android devices is the biggest technical risk before launch and must be resolved within the beta cycle. 💬 from transcript: „"On older Androids the welcome screen freezes now and then, but on newer phones we don't see it at all."“
- Customer support needs early access to the beta build so they can prepare the FAQ for the initial surge of questions. 💬 from transcript: „"If we only get the beta a day before launch, we won't have the answers ready and we'll drown in tickets."“
- Short videos for launch week are the main reason for increasing the marketing budget. 💬 from transcript: „"Without at least three short videos for that launch week it won't work, and that doesn't fit into a hundred and fifty thousand."“
Debates
Launch the app on the original June 20 date, or push it back a week for beta testing?
The marketing campaign and advertising are already scheduled for that week; a delay throws off the timing of posts and influencers and could cost us part of the media space we've already booked.
Without a full beta testing cycle we risk shipping the app with a bug on older devices; bad early store reviews are hard to recover from afterward and would hurt user acquisition more than a one-week delay.
→ The team sided with moving the launch to June 27. The risk of damaging the first impression with bad reviews outweighed the inconvenience of rescheduling the campaign; Lucy was tasked with adjusting the marketing timing.
Data
- 200000 CZK Launch marketing budget (after increase) Increased from CZK 150,000 to cover short videos for launch week.
- June 27 date Rescheduled public launch date Pushed back by one week from the original June 20 due to beta testing.
- 90 % Current app completion status Onboarding, push notifications, and stability on older devices still need polishing.
- 3 people Number of micro-influencers in the collaboration Part of the marketing plan for launch week.
Unclear / risks
- It's unclear who gives final approval on the itemized budget — whether the team lead or upper management.
- It wasn't specified on how many specific older Android device models stability should be verified.
Transcript sample
All right, let's get into it. The main question today is whether we can make the launch on the twentieth, or whether we'll have to push it. Mark, where are we with development?
The app is basically ninety percent done; onboarding and push notifications are still left. But we have one problem — on older Androids the welcome screen freezes now and then, while on newer phones we don't see it at all.
That really worries me, because the whole campaign is scheduled for the twentieth. If we push it, it throws off the influencers and the advertising we've already booked.
I get that, but if we ship it broken, we'll get hit with bad store reviews, and that'll cost us more than a week's delay.
Okay. Let's give it the extra week so we don't ship it broken and ruin the first impression. We're aiming for the twenty-seventh. Lucy, please adjust the campaign timing.
And one request from me — give support the beta this week. If we only get it a day before launch, we won't have the answers ready and we'll drown in tickets.