God's Promises started with an experiment. I wanted to explore how an existing multilingual Bible API could be used as the foundation for a small, focused web application.
Rather than building another general-purpose Bible reader, the idea was to create a simple experience around a specific purpose: helping people discover a Bible promise based on what they need in the moment.
What started as a technical experiment gradually became a complete web development project involving API integration, application architecture, multilingual content, interface design and real-world deployment.
Starting with a simple idea.
Sometimes you simply need the right word at the right moment.
God's Promises was built around that thought. Instead of asking users to search through large amounts of content, the application provides focused themes such as hope, peace, courage, strength, trust and comfort.
Users can choose a theme or receive a random Bible promise and experience the result through a calm and focused interface.
Experimenting with an API.
The technical starting point was the Holy Bible API, an existing open-source REST API providing multilingual Bible data.
The API provides access to Bible versions, books, verses, random verses and text searches across multiple languages.
This made it possible to work with real external data instead of maintaining a static collection of Bible verses directly inside the application.
Working with an external API also provided a practical opportunity to explore how applications consume external services, process their responses and transform that data into a focused user experience.
Open-source multilingual Bible REST API used as an external data source for God's Promises.
Building for multiple languages.
One of the most interesting parts of the project was working with multilingual content.
God's Promises currently supports nine languages: German, English, French, Spanish, Italian, Portuguese, Russian, Ukrainian and Romanian.
The selected language affects the interface and the Bible content retrieved by the application.
Supporting multiple languages required keeping the application structure flexible enough to work with different language responses without creating a separate application for each language.
From API experiment to application.
As the project developed, the experiment evolved into two connected applications: a web frontend and a dedicated backend API.
The web application is responsible for the user-facing experience, while the project's backend handles application logic and communication with the external Bible API.
This separation keeps the user interface, application logic and external data source independent from one another.
The basic architecture looks like this:
God's Promises
│
├── Web
│ └── ASP.NET Core Razor Pages
│
└── API
└── ASP.NET Core Web API
│
↓
Holy Bible API
External Data Source
Keeping the experience simple.
The technical architecture is only one part of the project. The interface was deliberately kept simple so that the content remains the focus.
Theme selection, language selection and random promises provide different ways to interact with the application without making the experience feel complicated.
The goal was not to build a large platform. It was to create a small digital space that does one thing clearly.
Technology behind the project.
What started as an experiment.
What began as a small experiment with an external API became a practical exercise in building a complete digital product.
The project brought together several areas of software development: consuming external APIs, designing application boundaries, handling multilingual content, building a user interface and deploying the application to a real web environment.
It also reinforced something I enjoy about software development: a small technical question can become a useful project when it is connected to a clear purpose.
God's Promises is a personal project by Turbo Turtle Systems — built as an experiment, a learning project and a small digital space for encouragement.
The application combines a custom web experience and backend architecture with an external open-source Bible API.
Rolling. Coding. Growing. 🐢