Using FF4J from java as a pure API client

[arbe]

Describe the bug
I guess this is more a question than a bug probably, I just can't find the answer in the documentation nor in any example.
We have a setup with ff4j in which we have a centralized deployment to manage all the feature configuration, using the web interface to configure our features, and then a client configured with that ff4j instance (using FeatureStoreHttp and PropertyStoreHttp).

It's all kind of ok, until we want to go one step further an implement our custom Strategies. The expectation was that we could just create a new strategy in the FF4J server, have it deployed there, and the client wouldn't even need to know about it, but that's not like this, and the client needs to know about that specific custom strategy class, otherwise it fails as it can't instantiate it.

Isn't there an out of the box way to have the client just use a rest api, without having to actually be so tied to the ff4j server details?

To Reproduce
Steps to reproduce the behavior:

1. Have a ff4j server and client setup
2. Implement a custom strategy in the server, and configure a feature using it
3. Have the client doing an ff4j.check on that feature.
4. See error in the client, as it can't instantiate the strategy

Expected behavior
The ff4j is a pure client asking for the "check" on the server, and not having to execute all the toggle logic