hoGAMEGATA.

Technical Specificationv2.0
About the project

Minimalistic, No BS and it just works.

The project is named hoGAMEGATA, where the prefix "ho" denotes horror, and GAMEGATA is the abbreviated technical slang of "game mega metadata". It aims to eliminate modern web fatigue by functioning strictly as a lightweight discovery layer.

01

Project Vision & Philosophy

Why?

"I created this to solve a problem, people (or atleast me, sighs...) have is that to find good games to play! Now you don't have to search for a game on Google, read it's reveiws, go to Steam or somewhere looking for it, realizing it doesn't have co-op so you can't play it with your friends! Duh, just use hoGAMEGATA. And yes, buy games to support the creators.."

Target

An user must be capable of discovering and learning about the game, and supporting a developer by purchasing the game within seconds. No ads or BS.

02

Technical Stack Map

Framework

Next.js (App Router)

Server-side rendering, routing logic, static/dynamic regeneration capabilities, and strict component separation.

Database

Supabase (PostgreSQL)

Relational game metadata storage leveraging a free-tier hosting node with standard PostgreSQL optimizations.

Schema Mapper

Prisma ORM

Strict schema mapping, type-safe database queries, and declarative relational mapping for nested tables.

Styles & UI

Tailwind CSS + shadcn/ui

Utility-first styling with custom dark-palette and no light mode!

Search Engine

MiniSearch Engine

Ultra-fast, client side memory indexing for basic autocorrect and autofill features.

Infrastructure

Vercel Infrastructure

Serverless compute deployment, asset delivery optimization, and global edge cache integration.

03

Data Pipeline Strategy

Ingestion Sequence
IGDB API (Local TypeScript)
Normalization Layer
Remote Supabase Postgres DB
Next.js Engine
Media Handling & Timeouts

Zero local storage. Bypassing Vercel serverless limits (10-second execution timeouts) via offline local batch ingestion. All imagery, cover nodes, and screenshots are stored, resolved, and rendered purely via remote-hosted asset URLs, keeping the database slim and hosting costs minimal.

04

App Functionality & Route Architecture

/

Instant, client-side typo-tolerant search and core catalog mapping of all ingested titles.

/game/[slug]

Raw game profile views showcasing developer data, release status, cover nodes, and direct external purchase outlinks.

/upcoming

An uncluttered release calendar tracking emerging software and upcoming project timelines.

/random

Fast server-side redirect utility mapping users to discover random database entries instantly.

/wishlist & /collection

Private, authenticated tracking dashboards backed by Supabase Magic Link credentials.

05

Non-Goals & Financial Guardrails

Non-Goals

To protect the scope and preserve a zero-noise user experience, the website enforces absolute structural boundaries:

  • No reviews or comments
  • No social elements, likes, or upvotes
  • No algorithmic feeds or recommendations
  • No piracy indexation or link distribution
  • No hosting for game files
Financial Limitations

I am starting this out by keeping the infra focused on cost efficiency, ensuring the project survives with minimal costs and upfront, with plans for scaling later.

Database & hosting:$0.00 / mo
Media CDN:$0.00 / mo
Total Fixed Budget:$0.00 / mo

*There are plans for purchasing a domain for the website. Media rendering remains free via external image links and hosters. And yes I am technically broke :)