You can implement this interface in your own project and annotated it with an @DeepLink annotation. This will lead to calling handleDeepLink function in your handler with an arguments object of type T (that you will define in your project) containing the parsed arguments (path placeholder and query parameters). For deserialization simple data types are supported directlty but you can also add your own TypeConverters when you instantiate you DeepLinkDelegate class. There you can also provide error handler overrides for the standard type converters.

Note: This is referenced via reflection in DeepLinkProcessor as well as in the proguard-rules.pro file of this lib. If you make any changes here be sure to also update those two usages!

DeepLinkHandler with type java.lang.Object will call handleDeepLink with a generic java.lang.Object instance for the cae that you don't want any of the parameters parsed out of the URI or it does not have any.