Flurry and AppWidgets

by Jake Colman » Thu, 08 Jul 2010 04:49:32 GMT


Sponsored Links
 I am familiar with using Flurry with Activities and calling
FlurryAgent.onStartSession() in the activity's onStart() method and
calling FlurryAgent.onEndSession in the activity's onStop() method.
What would be the best way to do the same thing if I want to use Flurry
with my appwidget?  Should I use the onEnabled()/onDisabled() methods or
should I use onUpdate() since the user may never delete my appwidget and
I won't know he's still using it?  Or maybe onUpdate() and onDisabled()
but then I won't be matching my start/end sessions.  If my appwidget has
a configuration activity or some other displayed activity I can
obviously use flurry there.  But how about in the appwidget itself?

-- 
Jake Colman -- Android Tinkerer

--



Flurry and AppWidgets

by whitemice » Fri, 16 Jul 2010 16:36:12 GMT


 Hi Jake
Assuming you are talking about Android Home Screen Widgets, I had the
same issue which I blogged here:
 http://blog.zedray.com/2010/05/01/tracking-a-android-home-screen-widget/ 

I still haven't gotten a response from Flurry, so I suggest you
consider the Google Analytics API.  While this offers fewer features
relevant for application developers, it does provide a dispatch()
method which allows you to manually workaround the widget life cycle
issue.  Let me know how this works for you.

Regards
Mark





--


Sponsored Links


Flurry and AppWidgets

by Jake Colman » Fri, 16 Jul 2010 20:46:30 GMT


 Mark,

Your blog postings hit the nail directly on the head!  I guess I'll do
as you suggest and see what Google Analytics can do for me.

Thanks.

...Jake



   w> Hi Jake

   w> Assuming you are talking about Android Home Screen Widgets, I had
   w> the same issue which I blogged here:
   w>  http://blog.zedray.com/2010/05/01/tracking-a-android-home-screen-widget/ 

   w> I still haven't gotten a response from Flurry, so I suggest you
   w> consider the Google Analytics API.  While this offers fewer
   w> features relevant for application developers, it does provide a
   w> dispatch() method which allows you to manually workaround the
   w> widget life cycle issue.  Let me know how this works for you.

   w> Regards
   w> Mark




   >> I am familiar with using Flurry with Activities and calling
   >> FlurryAgent.onStartSession() in the activity's onStart() method
   >> and calling FlurryAgent.onEndSession in the activity's onStop()
   >> method.  What would be the best way to do the same thing if I want
   >> to use Flurry with my appwidget? Should I use the
   >> onEnabled()/onDisabled() methods or should I use onUpdate() since
   >> the user may never delete my appwidget and I won't know he's still
   >> using it? Or maybe onUpdate() and onDisabled() but then I won't
   >> be matching my start/end sessions. If my appwidget has a
   >> configuration activity or some other displayed activity I can
   >> obviously use flurry there. But how about in the appwidget
   >> itself?
   >> 
   >> --
   >> Jake Colman -- Android Tinkerer

   w> -- 
   w>



Flurry and AppWidgets

by Jake Colman » Fri, 16 Jul 2010 20:50:15 GMT


 Mark,

So you call dispatch() from a service upon every call to onUpdate?

...Jake



   w> Hi Jake

   w> Assuming you are talking about Android Home Screen Widgets, I had
   w> the same issue which I blogged here:
   w>  http://blog.zedray.com/2010/05/01/tracking-a-android-home-screen-widget/ 

   w> I still haven't gotten a response from Flurry, so I suggest you
   w> consider the Google Analytics API.  While this offers fewer
   w> features relevant for application developers, it does provide a
   w> dispatch() method which allows you to manually workaround the
   w> widget life cycle issue.  Let me know how this works for you.

   w> Regards
   w> Mark


-- 
Jake Colman -- Android Tinkerer

--



Flurry and AppWidgets

by whitemice » Mon, 19 Jul 2010 17:05:41 GMT


 No, that would be crazy.
I have written a throttling algorithm that progressively reduces the
update frequency over time, since the last upgrade.

Regards
Mark





--



Other Threads

1. App behaves differently on device and emulator

My app binds to a service which loads a notification icon. When
leaving the app, the service stops if there are no background tasks
ongoing and removes the icon.

In the emulator, this works perfectly. On my Nexus 1 however, running
2.1-update1, the icon doesn't always disappear even though I set a
breakpoint on the line which removes the icon. The problem seems to
occur when I change orientation a few times. On my G1, running Android
1.6, there are no issues with removing the notification.

Any ideas what could cause this?

-- 

2. Activity receiving messages after onDestroy

I have an Activity with an inner Handler. The problem is that after
the activity is destroyed, the Handler is receiving messages for the
destroyed activity. This breaks things because the activity is in an
inconsistent state.

I'm thinking this might be a bug in Android - it should probably
delete all the messages in the queue when the activity is destroyed.
There doesn't appear to be any way I can manually delete all messages
in the queue (except by calling removeMessage(int what) with every
possible variation of what, which seems a bit ridiculous). The only
other solution I can think of is to create my own is_destroyed
instance variable and check it in handleMessage(), but again that
seems like a ridiculous hack.

Has anyone come across this problem before?

-- 

3. ask about x10

4. Not calling OnStop when an incoming call is received

5. Prevent scaling of :button on checkbox?

6. Not calling OnStop when an incoming call is received

7. Activity receiving messages after onDestroy