From e7c5b94c7d90131e4a22047fc359c2600fa2904d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dirk=20Ja=CC=88ckel?= <dirk@mautinoa.com>
Date: Tue, 18 Jun 2019 15:09:07 +0200
Subject: [PATCH] Adding a proposal for notifications

---
 en/logbook/notifications.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 en/logbook/notifications.md

diff --git a/en/logbook/notifications.md b/en/logbook/notifications.md
new file mode 100644
index 0000000..87f6892
--- /dev/null
+++ b/en/logbook/notifications.md
@@ -0,0 +1,24 @@
+---
+title: Notifications
+---
+
+
+# Overview:
+
+Android notifications can be intercepted and sent to the card10 to be displayed there
+
+# Firmware support:
+- The badge can receive notifications via BLE and display them
+- It is possible to trigger the  vibration motor with a notification
+- It is possible to define on the Android side how the motor vibrates
+- It is possible to only show the notification if the user presses one of the buttons 
+- Notifications can contain small images (avatar/app icons) to be displayed
+- If the text of the notification does not fit on the screen, the buttons on the badge can be used to scroll down (and up)
+- User feedback to these notifications is possible via buttons
+— For example: If the notification is a call notification: The user can reject or take that call
+— In general: pressing a button opens the application on the users phone
+
+# Data Format:
+- Protobufs are used  to encode these notifications to the badge
+
+
-- 
GitLab