Mapping is getting expensive. I'm running a site which depends on mapping too (https://doarama.com https://doarama.com). We are currently re-architecting some

Mapping is getting expensive. I'm running a site which depends on mapping too (https://doarama.com https://doarama.com). We are currently re-architecting some services and one of the key items in our newest version is creating an api where we can easily swap out map providers. You say it would take a lot to redo your code to swap service providers, but you don't have a choice. If you "want" to give up, then give up, that is a choice. If you're using this as an excuse, that's fine, but recognize that it is an excuse and not the real reason. I used to run HearWhere.com (now gone). I was in a somewhat similar position to you shortly before I shut it down (https://techcrunch.com/hearwhere https://techcrunch.com/hearwhere if you're curious). I would have had to do some major code changes due to outside circumstances, and I decided I didn't want to. Not that I couldn't. I just thought that the site had served it's purpose. I learned how to code, it got a bunch of interest, but in the long-term, I wasn't going to be the next songkick and didn't want to be. Mostly just because I didn't want to put in the effort in a very challenging industry. What I'm saying is there is nothing wrong with stopping if you'd like. But just be honest with yourself as to why you are not going forward. It isn't because Google changed their API pricing, it is because you don't want to put in the effort to change to another service provider that you could afford.