RUNSTR - Direction and Goals

Hey Freaks,

RUNSTR is a motion tracking app built on top of nostr. The project is built by TheWildHustle and TheNostrDev Team. The project has been tinkered with for about 3 months, but development has picked up and its goals and direction have become much clearer.

In a previous post I mentioned that RUNSTR was looking to become a Nike Run Club or Strava competitor, offering users an open source community and privacy focused alternative to the centralized silos that we've become used to.

I normally ramble incoherently.....even in writing, but this is my attempt to communicate the project's goals and direction as we move forward.

This is where the project is now:

Core Features#

• Run Tracker: Uses an algorithm which adjusts to your phone's location permissions and stores the data on your phone locally
• Stats: Stored locally on your phone with a basic profile screen so users can monitor calories burned during runs
• Nostr Feed: Made up of kind1 notes that contain #RUNSTR and other running related hashtags
• Music: Brought to you via a wavlake API, enabling your wavlake playlists and liked songs to be seen and played in the app

Current Roadmap#

• Bugs and small improvements: Fixing known issues within the client
• zap.store release: Launching a bug bounty program after release
• Clubs: Enabling running organizations to create territories for events, challenges, rewards and competition
• Testflight: Opening up the app to iOS users (currently Android only)
• Modes: Adding functionality to switch between Running, Walking, or Cycling modes

Future Roadmap#

• Requested Features: Implementing features requested by club managers to support virtual events and challenges
• Blossom: Giving power users the ability to upload their data to personal blossom servers
• NIP28: Making clubs interoperable with other group chat clients like 0xchat, Keychat, and Chachi Chat
• DVM's: Creating multiple feeds based on movement mode (e.g., Walking mode shows walkstr feed)
• NIP101e: Allowing users to create run records and store them on nostr relays
• Calories over relays: Using NIP89-like functionality for users to save calorie data on relays for use in other applications
• NIP60: Implementing automatic wallet creation for users to zap and get zapped within the app

In Conclusion#

I've just barely begun this thing and it'll be an up and down journey trying to push it into existence. I think RUNSTR has the potential to highlight the other things that nostr has going for it, demonstrating the protocol's interoperability, flexing its permissionless identity piece, and offering an experience that gives users a glimpse into what is possible when shipping into a new paradigm. Although we build into an environment that often offers no solutions, you'd have to be a crazy person not to try.

https://github.com/HealthNoteLabs/Runstr/releases/tag/feed-0.1.0-20250329-210157