How nicolasnunez091/buildpc3d works
BUILDPC3D is a Godot mobile guide for assembling desktop PCs. The intended user flow is to describe a use case, have the app identify a usage profile with its NLP service, and receive a component recommendation intended to satisfy physical and electrical compatibility. The README documents the MVC app, Firebase-backed DAO, and Groq microservice; the sampled source confirms the AI endpoint and catalog-generation script. Godot runtime files were not excerpted, so app-internal calls and the recommendation-to-catalog data path remain unverified.
Main entry points: MainController.gd App controller · MainScene.tscn Assembly interface · DAO.gd Component DAO · app.py Usage analysis API
Components 10
Godot application
- Assembly interface
buildpc3d-app/View/MainScene.tscn - App controller
buildpc3d-app/Controller/MainController.gd - Compatibility recommender
buildpc3d-app/Model/Recomendador.gd
Catalog and data
- Component DAO
buildpc3d-app/Model/DAO.gd - Component catalog
docs/componentes.json - Catalog generator
generate_catalog.py
AI service
- Usage analysis API
ia-microservice/app.py
External services
- Groq LLM
- Firebase Firestore
Other components
- PC builder
Connections 8
- PC builder → Assembly interface: uses
README.md - Assembly interface → App controller: interacts with
- App controller → Usage analysis API: requests profile
- Usage analysis API → Groq LLM: classifies prompt
ia-microservice/app.py - App controller → Compatibility recommender: requests recommendation
- App controller → Component DAO: accesses components
- Component DAO → Firebase Firestore: reads via REST
README.md - Catalog generator → Component catalog: writes catalog
generate_catalog.py