Tag: iOS

More on Audio

We are now able to create audio files on both the iOS and Android versions of our app, and are next working on saving and retrieving those files to and from Google Drive. Although both apps use Google Drive, the API’s for iOS and Android are quite different, and it is taking time to wade through the documentation and examples, try things out, and then go back and fix problems.

Meanwhile, we have also been doing a bit more thinking about the audio recording feature, and how it might work. We had the idea that recording each Torah or haftarah verse as a separate unit, and being able to play it back that way would be very useful. After looking at other audio recording and editing programs, we also will consider supporting the recording of each word or each phrase (marked by disjunctive trop) as separate units within a verse. A tutor may wish to record a verse phrase by phrase (or word by word) to allow students to hone their skills on specific trouble spots. A student, though, may want to record as a single unit a series of verses that have been assigned by a tutor. We need to think about how to flexibly to serve a range of needs.

{ Comments are closed }

Audio Files

Handling audio files is another critical technology that we need to master for our Tikkun app. Our app must support user creation of audio content, and subsequent storing and sharing of that content. The audio files must be compatible with both Android and iOS devices, which is best accomplished by using the AAC codec with an MPEG-4 container format. We have started by first adding an audio recording and playback feature to our apps. Next, we will be using our Google Drive file storage and sharing code to store and share audio recordings.

Once we have worked out all the details for handling audio files, we will be ready to: (1) design the user interface controls for creating, sharing and playing audio files, and (2) develop our own file format for the study materials that users will create, save and share. These two work areas are intertwined. When a user creates a recording of a Torah passage (or of any other content included in the app), we want to capture not just the recording, but also the Torah passage (or other content) that was the basis of the recording, as well as metadata such as the date/time of the recording, who created it, and perhaps other relevant information such as the date of the Shabbat or other occasion for which the reading is being prepared, or notes about specific parts of the reading that need special attention. The additional data stored with a recording will provide for a richer user experience. For example, a user who prepared a reading once before would be able to search for that reading and find the information about it when preparing again to do that reading at a future date. Or a tutor could organize a collection of study materials for easy sharing with students. We will need to think about how to flexibly add metadata to recordings, without excessively burdening users with data input.

{ Comments are closed }

Google Drive Integration

As I wrote a few weeks ago, we were working on integrating Google Drive into our Tikkun app. We had all of the key capabilities working for the Android version of the app, and were next diving into doing the same for iOS. Since we are relatively new to iOS and Swift programming, we are always on a learning curve as we start the next part of the project there. And, of course, the way that Android/Java accesses Google Drive differs significantly from the way that iOS/Swift does.

In particular, although calls to Google Drive occur asynchronously, they are handled in Android/Java in a way that basically results in things happening in order, without having to do any special programming. In iOS/Swift, the asynchronous nature of the interactions must be accounted for by the programmer. This led to learning how to use PromiseKit, a third-party Swift library for simplifying asynchronous code.

We are almost done now with bringing the iOS app’s functionality up to the same level as the we already had in the Android app. Next up: designing how user files should be represented in the app, and then how to arrange the user interface to simplify the sharing of files.

{ Comments are closed }

Deeper into Google Drive

This week I want to update you on our efforts in integrating Google Drive into our Tikkun app. As I wrote last month, we decided that Google Drive provided the best solution at present for giving iOS and Android users a way to share content with each other directly through our app. It will also give users a way to sync their own content and app preferences across multiple devices. In order to make sharing and syncing “just work” for our app, we needed to get a deep understanding of how Google Drive operates, and then how to program the desired functionality. So we have been doing a lot of reading and experimenting, learning how to securely log in and out of Google Drive, create, find or delete a particular folder or file, how to use our own custom file types, and so on. (For those with a technical background, we are using the Google Drive REST API.) We have been able to log in and out of Google Drive on both the iOS and Android versions of our app. We have so far only tested out the various file and folder operations on Android. We will soon move on to doing the same operations of iOS.

Another critical aspect of integrating Google Drive into our app is handling any error conditions that might occur. In particular, the app will need to respond reasonably if a file or folder that is requested is not available. This could be because the item was deleted, or because there is no network connection. Further, if a network connection is metered (i.e., it uses data on a data plan), the app should not make that connection without the explicit permission from the user.

Once we have the level of control that we need in both iOS and Android, we will start looking at how to present information about the user’s content on various sizes of screens. We also need to refine exactly what data we need to store for the user, and how best to organize it. User data management is at the core of what will make the app really useful, and it will, undoubtedly, take some time to get it right.

{ Comments are closed }

STaM fonts for our apps

Font development has always been a key part of our work. The accurate display of Biblical Hebrew on mobile devices has been one of the distinguishing features of the apps we have built. For many years, we used a proprietary technology for rendering fully-pointed Hebrew. The fonts were bitmaps and the layout engine was developed by us based on the ideas presented by Yannis Haralambous in his paper, “Typesetting the Holy Bible in Hebrew.” This technology worked well, but could not take advantage of improvements in font handling on mobile platforms. With those improvements — in particular, support for OpenType fonts — we developed our own OpenType font for Biblical Hebrew, tailored to the specifics of Android behavior. This font was modeled on our bitmap font and layout engine. Then, as we moved on to cross-platform development — adding iOS to our work — one of the first steps we took was to tweak our Hebrew OpenType font to also handle the specifics of iOS behavior.

