Hello all! My name is Luke, and I'm a 14 year old with a idea for SSC. This is my first SSC submission ever. I would like some feedback concerning a question.
My app is an AI powered academic planner that helps you and your life. I won't give too much away, but I believe it's a really helpful concept. It uses a mini on-device LLM (built with simple if this word typed then do this logic) to help organize assignments.
This is a real business I am building, and I put inside of my app simulated features such as the app saying "scanning your Google Classroom..", would this go against any terms and make the app less likely to win?
I also have my app fully polished, and feels like an actual app and finished product, with demo assignments pre-loaded, and most stuff is placeholders. Should the app be more like a guided simulator? Such as "click here to see how this will be simulated in a final release" or again should it be polished?
I just want some feedback, since I only have 3 minutes, and the app needs to be offline, I just want to improvise.
Hopefully I can get some feedback from the community, and/or ex-winners! Thanks all! And good luck! :) - Luke
Hello Luke,
It is encouraging to learn about your interest in participating in the SSC and developing an AI-powered academic planner. Based on your inquiries, I would like to share some personal opinions and feedback. Please be aware I’m not in the Swift Student Challenge team nor I know their process. I encourage other engineers to post their opinions here.
Using simulated features such as “scanning your Classroom” is a common practice in prototyping, particularly when API access or live integrations are not feasible due to time constraints, limited internet access, or API restrictions. As long as it is evident to the judges that these features are simulations and you clearly communicate their intended functionality, it should not adversely affect your chances. Transparency is paramount, consider including a brief note or disclaimer in your presentation or documentation to clarify that certain features are simulated.
Presenting a polished version demonstrates your design skills, attention to detail, and provides a tangible representation of the user experience. Judges, in my opinion, often appreciate seeing a fully-realized concept, even if some functionalities are placeholders. This approach can be effective if your objective is to focus on specific workflows or key features. It may guide judges through the most critical aspects of your application without delving into excessive details.
Given the time constraint and offline requirement, you may consider combining both approaches. For instance, have a polished interface with key interactive elements prepared, but also prepare a few scripted interactions or a walkthrough that highlights the core functionalities and potential user journey?
Utilize feedback from this submission to further refine your application. Engage with potential users to gain their perspectives and iterate based on real-world needs.
Best of luck with your submission, Luke! Remember, passion and clarity in communicating your idea can significantly impact the outcome.
Albert Pascual Worldwide Developer Relations.
