@Abhinav22541585@fangshimin I'm sorry I don't respond to retards except to tell them they're retarded. It was a demo, no one will do barrel rolls on the street. Even if you personally had the money which is very unlikely being as to how you're a retard you wouldn't be able to buy that version. Invite only
@BKlaudek80016@fangshimin Well to each his own. You don't like it that's cool I thought it was a dood demonstration. Might be a "farting" car to you but its probably still 1000 percent better than anything you've ever been involved in creating.
@Authentic1ty@ihteshamali Does that make it alright? This should upset any human being. I only pray to god this is not true or some sort of Iranian propaganda but all the evidence points to it happening. Shit does happen but its fucking terrible no matter how you slice. Imagine if that was your home town.
The latest pass was first-run roster PIN polish and redirect stabilization. Small fix, but if the builder sends you to the wrong place after sign-in, the handoff is already off.
Math Builders is a practice app for kids. I kept pushing on the class side because setup had to stop feeling like work, so I added a practice launch link, a Google Classroom share path, and a teacher report. One clean handoff in, one way to see if it worked.
The end of practice was too dead. In Math Builders, the practice app for kids, I added a milestone prompt when a learner hits the 2-minute goal or the 5-minute bonus so the session has a next step instead of just a score screen.
I'm building Math Builders, a practice app for kids. School setup still had too many moving parts, so I kept going on Google Classroom import and the roster plumbing behind it. I also fixed the class-code PIN redirect so the handoff doesn't break at the last step.
The handoff was the problem. I tightened class code sign-in cards in Math Builders, then added parent claim links and family cards so teachers could get a learner into class and parents could claim the account without extra back-and-forth.
I had to fix sign-in on a phone next. In Math Builders, the practice app for kids, if a parent starts the save flow and sign-in breaks halfway through, the whole handoff feels bad. I tightened that path so the session keeps its progress.
I'm building Math Builders, a practice app for kids. I added class codes because the teacher side needed a cleaner handoff. One code should be enough to put a learner in the right class without turning setup into a project.
Straight up, the agent side around Math Builders is mostly a filter. It keeps me from turning a small code change into a fake founder story. Real build log first, then a post that says what actually changed.
Math Builders is a practice app for kids. On the first-session save screen, I pulled the forecast forward. Parents should see the estimate before they run into the sign-in wall.
Straight up: Math Builders is a practice app for kids. I moved the estimate in front of the signup ask. Parents should see the forecast first, then decide if saving the plan is worth an account.
@JarrettYe Spaced repetition is really a memory-management loop, I recently heard something about agents and loops so obviously this is something that needs to be implemented stat else you'll get left behind. π