SBTH app
Download the app!!
Most of the features people associate with apps have very little to do with what we are doing here.
When people think of an app, they are usually thinking of things like notifications, accounts, personalization, and constant updates. Apps send alerts, ask you to log in, track what you do, and try to keep you coming back. Many of them are built around transactions, data collection, or ongoing interaction. That’s not what this is. This site is designed to present information clearly and directly. There are no accounts, no tracking, no notifications, and no attempt to manage or retain users. You can come here when you choose to, spend time with it, and leave when you’re done. That’s intentional.
Some apps also offer things like offline access or deeper integration with a device, such as using the camera or GPS. Those features can be useful in the right context, but they add complexity and ongoing maintenance, and they don’t contribute anything meaningful to what we’re doing here. The same is true of feeds, recommendations, or personalized content. Those systems are designed to shape attention, not support understanding.
In practical terms, the site already does everything it needs to do. It loads quickly, it’s easy to navigate, and it works on any device. If you’d like, you can add it to your phone’s home screen and open it with a single tap, just like an app. The kinds of features apps add—accounts, notifications, tracking, and constant engagement—aren’t missing here. They’ve been intentionally left out.
Why We Don’t Use an App
Most apps are, at their core, just text and media presented through a user interface. Whether it is a stream of posts, a set of pages, or a form, the underlying work is the same: retrieving information and displaying it. For many kinds of content, that does not require a dedicated application. A website can do the same work directly, without requiring a large download, background processes, or permissions that have nothing to do with the task at hand. We have chosen to keep things simple. The site delivers the material without adding another layer between the content and the reader. There is no separate application, no installation, and no additional system to maintain.
In many cases, apps introduce subtle friction. Even when they function correctly, they can feel slightly out of place or less responsive than the system around them. Those small inconsistencies add up. The result is an experience that is more complex without being better. The work presented here does not benefit from that added complexity. It is primarily text, images, and careful organization. A fast, direct website serves that purpose more clearly and more reliably than an app would.
The Web as the Primary Experience
It has become common for websites to push visitors toward mobile apps. A page may be partially obscured, or access limited, with prompts encouraging a download before the content can be viewed fully. For many users, the easiest path is simply to install the app and continue.
Over time, this has led to a shift in how many services are designed. The website becomes a point of entry, while the app becomes the primary environment. Features available on the web are reduced or constrained, and the full experience is increasingly reserved for the app. This approach is effective, but it comes at a cost. The web version becomes less useful, and the open, flexible nature of the browser is replaced by a more controlled and limited interface.
We have taken a different approach. The website is not a gateway to something else. It is the primary and complete experience. Nothing is hidden behind an app, and nothing is withheld to encourage installation. The web remains a universal platform: accessible, linkable, and open to a wide range of tools and ways of reading. That is the environment we have chosen to work within.