Why “my leopard gecko” isn’t a record
For many keepers, the journey starts with a single animal. At that stage, a formal record-keeping system might feel unnecessary because every detail about that specific individual is easily stored in memory. However, the reptile and amphibian hobby is characterized by a strong trend toward multi-animal households. As a collection grows to include several leopard geckos, ball pythons, or crested geckos, the limitations of “memory-based management” become apparent.
When a keeper has three different leopard geckos—perhaps an Albino, a Blizzard, and a Normal morph—referring to “the leopard gecko” in a diary or a mental note is no longer sufficient. Without a structured profile for each animal, it becomes increasingly difficult to distinguish which individual is due for a feeding, which one had an incomplete shed last month, or which one is showing a subtle but important change in weight. As developers, we approach this not as a hobbyist’s diary, but as a problem of information architecture. A care record is only as useful as the profile it is attached to; if the foundation is vague, the data built upon it will eventually become an unmanageable tangle.
The transition from a “diary” approach to a “system” approach begins by defining exactly who is being cared for. By establishing a dedicated profile with unique identifiers, the keeper ensures that every feeding log, weight measurement, and environmental check is tied to a specific biological entity. This structure is what allows a management tool to scale alongside a growing collection.
Core profile fields
From a management-design perspective, a useful animal profile consists of both identifying information and operational settings. The following table outlines the core fields used in a robust care-tracking system.
| Field | What it’s for |
|---|---|
| Name | The primary identifier for the animal within the system. |
| Species | Categorizes the animal (e.g., bearded dragon, ball python) for easier filtering and organization. |
| Morph | An optional field to record the specific genetic or visual variation, which is particularly useful in multi-animal households with multiple individuals of the same species. |
| Sex | Recorded as male, female, or unknown; essential for health monitoring and necessary for those utilizing breeding management features. |
| Birth date | Tracks the chronological age of the animal. |
| Acquired date | Records when the animal entered the keeper’s care, allowing for “time-in-collection” tracking. |
| Photo | Provides an immediate visual confirmation of the animal’s identity. |
| Notes | A free-text area for static information that does not change frequently, such as origin details or permanent physical traits. |
| Feeding interval | A numerical setting (in days) that defines the expected frequency of meals for that specific individual. |
These fields are designed to be the “anchor” for all subsequent logs. While fields like “Morph” or “Birth date” are optional in a database sense, they provide the necessary context for long-term history tracking.
Why feeding interval lives on the profile, not the feeding log
A common question in management design is why certain data points are treated as “profile settings” rather than “log entries”. The “feeding interval” is a prime example of this. While a feeding log records a single historical event (e.g., “fed one mouse on Tuesday”), the feeding interval is a standing property of the animal’s current care routine.
In our system design, the feeding interval serves as a functional engine for two critical features: dashboard status and reminders.
- Home-Screen Color-Coding: The dashboard uses the feeding interval to calculate “who needs attention”. By comparing the date of the last successful feeding with the interval set in the animal’s profile, the system can automatically highlight animals that are overdue for a meal. This provides an immediate, at-a-glance overview of the entire collection’s status without the keeper having to check every individual log manually.
- Feeding Reminders: The interval powers the local notification system. Because the interval is a property of the profile, the system can autonomously calculate the next due date and send a reminder at a pre-set time.
Importantly, this interval is distinct from any single record. If an animal refuses a meal, a “refusal flag” is marked in the feeding log, which ensures the system does not reset the “last fed” date incorrectly. By keeping the standard interval on the profile and the actual events in the log, the system maintains a clear distinction between the plan and the reality of care.
Photos and multiple animals at a glance
In a multi-animal management tool, visual identifiers are just as important as text-based ones. A profile photo serves more than an aesthetic purpose; it is a practical tool for rapid identification in a list view.
When a keeper is scrolling through a list of a dozen ball pythons, photos allow for much faster navigation than reading through a list of names or morph descriptions. To support this, the system’s logic is designed to show animals with a profile photo first in the home screen ordering. This “photo-first” prioritization is a small but intentional detail meant to streamline the daily workflow for keepers who manage large collections.
The home screen itself adapts based on the number of animals in the collection. For those with one to three animals, the system uses a “hero-style” dashboard that emphasizes individual status. As the collection grows beyond three, the view transitions to a two-column grid, maximizing information density while still relying on those profile photos to maintain clear distinctions between individuals.
How ScaleNote handles this
ScaleNote implements this exact structured approach to animal profiles. Every animal you register in the app includes the fields listed above—from name and species to the specific feeding interval that drives your custom notifications.
The app is built with a local-first philosophy, ensuring that your animal profiles and photos remain stored securely on your device rather than on a remote server. For those starting their collection, the free tier of ScaleNote allows you to manage up to three animals with full access to these profile fields, feeding statistics, and reminders.
For keepers who have surpassed the “multi-animal problem” and manage larger collections, ScaleNote Pro is available as a one-time purchase. Upgrading to Pro removes the animal limit entirely and unlocks advanced management tools, including growth charts, a color-coded calendar overview, and specialized modules for breeding and egg management. Regardless of your tier, ScaleNote provides free CSV and ZIP export/import features to ensure your data is always portable.
ScaleNote is available for download on the App Store: https://apps.apple.com/us/app/scalenote/id6762964531.
Summary
A robust care-tracking system begins with a detailed animal profile that includes unique identifiers like name, morph, and photo alongside operational settings like feeding intervals. By moving from generic labels to structured data, keepers can manage multiple animals with greater accuracy and less mental overhead. These profiles serve as the permanent foundation for all long-term health and history records within your collection.
For more on choosing the right framework for your records, see our guide on Reptile and Amphibian Care Records: A System, Not Just a Diary.
This article organizes information from a recording and organizing perspective. If you notice an error or outdated information, please contact us. Last verified: August 2026
