You know, I don't. My apps aren't open source, and I came up with it
myself, not borrowed from a library.
But it's not rocket science, I'm sure you understand the pattern.
-- K
On Friday, February 20, 2015 at 4:39:32 AM UTC+3, Kristopher Micinski wrote:
I agree, that sounds like a useful
Agreed, thanks for the heads up!
Kris
On Fri, Feb 20, 2015 at 6:21 AM, Kostya Vasilyev kmans...@gmail.com wrote:
You know, I don't. My apps aren't open source, and I came up with it myself,
not borrowed from a library.
But it's not rocket science, I'm sure you understand the pattern.
-- K
Right, that's a good point I did not mention.
I'm interested in knowing what percentage of apps use a framework like
this rather than facilities purely within the vanilla Android
framework.
I can do some rough calculations in a while by grabbing a bunch of
apps and running some analysis on them,
I am trying to get an idea of what most developers use to interact
with web services.
The two main patterns I see in apps is to either create:
- Create an AsyncTask to make restful requests, and then do
something with `onPostExecute`, or to
- Create a service, and then have some API between
On Thu, Feb 19, 2015 at 2:03 PM, Kristopher Micinski krismicin...@gmail.com
wrote:
I was
wondering if there were any other patterns that app developers used
that I hadn't thought about,
Use a library like Volley or Retrofit.
A service turned inside out
A mediator class that manages a pool of threads, submits / cancels /
executes task objects, manages the wake lock (based on having tasks).
And a service whose only responsibility is to do startForeground /
stopForeground when it's told to.
All in the same process.
I agree, that sounds like a useful pattern. I *think* that's
relatively close to how Volley is implemented (though I haven't read
the implementation fully), too.
Do you have any pointers to open sourced code that would provide an
example of such a behavior? If not, no big deal: I can certainly
7 matches
Mail list logo
