Level 54
Is laravel alone enough? Yes, certainly.
Dingo might save you some work, but it's definitely not necessary.
Oct 15, 2016
8
Level 2
Which use to create APIs, built-in laravel 5.3 features or dingo ?
I'm really new in API developing but I developed many websites before using Laravel.(and PHP)
Now I want to create my first API that can respond to any kind of clients like Android , iOS or an Angular powered Application.
I've done a lot of research in this case that How can I make an API via laravel.
I found that there is a package named dingo/api that simplifies and provide requirements to create flexible APIs.
And in the other hand, in last version of Laravel (5.3) added new features that help to create APIs like Passport.
But I am confused and do not know which are best approach.
Whether the use of Laravel in this case alone is enough? or will I surely need Dingo?
Level 2
@willvincent,do you know that Dingo support laravel 5.3 or not? Is it do not conflict with each other?
Level 54
I have no idea, I've never used dingo.
Level 54
But, it looks like it should, yes.. https://github.com/dingo/api/blob/master/composer.json
Level 1
According to this https://github.com/dingo/api/issues/1159 dingo supports passport.
Level 1
This question is related to this discussion: https://laracasts.com/discuss/channels/laravel/internal-usage-of-passport-for-own-api
I am still not sure what advatages I will have if using dingo with passport and what approach should I take.
Level 1
This reply from https://github.com/dingo/api/issues/1189add some value to discussion:
I am not so sure this is true. It depends very much on your use case. Passport for example is very focused on having other people build applications for your API, which might not be what your use-case is.
Also I do not think Laravel comes with any kind of Transformers, does it?
Level 1
Another relevant question: https://laracasts.com/discuss/channels/laravel/creating-my-own-api-using-laravel-53-a-lot-of-questions
Please or to participate in this conversation.