added 16 characters in body

Source Link

edited Dec 11, 2017 at 5:56

Billal Begueradj

3.4k
10
25
34

InterfaceInterface

Retrofit ImplementationRetrofit Implementation

ServiceCalls.javaServiceCalls.java

MainFragment:MainFragment:

Bumped by Community user

occurred Dec 11, 2017 at 5:33

Bumped by Community user

occurred Nov 11, 2017 at 5:20

Bumped by Community user

occurred Oct 11, 2017 at 22:59

Bumped by Community user

occurred Sep 11, 2017 at 22:37

Bumped by Community user

occurred Aug 12, 2017 at 22:22

Bumped by Community user

occurred Jul 13, 2017 at 21:28

Tweeted twitter.com/StackCodeReview/status/874944239813230592

occurred Jun 14, 2017 at 10:58

Bumped by Community user

occurred Jun 13, 2017 at 19:43

Bumped by Community user

occurred May 14, 2017 at 19:40

edited tags

Link

edited Apr 14, 2017 at 17:30

200_success

144.2k
22
188
473

Bumped by Community user

occurred Apr 14, 2017 at 14:57

Bumped by Community user

occurred Mar 15, 2017 at 14:35

coding against interfaces is not a design pattern it is a principle, got the wording right

Source Link

edited Feb 13, 2017 at 14:13

oopexpert

3.1k
11
17

Interface design pattern to have multiple implementations of network call libraries (Retrofit or Volley)

I am learning design patterns from Head First Design Patterns and the first patterna principle I came across is to "code to interface". Now I want to use that patternapply this principle in my Android app, which includes lots of API calls. I am using Retrofit for network calls.

I have used that design patternapplied this principle considering some scenario something like this:

Have I correctly implementedapplied that design patternprinciple? If not, what changes do I need to make? In onCreate of MainFragment, I am hardcoding the implementation. How can the interface design pattern be better applied in this scenario?

Interface design pattern to have multiple implementations of network call libraries (Retrofit or Volley)

I am learning design patterns from Head First Design Patterns and the first pattern I came across is to "code to interface". Now I want to use that pattern in my Android app, which includes lots of API calls. I am using Retrofit for network calls.

I have used that design pattern considering some scenario something like this:

Have I correctly implemented that design pattern? If not, what changes do I need to make? In onCreate of MainFragment, I am hardcoding the implementation. How can the interface design pattern be better applied in this scenario?

Interface design to have multiple implementations of network call libraries (Retrofit or Volley)

I am learning design patterns from Head First Design Patterns and a principle I came across is to "code to interface". Now I want to apply this principle in my Android app, which includes lots of API calls. I am using Retrofit for network calls.

I have applied this principle considering some scenario something like this:

Have I correctly applied that principle? If not, what changes do I need to make? In onCreate of MainFragment, I am hardcoding the implementation. How can the interface design pattern be better applied in this scenario?