136 reputation
5
bio website
location
age
visits member for 3 years, 8 months
seen Oct 23 at 21:16

Oct
23
awarded  Commentator
Oct
23
comment Do I need to use an interface when only one class will ever implement it?
@AvnerShahar-Kashtan conceptually I agree. I ask practically is it worthy to manage interface when the mocking FW create implicit one any way. Interfaces make it harder to navigate in code. Adds more files to the project structure and should be re-factored when the concrete changes its signatures.
Oct
23
comment Do I need to use an interface when only one class will ever implement it?
using an interface even for a single class will provide you with another mock implementation for unit tests, one that's not on production but mockito allow to create mock for a concrete class. So you shouldn't count it as a second implementation- thus no need for an interface?
Oct
23
comment Do I need to use an interface when only one class will ever implement it?
using an interface even for a single class will provide you with another mock implementation for unit tests, one that's not on production but mockito allow to create mock for a concrete class. So you shouldn't count it as a second implementation- thus no need for an interface?
Oct
18
comment when would you wrap a service object with an interface?
would I ever provide at least two different implementations for the service. you mean two production real implementations. right? Not counting the mock implementation
Oct
16
comment when would you write static method as it avoid a “seam” for testing
seam is a point where you can replace calling to a PROD obj with calling to a fake obj.
Oct
15
asked when would you wrap a service object with an interface?
Oct
15
asked when would you write static method as it avoid a “seam” for testing
Apr
12
asked how to separate the logic of different views when using android viewFlipper?
Mar
25
accepted is there a way to leave notificationManager and alarmManger alive even when the app is closed?
Mar
25
comment is there a way to leave notificationManager and alarmManger alive even when the app is closed?
thanks for your reply. what's missing in using regular manager in java class? can you please relate my 3 comments?
Mar
24
comment is there a way to leave notificationManager and alarmManger alive even when the app is closed?
always consider doing the actual logic in an IntentService - but then it means I'll have to re-start a service every time? nowadays my reciever calls a regular java class (manager). no service
Mar
24
comment is there a way to leave notificationManager and alarmManger alive even when the app is closed?
If you registered the BroadcastReciever in your app's Manifest, the code in the Receiver will be executed - but then I saw force closing is stopping the whole process and thus the receiver as well
Mar
24
comment is there a way to leave notificationManager and alarmManger alive even when the app is closed?
BraodcastReceivers only have about 5 seconds to perform their work! - why is that?
Mar
24
comment is there a way to leave notificationManager and alarmManger alive even when the app is closed?
what "closed" states an app can be in
Mar
24
asked is there a way to leave notificationManager and alarmManger alive even when the app is closed?
Feb
28
awarded  Tumbleweed
Feb
20
asked what should I save in local android DB to be more efficient and to last more than one session (and shouldn't be stored in the server only)?
Feb
10
awarded  Popular Question
Apr
22
awarded  Scholar