Feature request - panic pin [169172437]

Feature Request

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Sep 22, 2020 11:24PM

This is reopening of previously closed 121372590 which seems to attract public attention and was closed with rather strange "obsolete" wording.

Key idea: allow user, after giving explicit consent in settings dialogue to enter alternative pin/password for unlocking the device, that is intended to unconditionally wipe the data from the device. The reasoning behind is to keep user in control of his or her data even when being opposed by criminals or corrupt government officers.

This would require additional menu item in settings, legally-proven additional consent screen, screen to enter the panic password, and a backend engine that resets the device to factory settings.

It's understandable that this feature would require significant engineering effort and may not fit into the current priorities of the development team, so the key questions in this issue are:

1. Does this feature fits into google's vision of user's security model? (If not, why not?)
2. Is there any chance that this will be implemented by google?
3. Will you accept pull requests/patches if this will be implemented by community?

Comments

fe...@gmail.com <fe...@gmail.com> #2Sep 22, 2020 11:29PM

Could we get an official response to this feature request? Is there an idea to support SafeArgs in navigation-compose one day? Not asking for any time frames. Maybe there is no plans for statically generated args for navigation-compose at all.

vi...@google.com <vi...@google.com> Sep 23, 2020 05:10AM

Assigned to vi...@google.com.

al...@gmail.com <al...@gmail.com> #3Sep 23, 2020 01:30PM

Please check out my implementation of the same-

Part 1-

https://proandroiddev.com/safe-compose-arguments-an-improved-way-to-navigate-in-jetpack-compose-95c84722eec2

Part 2-

https://proandroiddev.com/safe-compose-arguments-an-improved-way-to-navigate-in-jetpack-compose-part-2-218a6ae7a027

Github repo-

https://github.com/dilrajsingh1997/safe-compose-args

pa...@gmail.com <pa...@gmail.com> #4Sep 23, 2020 01:36PM

Integration guide-

https://proandroiddev.com/safe-compose-arguments-an-improved-way-to-navigate-in-jetpack-compose-part-3-2e5ab79b9a05

ak...@gmail.com <ak...@gmail.com> #5Sep 23, 2020 02:04PM

vi...@google.com <vi...@google.com> #6Sep 23, 2020 02:39PM

Status: New

https://github.com/raamcosta/compose-destinations

this library make it super easy if can you support this on the native way

ra...@gmail.com <ra...@gmail.com> #7Sep 23, 2020 04:37PM

Here's a library that does just this: https://github.com/kiwicom/navigation-compose-typed. I tested it out and it works as expected

ld...@gmail.com <ld...@gmail.com> #8Sep 28, 2020 06:39AM

+1

something similar to 'compose-destinations' should be officially available to the devs. Its a pain to manage all the parameters manually.
Currently, I am working with a custom NavType implementation with Gson.

mi...@gmail.com <mi...@gmail.com> #9Nov 7, 2020 10:15AM

The current navigation is really difficult to use. It makes me unwilling to use composite in new projects and upgrade in outdated projects

sh...@google.com <sh...@google.com> #10Nov 14, 2020 06:49AM

Google team are there any news/priorities on this? Are you planning on improve the existing compose-navigation lib or this is going to not feasible😉?

lv...@gmail.com <lv...@gmail.com> #11Dec 21, 2020 09:57AM

There's some ongoing work on this here https://android-review.googlesource.com/c/platform/frameworks/support/+/2957296?s=09 as it seems

gc...@google.com <gc...@google.com> Aug 24, 2021 03:08PM

Accepted by gc...@google.com.

hi...@gmail.com <hi...@gmail.com> #12Jun 11, 2023 09:26PM

Re comment#11 - yes, you'll start to see commits for a Kotlin Serialization based approach to generating destination routes (and their associated navigate calls) from @Serializable classes.

There's a lot of parts to this, so please bear with us. We'll make sure to write a public blog post explaining much of the reasoning and other alternatives we looked into when we're ready to make a public release.

is...@google.com <is...@google.com> Nov 11, 2023 07:09AM