So it's more like a one-time thing, when somebody wins the challenge, the challenge is done. Also if people likes it I plan to make it multi platform, such that you can challenge others even if you don't have your running data on the same platform (strava,garmin etc.)
Requirements: Testers will need to be runners (at least some times) and have a Strava account.
Project Description: Challenge friends/family/colleagues for who will run X kilometers first. Integrates with Strava to track the progress and keep the leaderboard for the challenge up-to-date.
I launched https://thecitymapquiz.com some time ago and I really don't have any succeed critia for it. It was fun to built, playing around with rendering open street map data, and building the web part with phoenix liveview. I really don't have any plans to it going forward, and with a couple of small kids and a full-time job, I'll probably not have any time to spent on it if I actually had a plan. So in someway you could say it's already a success whether or not anyone will use it.
Another approach is to unsubscribe from everything (friends, groups etc.). You feed is empty, but you can still visit profiles/groups etc. but nothing will be pushed to you.
Thank you. I think 23 is pretty good - I have looked a lot on these maps during development and I only managed 24 after I deployed the site yesterday. I'm not really satisfied with the site yet, but I through it was time to find out if any other than me found it interesting - now there is at least one other than me :)
Sounds good. But I probably should implement something to store the state between websocket connections anyways. Loosing all progress when a connection drops is probably not optimal :-)
I deployed a little side-project (https://thecitymapquiz.com) to fly.io yesterday. The deployment went really smooth, but friends testing it out complained their connection (websockets in Phoenix LiveView) dropped. It might be because its running on the cheapest VMs, I don't know yet.
That said, it was really satisfying seeing the application running in Seattle, Hong Kong, and Amsterdam within minutes after launch.
Great idea, and I really like the design of the site. One thing that could be improved is the navigation between policies. The 'down arrow' confused me since I expected the policy would open directly below the headline, and the page navigate to "Available policies" instead of the start of the actual policy.
I just deployed a side-project to fly.io. I cannot really say anything about the multi-region capabilities since it is single-region so far, but I must say the domain setup and certificates is really smooths