Hi,
this is more a broad question about Azure App Services, so I hope I chose the right forum to ask this question, since there's no general forum.
I'm building an application that has mobile clients and a web Client (ASP.NET MVC). The apps use social authentication and push. Both could make the same api calls to the backend. From what I read Azure App Services should cover this scenario better than before (e.g. with API apps) but I can't find any advice on how to actually build this scenario, so how is this inteded to work?
Without Azure App Services you would create a Mobile Service and then try to build a web client that also calls the mobile service api. Correct? Now I like the capabilities of the API apps (Swagger, etc.) and it also seems like a good idea to separate the api from the "mobile stuff". But I didn't see things like authentication in API apps and it seems like I still need a Mobile Apps backend. So I've gained nothing but an extra backend (with some fancy features) and I've no idea how to implement authentication.
I only read stuff like "it's made for this scenario" and then the documentation states: if mobile app -> then this, if API with web Client -> then this. But how does this actually work if you have everything?
Can someone enlighten me please?