No idea how much control there is but finally looked at this on a mobile device and it’s practically impossible to use,feels similar to peering through a small slit in the fence.
1 Like
I can tinker with it
I had only viewed this on my desktop before and thought nothing of it (it all functioned as expected.) But viewing it on mobile and it’s even more unusable for me I think. The banner is locked in place so you can only view the website through that tiny sliver at the bottom.
2 Likes
Yeah sorry been doing this on desktop didn’t think to check mobile. I honestly am not great at mobile optimization and had to rebuild everything for the multi language functions which when I checked still aren’t perfect. I’ll fix the mobile view today
@mable I think the mobile view is better now. Let me know how yall feel about it.
I still need to normalize the original data which is tedious so it’ll be a bit but I think I’m happy with the UI/UX and the form now.
I may add other skill toy/hobbies like kendama at some point and I want to add a calendar and correlate events on the map but that’s a future state . I think it would be cool to check the map and see contests and such but I don’t have the drive for that yet.
If anyone has any other issues, or ideas throw them at me I’m happy to mess with it more.
My end goal for the yoyo map is to one day make a non profit that helps coordinate non Nyyl yoyo events around the US but that’s way out in the future state of my plans I might get to organizing a club coalition in the midatlantic
My goal isn’t to replace anything out there but to fill gaps where I see them
Like eventually setting up club merch stuff but that’s a pain to setup too
3 Likes
Indeed!! I still don’t see my marker. Should I try again? I certainly won’t discount the possibility that I didn’t do it right. 
1 Like
The burger nav bar was easy cause I could just replicate what I did on the club site but I had commited a data normalization code change prior that broke so I had to fix that which was a pain in the but to the point I had copilot help and it went in circles until I reversed some of the normalization changes for now and will just deal with that later. For now we got fun quirks like multiple ways California entries in the filter list. Sadly I had a better view on that in my previous build but I trashed it when I reverted. Ohh well eventually you’ll be able to see all folks in a region and be able to filter by state and such but that’s a fix when I get the original data normalized on the db
1 Like
I think you didn’t verify the email
Workflow is sign up, verify by email then profit unless your under 18 then your parents email has to verify too.
Hopefully it didn’t go to spam.
If you go to my profile enter your email it “should “ re send the verify email
1 Like
This is likely.
2 Likes
I should add a toast message to check your email after you enter your details
Or make the flow more apparent
Maybe later tonight after dinner
1 Like
trying to add but encounter error " Expected number, received null"
2 Likes
I found it and verified. 
2 Likes
Found it bad UX on my end when you entered a new city it would take a minute for the backend to catch up and no error handling to let you know why it failed
I changed it to an api call so it’s instant and added error handling so it shows why it failed before it submits not just a generic it broke message after you submit.
Should work now. I need to add cities from Genames to pre populate that but meh tomorrow ne can do that
Also found an issue with socials not actually being added just dropping woops…
also drop pin is wrong. it’s in the ocean 
How do I fix the location?
1 Like
I would move… the middle of the ocean is not a hospitable living place for humans…
3 Likes
Ohh I found the reason everyone’s distance is so off. I built in the 10 mile jitter into the Postgres side (cause I know how to build sql queries and logic way more than typescript and next.js and at some point when Claude was helpfully integrating the map (the part I didn’t know how to do and used AI to do) it added the jitter component to the next.js side too so it was adding 20+ miles in jitter in some cases basically the front end would offset the dot and the database would run some logic to send it in a different direction offset too. I wanted the offset on the db side so if there was a data breach or something I don’t have exact coordinates anyway but Claude was so kind to help me build in extra on the front end.
So yeah that’s fun.
And I realize I only have cities. The 10 mile jitter is more security theater than anything to help make the data entered particularly not all that useful to data brokers and such but still helpful enough to link communities.
Ohh well that’s a weekend task at this point
2 Likes
Ha. I just realized my dot was way off 