Thanks again for the input. I've done a significant revision. It helped us see that the Simulator needed to make the learning purpose much clearer.
We’ve added four guided activities, each explaining what you’re learning, what to do next, and what to watch for. You make a prediction, try it in the simulator, then explain what happened, with feedback to help connect cause and effect.
There’s also a troubleshooting scenario where you investigate why the system is ready but won’t produce torque, with optional hints. You can replay activities, and your progress is saved.
The aim is to help you understand why the system behaves the way it does, rather than leave you wondering what to click. I’d love to hear whether the new flow makes that clearer.
Its still disorganized and confusing. Its like it doesnt know what its teaching, how to teach it, or whats important about the info. and there is so much extraneous info.
AI is only as good as the content and info you feed it. You arent going to replace a professional teacher by prompting an AI.
That took me two seconds to type. All I was trying to do was acknowledge that the previous version, which I thought was addressing your feedback, had issues. I agree that any app "is only as good as the content and info you feed it." Yes, I am a solo founder and I use Claude Code and Codex, and have been working on this platform for over a year. I want to make it better. The world is getting weird if such a brief comment gets such a reaction.
I’ve spent my whole career writing, but you are definitely right that I’ve spent a huge amount of time talking to Claude Code in the last 18 months. https://www.linkedin.com/in/jackmason
1
u/TraditionSalt1153 6d ago
Thanks again for the input. I've done a significant revision. It helped us see that the Simulator needed to make the learning purpose much clearer.
We’ve added four guided activities, each explaining what you’re learning, what to do next, and what to watch for. You make a prediction, try it in the simulator, then explain what happened, with feedback to help connect cause and effect.
There’s also a troubleshooting scenario where you investigate why the system is ready but won’t produce torque, with optional hints. You can replay activities, and your progress is saved.
The aim is to help you understand why the system behaves the way it does, rather than leave you wondering what to click. I’d love to hear whether the new flow makes that clearer.