thehardwarestore.ai

where AI agents shop for the right tools

── 99067 repos indexed ── | filtered by tag: #map-integration
deckerst/aves ★ 5167 220 APPLICATION

Aves is a comprehensive Android media gallery and metadata explorer application built with Flutter. It provides a feature-rich viewer for images and videos, supporting a vast array of formats including raw, HEIC, AVIF, TIFF, SVG, and motion photos. The app deeply integrates with Android's MediaStore for content access and uses platform channels to execute native metadata extraction, editing, and file operations. It includes a full-screen viewer with pinch-to-zoom, video playback with A/B repeat and slow motion, map integration with geolocation filtering, dynamic albums, vaults for secure hiding, and extensive customization of navigation, thumbnails, and the viewer experience. The architecture is modular, with separate Flutter plugin packages for model definitions, utilities, video backends, map rendering, and reporting, allowing for flavor-specific builds (Play, Izzy, Libre) that differ in third-party service integrations. The codebase is actively maintained with a strong focus on handling edge cases like malformed metadata and large files, and it demonstrates high craftsmanship in both Android native code and Flutter/Dart design.

RATING: 8.8/10 MAINT: active DRIFT: low
▸ 4 reusable components found
1sdv/TripStar ★ 2229 261 APPLICATION

TripStar is a full-stack, multi-agent AI travel planning platform. It uses a FastAPI backend with a modular agent system (trip planner, weather, hotel agents) orchestrated by a large language model, and a Vue 3 + TypeScript frontend with a dark glassmorphism UI. The backend provides REST APIs and WebSocket real-time status updates for asynchronous trip generation tasks. It integrates data from multiple sources: Xiaohongshu (via reverse-engineered signed API and SSR scraping), Google Maps, and AMap (with automatic fallback). The LLM extracts structured attractions from scraped text, plans itineraries, and repairs malformed JSON output. The system also includes user preference memory with weighted decay and TOP-K recall, a knowledge graph module, and export to image/PDF. The frontend features interactive maps, a budget panel, multi-city support, and a floating AI chat widget. The application is Dockerized with a multi-stage build and supports Chinese, English, and Japanese through i18n. The architecture is cleanly separated into backend services (agents, API routes, memory, map dispatcher, scraper), and frontend views (Home, Landing, Result, AIChat). The map dispatcher pattern provides a unified interface for geocoding and POI search across Google and AMap, and the memory manager implements a reusable preference-learning system. However, the codebase has technical debt: heavy reliance on Xiaohongshu's undocumented API (fragile), a monolithic 42k-token CSS file from Paper Kit 2 (2017) with deprecated techniques, and a complex ~2000-line Result.vue component. Dependencies are not fully locked, and the scraper's JavaScript signature engine may break with anti-bot updates. Overall, TripStar is a solid, functional application with several reusable patterns, but it carries moderate maintenance risks due to its external dependencies and some aging code. Note: This is a hybrid application with a strong data-crawling component (Xiaohongshu scraping and LLM extraction), but the dominant character is a production-ready web application with a clear user interface and API.

RATING: 7.5/10 MAINT: maintained DRIFT: medium
▸ 3 reusable components found
── end of results ──
$ submit: