> For the complete documentation index, see [llms.txt](https://piny.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piny.gitbook.io/doc/07-roadmap.md). # Roadmap *Last updated: January 2026* ## Why Piny is live in an early state Piny is not a perfectly polished product yet – and that is **on purpose**. Right now you are using a version that still has rough edges, missing features, and obvious places where the experience can be smoother and more beautiful. We chose to open Piny at this stage because: * **Real stories beat test data.** We want real people to start pinning real memories on the map instead of waiting for a “perfect” launch built on assumptions. * **Product direction should be shaped with you.** Seeing how you actually use Piny – where you get stuck, what you love, what you ignore – is the fastest way to build the right product, not just the most polished one. * **Maps and communities grow over time.** A story map is never “done”. Releasing early lets the map and the community grow together while we keep improving the tools underneath. In short: we prefer a **real, evolving product** with you in the loop over a perfect demo that lives only in slides. Below is an overview of what we are focusing on next. *** ## Short to mid term ### Multilingual experience Piny should feel natural in your own language, not just English. * Add **multi-language support** across the app and documentation. * Prioritise translations for the main flows (explore, create, market, profile). * Make it easy to switch languages and remember your preference. ### A sleeker, more usable UI The current interface is functional, but it can be much more delightful. * Refresh the overall **visual design** to feel cleaner, more modern, and consistent. * Improve layouts on mobile and desktop for easier reading and interaction. * Reduce friction in key flows (create marker, join event, list on market) with clearer steps and better micro-copy. ### Richer user profiles Your wallet address is a start, but it’s not a full identity. * Let you add **human-friendly identifiers** (such as a username) on top of wallet addresses. * Make it easier to recognise creators and collectors across markers, events, and the market. * Prepare the ground for future social features (following, favourites, etc.) while keeping privacy in mind. ### A more powerful Market The Market already lets you list and buy markers, but it can do more for discovery and trading. * Improve **search and filtering** so you can quickly find the markers and creators you care about. * Add clearer **listing and offer information** to help you make better decisions. * Explore new market views (for example, by collection, by event, or by theme) on top of the map-first experience. * Explore ways to let you **make offers on markers even when they are not currently listed**, so you can signal interest to owners. * Experiment with **auction-style sales** and other advanced trading formats, while keeping the experience understandable for non-expert users. ### More EVM networks Piny is designed to be multi-chain. * Add support for more **EVM-compatible networks**, so you can mint and trade on the chains you prefer. * Make network selection clearer and safer, with better guidance on fees and performance. ### Creator analytics Creators should be able to see how their stories are performing. * Provide simple **analytics dashboards** for creators: views, pins, sales, and engagement over time. * Help event owners understand how people participate in their events across locations and networks. * Keep metrics easy to read and action-oriented, not just charts for the sake of charts. *** ## Longer term vision ### Google Maps integration Not everyone is familiar with open map layers, but almost everyone knows Google Maps. * Explore ways to **integrate Google Maps** for certain views or use cases, while keeping the core of Piny open and interoperable. * Make location selection and navigation feel instantly familiar for mainstream users. ### Beyond EVM chains The story of the world should not be limited to a single family of blockchains. * Add support for **non-EVM networks** where it makes sense, bringing Piny’s marker and event model to new ecosystems. * Keep the user experience as unified as possible, even when the underlying technology differs. ### Physical kiosks in real-world places We want Piny to live not just on screens, but in the physical world. * Experiment with **fixed kiosk devices** in places like museums or cultural spaces, where visitors can mint markers on-site. ### Piny token Over the long term, we see value in a native token that aligns incentives between creators, collectors, and the wider ecosystem. * Explore a **Piny token** that could be used for rewards, governance, or special experiences. * Design any token mechanics carefully, with sustainability and user value at the core, not speculation alone. ### Towards a Piny DAO In the very long run, we want Piny to be steered more and more by the people who use it and build on it. * Explore a **DAO-style governance model** where token holders and key contributors can help guide major product and ecosystem decisions. * Design governance so that active creators, collectors, and community members have a meaningful voice, not just pure capital. * Move towards this gradually, starting from simple feedback and voting mechanisms and only decentralising what makes sense over time. *** ## A living roadmap This roadmap is **not a binding promise** or a fixed release schedule. Priorities can change based on what we learn from you, from the market, and from the evolving Web3 and mapping ecosystems. Think of it as a **directional map**: it shows where we want to go, not every turn we will take. If you have ideas, needs, or feedback that you feel should be part of this journey, we’d love to hear them through the usual feedback and community channels.