-
### Use Case
The HealthKit component currently provides a good automated setup to collect HealthKit data that is defined in the `Configuration` of a Spezi application. Nevertheless, some Spezi appl…
-
### Problem
The Template Application should include more structured documentation that takes inspiration from the README but restructures and decomposes the setup into smaller elements.
### Solution…
-
### Problem
The current usage of the local storage module to store tasks and events is functional but not ideal. It provides limited functionality when querying for tasks and events and does allow …
-
### Problem
The Spezi module should support watchOS to enable developers to build a watchOS-based application.
The current UI elements in the Spezi module only support iOS. As we want to support t…
-
### Problem
Some of the Spezi-based applications contain a decent amount of dead code as students or inexperienced developers forget to remove functions, unused views, and leftover dependencies/impor…
-
- [x] Consent.sourceReference: 0..1 statt 1..1
- [x] Provenance.entity kann mehrfach vorkommen, um z.B. die multiplen Quellen eines Einwilligungstand-Consents zu referenzieren -> ist gegeben, da Prov…
lhitc updated
1 month ago
-
### Problem
Some applications require the usage of an innovation code to participate in an application. The invitation code must be verified and correlated with some additional information about th…
-
### Description
In the current template, one gets notified if the social support questionnaire is ready to be filled out again (daily basis on 8am). However, if you open the App by clicking on the no…
-
### Use Case
Some tasks are not repeating, and it should be possible to schedule these types of tasks independent of a start and end date as well as the need for a repetition definition.
### Pro…
-
### Description
When using `XCTRuntimePrecondition` the `precondition` methods are overridden and redirected to call `neverReturn()` which loops forever (see [here](https://github.com/StanfordBDHG/XC…