Adding subscription in existing 'location verification' API or adding a new API

[bigludo7]

Team, We need a decision about introduction of 'geo fencing' notification endpoint. We have 2 options:

1. Add this subscription endpoint in existing 'location verification' API
2. Create a whole new API for that.

From my perspective Functionally, checking location & notification management for geofencing are very close and share a lot of in common. From a business perspective, we'll probably have separate business case and model.

I tend to prefer option 1 to not multiply the API and we are in very similar context. Please provide feedback in order to get discussion/decision in next meeting.

cc: @ukkaps

[Dharmik-T-Mobile]

(Sharing my opinion as a product manager, so my perspective might be different from the tech SMEs.) Location Verification and Geo Fencing will have very different use cases and Legal implications. So, I'd recommend keeping them separate and create a new API for it.

[jgarciahospital]

(Also from product perspective) Since the use cases / services to implement can be so different, our option is also implementing different APIs.

[alpaycetin74]

Implementing different APIs would also help them to evolve independently.

[bigludo7]

Team decision from June 20th meeting: We opt to have 2 distinct APIs.