Urgent.News

What's breaking now, across thousands of outlets.

Tech

MoneyVerse: a financial literacy game for kids.

๐Ÿš€ MoneyVerse: A Financial Literacy Game for Kids | Sanity Challenge This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange ๐ŸŽฎ What I Built I built MoneyVerse , a financial-literacy game for kids aged 8โ€“12. Pip, a piggy-bank guide, walks players through three missions: ๐Ÿ›๏ธ Needs vs. Wants: A 24-coin outing budget with trade-offs and opportunity cost. ๐Ÿท Savingsโ€ฆ

MoneyVerse is a financial literacy game designed for children aged 8 to 12. In the game, players are guided by Pip, a piggy-bank character, through three missions. In the first mission, players learn the difference between needs and wants by managing a 24-coin outing budget, considering trade-offs and opportunity cost. The second mission involves a savings quest, where players start with 100 coins and aim to save for a 150-coin bicycle, learning about simple interest along the way.

The third mission is a lemonade stand, where players manage supply costs, pricing, and profit by subtracting expenses from revenue.

The game's technology stack includes the Next.js framework with React 19 and TypeScript for the frontend, Tailwind CSS for styling, Sanity v6 as the Content Management System (CMS), and GROQ queries for data retrieval. Studio Customization allows for custom schemas for lesson, mission, and playerProgress content types, as well as a review workflow with draft, inReview, and approved states, and actions to send for review and approve. The game also features a custom CoinField input and a mission play preview.

For live content updates, defineLive is used, which enables published missions to appear without requiring a redeploy. The app can be accessed through a demo link, and the source code is available on GitHub. The development process began on September 30th and concluded on October 4th, with the majority of work completed in the last two days due to a birthday on the third day.

Initial plans included building the game as a Progressive Web App (PWA) with Google authentication, but these features were later removed due to added complexity.

Written by urgent.news from Dev.to's reporting โ€” not their text. Machine-written โ€” may contain errors; check the original before relying on it.

Read the original at dev.to โ†’

More in Tech

If You Can't Draw the Boundary, You Don't Have an Architecture

The boundary question ended my whiteboard round before it started. The interviewer asked where my system ended. I listed components. He said I had just described the whole company. He was right.

  • The interview focuses on system boundaries to assess architectural thinking.
  • Team boundaries, not just technical ones, often cause project failures.
  • The 4-seam checklist (auth, payments, third-party data, shell) helps define boundaries.

Is Vercel Speed Insights enough for Core Web Vitals monitoring?

Agencies often turn on Vercel Speed Insights for a Next.js client, see route-level Core Web Vitals, and assume monitoring is โ€œdone.โ€ For that Vercel project, the product is genuinely useful.

  • Vercel Speed Insights offers route-level Core Web Vitals monitoring for Vercel-hosted projects.
  • It does not cover other platforms like WordPress, Shopify, or Magento.
  • Agencies use Speed Insights for Vercel sites and third-party tools for other domains.

Week 32: Learning From the Students Who Are Already Finding Their Way

One thing we are learning while building BAINT is that we cannot only look for students who are struggling We also need to learn from students who are already finding ways to understand difficultโ€ฆ

  • Learn from students excelling in complex subjects.
  • Identify unique learning behaviors of successful students.
  • Design personalized learning platform catering to diverse styles.

Four Mindset Shifts for Teams Adopting Elixir

How immutability, explicit data, pattern matching, and result values change software design. The first warning sign usually appears after the team is already productive. People know the syntax.

  • Immutable values over mutable state
  • Declarative transformations instead of imperative instructions
  • Functions over methods on objects

More from Sunday 4 October โ†’