We are in the process of designing the data structures that our Tikkun app will use to support the needs of a variety of users. Users may study by themselves without any need to interact with others, or they may study primarily by themselves and occasionally interact with others, or they may be tutors or students who continually interact with others as part of their studying and teaching. Each of these usage patterns will result in different demands for data in the app.

One particular issue that we have been discussing is how to support easy access to a user’s custom readings, each with its own notes and audio files, along with the straightforward retrieval of all notes and audio files that a user may have created over time for a particular range of verses or parts of a tefillah. For example, a user may have created two different custom readings for the Akedah section of Bereishit, one with audio files and notes for the regular weekly version and one with audio files and notes for the High Holiday version. The user will need to be able to find each of these custom readings easily. A title, created by the user for each custom reading, should work for that purpose. However, the user may also want to just look up the Akedah reading in the app’s library of texts, and quickly access all of the content that may have been created for those verses. We are trying out some ideas for data structures that will make this work efficiently.

Once we have an initial version of our data structures in place, we can start experimenting with different use cases and user interface ideas to refine our approach.