Just say no. Developers should recognize when a tool no longer fits the problem space and move on. That does not invalidate the other usecases in any way. Not everyone is a developer, not every problem needs to scale.
Unfortunately, yes, this will become hell for some. Job security for others and ..
Having used Access a few times I find it hard to believe how anything could be worse than that anti-productive, database corrupting, File Already in Use piece of garbage. It's astounding that they're still updating it.
If it doesn't lock in data access like MS Access did, it could be seen as just an interface designer. Whatever data it gets fed, could be migrated from a simple database to a proper backend if such need arises. It could even coexist with other front-ends.
As long as it doesn't let too much business logic to be programed into it without a simple way to extract it, it shouldn't be a problem.
The problem isn't that Access locked in data, it was that people stuck with MS JET engine instead of hooking ODBC server properly - then Access became a funky, useful UI tool for databases.
The default datasource is a regular Google SQL server, so if you want to change something later on, just plug the DB credentials into your new thing. There's no lock-in.