palmkin
← Back to Palmkin

More about Palmkin / Android actions

You decide what happens next

An assistant could help prepare a task without taking the final decision away from you. The examples here explain Palmkin’s approach to Android actions; they are a concept, not available functions.

How you stay in control

An example of what an action could look like. This website does not control your phone.

  1. 01

    You ask

    For example: prepare a timer for ten minutes.

  2. 02

    You review

    Palmkin shows the proposed action and its details.

  3. 03

    You confirm

    The action is not opened without your approval.

  4. 04

    Android opens

    Check and finish the timer in the clock app. Opened does not mean set.

Start with a clear request

“Prepare a ten-minute timer” is clearer than “remind me later”. A useful assistant should ask about missing details rather than guess a time, person or destination.

Check before confirming

Review the proposed action, the app it would open and the information it would receive. Declining should always be an option.

Finish in the right app

Opening a clock screen is not the same as starting a timer. Opening a calendar draft does not save an appointment. Check the result in the destination app.

Keep messages and calls personal

Check the recipient and every word before sending a message. A phone number should come from you or a contact you choose, never a guess about who “Mum” means. A message draft is not a sent message.

Choose access separately

Reading contacts or calendar entries needs separate consent and Android permission. Opening another app also brings that app’s own privacy and syncing rules into play.

No hidden continuation

The approach is to stop when handing you to another app, not silently continue a chain of tasks in the background. You should be able to see what happened and decide what comes next.