Since you are talking about prioritizing I would like to add a comment. Ask the question, “what is the goal of CityStrides?”, and you will quickly come up with the top items on the priority list. Supermitch mentioned adding new cities to bring in new users and revenue. I think another is finding a way to import just streets with the new cities. Although many of the added features are nice, they don’t mean much until the core product is functioning as intended. Things like leaderboards, percentage of city complete, etc are meaningless unless we have an accurate list of targets to achieve (Streets). Currently, I have 12 cities/towns completed and they show a range of completion from 61% to 97%. I generally come up with a list of streets and add any new streets (new developments) to that list and cross reference against googlemaps and/or satellite view. My thinking was, that as CityStrides was updated, my list of towns would just automatically update and become more accurate over time. There are too many towns in the world to expect James to update each town manually as we go along and there is too many junk targets (businesses, parks, etc) for me to flag. I know, James, you mentioned in the beginning, that it was easier to import all targets/objects when importing a city. Have you given any thought to how you could narrow that down to just streets and add other things if people request it? I think it would be better to have too little targets and have Citystrides meet 98% of your objective and add the few missing items/targets/objects, then to import everything and try to weed out all the bad stuff.