Pingo

Built during an extreme-programming week at FH St. Pölten: Pingo, a location-based app that breaks the surroundings into “Geostops” — nature spots, cultural landmarks, small discoveries. For locals who want to see their home with fresh eyes, and for travellers looking for more than the tourist highlights.

Implementation

Frontend in Ionic + Vue, backend in NestJS, maps with Leaflet, Docker for local setup and deployment. My main responsibility was frontend architecture and the map-based features.

Challenges

The team knew Angular well but Vue barely at all. Reactive data binding in particular, and the integration of individual libraries, kept reminding us that frameworks may look related but ask for different mental models. An intense week where we learned the difference between Vue and Angular not in theory but while debugging.

Features

• Map-based discovery with location awareness.
• Geostops with ratings, photos, and short descriptions.
• User management with registration, login, profile.
• QR-code generation per Geostop.

Takeaways

Frameworks share vocabulary, not semantics. Reactivity in Vue and Angular feels similar on the surface and differs in the details — “knowing” one framework means something different than knowing the other. Also: cross-team work across backend stacks (NestJS, Spring Boot) is possible but takes discipline in defining API contracts.