This wasn’t address on the above mentioned page… (or at least I didn’t see it).
It currently doesn’t affect me… but if I ever become an ex-Webflow customer
- I could see how something like this
could affect my clients or myself.
It’s clear (to me) that Webflow is not responsible for Google’s actions…
- (but may not be clear to someone else)…
So… perhaps @webflow wants to add / clarify / address
- the potential situation before it becomes a situation.
I’m guessing this dramatically affects
- all former Webflow customers, and
- current customers who don’t return often.
From what I understand… if you’ve already exported a website that had a Google Map on it…
come July 1st: the map will no longer function correctly
- Return to Webflow, enter your own Google Map API Key AND
- Re-export the site to your own server.
If you are a former Webflow client… you don’t have the ability to “fix the problem”
- without becoming a Webflow customer again (which means out-of-pocket-money)
What if you used Webflow to create a free website ? Is the new API Key still required ?
Here’s a Scenario:
After using the wonderful Webflow Designer to create an incredible website… the
- (Web Designer) moves on to their next project or
- (Small Business Owner) goes back to managing their business
…3, 6, 12 months later… they find out the map on their site is not working.
They contact the Web Designer, or return to Webflow - angry / upset / perturbed / etc.
Perhaps, Webflow should mass email all former and current clients ?
I personally think having a non-working map on your website - is not a good thing.
Again - personally… if I knew of upcoming issue…
- and If I had the ability to fix the problem at little or no cost…
----- that would leave a better taste in my mouth.
Just a suggestion. If I’m over-inflating this… then that’s fine. As a business owners… I just don’t like un-expected surprises.