AWS Builder Center

Full Stack Challenge: QuestForge

When AWS Full Stack Challenge dropped the word ATLAS, I didn't think geographic maps. I thought about tabletop RPG campaigns - worlds half-sketched on graph paper, lore scattered across Google Docs and Discord threads, maps no one can edit together. That's exactly the problem QuestForge was built to fix.

Vision and What It Does

QuestForge is a real-time collaborative worldbuilding platform for tabletop RPG players. You create a world, open the canvas, place markers - cities, dungeons, dragon lairs - and collaborators see every change instantly. No refresh, no resending files. Think Figma for fantasy maps.



Full Stack Breakdown

Pitch: "Collaborative worldbuilding in real time." That one sentence kept scope tight across the 48-hour sprint.
Prototype: I proved the core mechanic before touching Amplify - a static Konva canvas with drag-and-drop markers serializing positions to JSON cleanly. If state wasn't clean here, sync would break everywhere else.
MVP: Cognito auth, world creation, and a live canvas with AppSync subscriptions syncing markers across tabs.
UX: The dark fantasy aesthetic isn't decoration - it's the product. Cinzel headings, Inter body text, and a five-color palette (void  #1A0A2E , gold  #C9A84C , parchment  #F5E6D0 ). Dark mode is the default.
Launch: Amplify Hosting CI/CD. Every push to main deploys automatically. A live URL by hour 3 meant I could test on mobile throughout.



How You Built It

I evaluated Leaflet, fabric.js, and tldraw before picking react-konva. Konva shapes map directly to React components and every element's position is plain  {x, y}  - easy to store in DynamoDB and broadcast over WebSockets.
Real-time sync uses element-level last-write-wins. Each marker is a separate DynamoDB item. Mutations fire optimistically, AppSync broadcasts to subscribers filtered by  worldId . No CRDTs needed for a 48-hour demo where users rarely touch the same element simultaneously.
Two gotchas: react-konva breaks SSR ( dynamic(() => import('./MapCanvas'), { ssr: false })  fixes it), and AppSync subscriptions broadcast to all clients by default - filtering by  worldId  at the schema level is easy to miss when moving fast.



AWS Services and Architecture

Browser → Amplify Hosting (CloudFront)
└── Next.js App
├── Cognito (auth)
└── AppSync (GraphQL + WebSockets)
├── DynamoDB
└── Lambda + Bedrock (lore generation)

Service
Role
Amplify Gen 2
Hosting, CI/CD, TypeScript type generation
AppSync
GraphQL API + real-time subscriptions
DynamoDB
Worlds, map elements, lore entries
Cognito
Email sign-up and sign-in
Lambda + Bedrock
AI-generated lore via Claude (stretch)



What I Learned

Amplify Gen 2's TypeScript schema auto-generates the GraphQL API, types, and subscriptions - I didn't write a single resolver. The AppSync subscription model (push over poll) clicked fast once I stopped thinking in intervals and started thinking in events. Biggest lesson: build the risky core mechanic first. I had a syncing canvas by hour 22 of 48; everything after was polish. That's not how most hackathons go for me.



Links

Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article