As proposed in bug 1181505, let's send a command named 'k' with the needed payload.

Gecko implementation should be able to reply whether enabling the kill switch mode was successfull or not.

Hi JR, Anything else do we need to kick off the development in server side?

Just need to get my manager to schedule time to support the patch. I'll also need to make sure that we have the correct UI element, localization and whatever other bits of support will be required to introduce what "killswitch" is presented to the user as. (e.g. "Lost mode", "remote secure", etc.)

Is there a detailed specification and list of requirements for the server changes you're asking for? After we have that, the next steps are: 1) JR does a bug breakdown for the work 2) JR gives me a ball park estimate of the time required

JR, There are flow charts here: https://docs.google.com/document/d/1-Ws_H5Nx8JxV1bCb2yOsOZo-fO6Ijgyt6YIHT5uvBRw/edit. Is this enough detail?

mtreese: No. While those highlight flow, they don't describe the sort of UX actions that I understand I'll need to replicate. Perhaps it makes more sense for me to clearly outline the questions and tasks as I understand them: For a logged in user with Find My Device active on their device, there is now a new "K" command that needs to be sent from the server to the device. * What is the trigger for this new "k" command? * How is this command different than the Lock or Erase commands? * Should other commands be disabled or removed in states where the "k" command is valid? * Does the "k" command display require internationalization? * Devices normally report back functions, should "k" be available on older devices? If I'm missing some context around 'k' that is explained in the flowcharts, I would greatly appreciate knowing it. Does that sufficiently help you understand my needs?

Jacqueline, is there someone from UX who can help answer JR's questions?

I have similar questions as JR. We need more explicit and detailed requirements around the FMD API changes needed to support this feature. Also, are there UX changes needed on the FMD Web dashboard (https://find.firefox.com/)? If so, where can I see the requested UX design changes?

redquired for 2.6