If you use telegram it would be very helpful to continue this conversation here t.me/yondarme
The technical implementation of OSM in Yondar will greatly complicate the UX and codebase. A single relay subscription will turn into multiple API calls for OSM data. Creating places will no longer be instant and final, but an interminable waiting game where parties may lose interest and real ownership is not possible. I need to find a balance and find the right approach where OSM makes sense for Yondar and compliments the experience rather than hindering it or slowing it down. I don't want to sound like I don't love OSM, because it is really awesome and gets more awesome the more I look into it, but it is just looking like a big challenge to implement.
I've posited several possible implementation ideas for discussion in the Telegram group.
Thanks so much for your input, I appreciate you!