Next, with the idea for an app that would show a two-column Tikkun-style layout of the Torah text, with the fully-pointed Hebrew on the right and the unpointed Hebrew on the left, we needed to have a font for the unpointed text that would be in the style appropriate for sifrei Torah, tefillin and mezuzot. This style is know as STaM (סת״ם). As I began working on creating a new font in this style, I learned that there are a number of different traditions for how to form the letters. The three most common traditions are the two Ashkenzai styles — Beis Yosef and Arizal — and the Sephardic tradition. This YouTube video was helpful to me in learning about the distinguishing features of each style. Once I knew about these distinctions, I realized that I should create three fonts, not one.

Of course, you may wonder why we did not just use any of the existing STaM fonts. As I mentioned earlier, we already had an OpenType font for Biblical Hebrew that provided excellent readability on Android and iOS. Now we wanted STaM fonts whose metrics would match. If both the Biblical Hebrew font and the STaM font have the same font metrics, then in a two-column presentation, at any font size, the words on each line take up the same amount of space, with the same line height. Having everything match ensures that the two columns of text look equally well-aligned and well-spaced.  Additionally, we wanted to be able to show the various special letter forms that are in a Torah. These include the large and small letters, the broken vav and the closed qof. By creating our own fonts, we can add any special forms that we want. So doing our own fonts was an easy choice to make, given the appearance standards we wanted to achieve. I am currently working on adding all of the special letter forms to our three StaM fonts.

Write to me directly at marsha@zigzagworld.com

{ Comments are closed }

File sharing & Google Drive

As I wrote last week, we are working on how to support users in sharing their study materials with one another, regardless of whether they have iOS or Android devices. I want to present some additional background about our goals and our approach. First, we want to enable the sharing of study materials entirely through the apps we are building, and in as simple a manner as possible. We do not want users to have to use their desktop or laptop computers as intermediary devices, or have to switch to email, another app, or a web page to share something. This means that the file sharing protocols must all be accessible programmatically from within our apps. We also want users to fully own and manage their study materials, without us keeping any copies of them or other related data on some server that we manage. Each user’s data should be entirely under their own control, so they can be comfortable that their data is not being used in any unknown ways or for any purposes other than what they want. Additionally, sharing can be useful to users by themselves. Users who own more than one mobile device — for example, an iPad and an Android phone — may want to use our apps on each device, and have all of their study materials synced between those different devices. And whenever users upgrade to new mobile devices, they need a straightforward way to transfer all of their study materials from the old device to the new one.

With these goals in mind, we settled on Google Drive as the most promising technology to use. Google Drive also stood out because of the continuing surge in the use of Chromebooks and related Google services by students in elementary and secondary schools, especially in the United States. This is important since we are looking to have our apps used by b’nai mitzvah students and their tutors. If students are already familiar with Google services like Google Drive, it will make using our apps that much more straightforward for them. A recent article in the New York Times noted that, “In 2016, Chromebooks accounted for 58 percent of mobile devices shipped to primary and secondary schools in the United States,” and that “more than half the nation’s primary- and secondary-school students — more than 30 million children — use Google education apps like Gmail and Docs.” Also, Google Drive is free for anyone to use, with generous data limits.

So we are now deep into the technical details of accessing the Google Drive functionality within our Android and iOS apps. This is actually more complicated in Android than in iOS, because in iOS, there is only one way to do things. In Android, there are multiple supporting technologies, and it requires some extra effort to determine which approach will give us the right services for our needs. And, of course, newer versions of Android work differently than older versions, so that also has to be taken into account. Further, on Android, a user is basically already signed in to Google, so we want to take advantage of that and streamline the process for the user. That means doing more behind the scenes programming to make everything “just happen.” And that’s where we are this week.

We are always happy to hear from you. Write to me directly at marsha@zigzagworld.com

{ Comments are closed }

Welcome to our blog

Thank you to everyone who has subscribed to our Hebrew in Hand Newsletter for so many years! I look forward to staying in touch with you about our work through this blog, which will be updated regularly. I plan to tweet whenever there is an update — find us @hebrewinhand. Visit us here anytime to find out what we are up to. As always, we want to hear from you. Please share your thoughts and questions directly with me at:


In case you have just found us, here is a quick summary of who we are and what we are doing. ZigZag, Inc. is a small software development company, and for many years we have been creating mobile apps of Judaic and Hebrew interest. As part of our work, we have created Android apps, web apps and fonts for accurately displaying Biblical Hebrew on mobile devices. We have recently added iOS apps to our development repertoire. Our most well-known apps are Tanach Bible and My Tanach, both for Android. They were done in partnership with Davka Corporation, and are sold through them.

Late last year, we began exploring the idea of creating a cross-platform Tikkun app — for both iOS and Android — for leiners (Torah readers) and b’nai mitzvah tutors and students. Our first task was to determine whether to use a cross-platform development environment, or to code each app natively. After studying the most promising cross-platform options, we decided to try using Nativescript to code the core of the app — the two-column display of Torah text, pointed text on the right and unpointed text on the left, with fully-justified lines,  predetermined line-breaks, and extra space at specific points within a line of text. This is a very demanding layout to handle. And we found that the cross-platform environment was just too limited for it to work. We then moved on to creating two separate apps, each coded natively. Both apps can display the two-column Tikkun text, plus handle a few user preferences. Here is the two-column text displayed on an iPad:

The next major technical area that we needed to work through was how to share study materials between users, no matter which platform each might be using. It clearly would not be enough for iOS users to only share with iOS users and Android users to only share with Android users. Again, we studied the various technologies for sharing data between users on different platforms, and settled on Google Drive as being the best candidate for our needs. We implemented a very limited proof-of-concept sharing feature in both the iOS and Android environments, and are now expanding that work to include the standard user interface features that users will expect. We now have the ability to securely sign in and out of Google drive accounts. We are next working on the internal mechanisms for sharing a specific file with a specific user directly through the app.

And that is where we are today.

{ Comments are closed }