As we failed to meet our desired user & revenue goals during Week 3, I propose we shift our focus for the next week entirely towards short-term gains. That means removing any protocol around type/data safety - as long as it works, and there is a < 1% chance of user data loss, we push it through. We do not have the time to waste on following our regular practices 100%. At the end of week 4, I will comb through the changes made to our codebase & identify any clean-up that needs to be made, however in the interest of said desired gains on user engagement, this clean-up will not be made until the end of the S4 incubator period. The only improvement to our programming practices will be a tightening of beaurocracy when it comes to the commit & log history/movements, and a greater adherence to the Jira tickets that are created. No features should be added until they have been added to Jira and have been shown how they will enhance our signups or our user retention.

Here are some of the smaller technical goals I will be setting out to achieve this game week:

  1. More ways to earn Silfur → community events, quizzes, competitions
  2. David will look into the commenting issue → but this is not a priority, as the number of classifications being made remains negligble, and therefore the importance of a fully-working commenting system is reduced significantly (for now, anyway)
  3. Improve user-facing dashboard, landing page for non-authenticated users, and the creation of a fully-fledged admin dashboard using Dashibase & our self-hosted instance of Supabase
  4. Planet difficulty/rating category (relying on Rhys for the finalisation of the Jira ticket) & status updates/reports for the classification state for individual planet entities. I guess this would include the creation of a public-facing protocol to be followed to mark planets as complete → cross-referencing with exofop database would suffice for now after a certain number of transactions/classifications that provide useful data. Next step is finding data sets that aren’t already 100% sorted, and further exploring the ethical ML usecases → what’s the fucking point, basically?
  5. Filter system for /tests/planets route
  6. Review the voting system implementation & performance on end-user devices
  7. Obviously adding some more planets….
  8. I think we need to look into creating an algo to generate images based on the surface-level data that the lightcurve generates; this algo should be plugged into the Unity generator as well.

I propose that we investigate the competitive aspect in-depth, as it could provide an adequate precursor to the media juggernaut we intend to put together post-S4.

I will be heading into the field this week, more significantly than I have at any point during the development lifecycle of Star Sailors, and will be working closely with Rhys & Nathan to ensure we meet our required user goals during week 4. I will be meeting with David on Thursday and post-Tender, we will have a plan in place which I will relay to R & N that will be immediately executed.

Of course, the Talonova website needs to be created as well 😫😫😫 Welcome to TaloNova Rhys/Lee: