Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Check lifetimeMonitor on all platforms - decide what to do! #161

Open
slodge opened this Issue Feb 16, 2013 · 2 comments

Comments

Projects
None yet
2 participants
Contributor

slodge commented Feb 16, 2013

lifetimeMonitor is important - but not really supported perfectly right now

And is perfect possible on all these targets?

@martijn00 martijn00 changed the title from VeeThree - check lifetimeMonitor on all platforms - decide what to do! to Check lifetimeMonitor on all platforms - decide what to do! Jan 24, 2015

@martijn00 martijn00 removed the VeeThree label Jan 24, 2015

Owner

martijn00 commented Jan 24, 2015

Not sure what this issue means. @slodge could you explain this one, or close it.

Contributor

slodge commented Jan 26, 2015

This is about the interface IMvxLifetime - https://github.com/MvvmCross/MvvmCross/blob/3.5/Cirrious/Cirrious.MvvmCross/Platform/IMvxLifetime.cs

This interface (or its replacement) could be really useful to developers wanting to track (cross-platform) whether an app is foreground/background/hibernating/reinflating/whatever...

To do this properly would require someone first really clearly understanding that whatever across all the platforms... is it even possible to unify the different lifetimes across Droid and Windows?

So I think it's linked to #143 - it would be lovely to have some good samples/guidance/code on:

  • handling tombstoning
  • consuming local and remote push notifications (in the different tombstoning states)
  • implementing background tasks (and long running tasks)

martijn00 added a commit to martijn00/MvvmCross that referenced this issue Dec 8, 2016

Merge pull request #161 from lothrop/master
Updated AndroidSupport to beta8.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment