Kase is your personal data manager. It is simple, flexible, and it is relational. From a list of collectibles to an expert system or a knowledge base, you can build them with Kase.
Kase: Simple. Flexible. Relational.
Using Kase should be easy and intuitive.
Kase should allow you to design any database to track anything important to you.
Not just a flat file, Kase should support relational linking, so you don't need to repeat or duplicate data. Interlinked data is an order of magnitude more useful.
Additionally, Kase should be:
It should respect privacy, and you should not need to worry who can peek into your data.
Your data should always be available to you, and high-speed wireless network connection should not be a prerequisite for accessing your own data.
First, some basic concepts in Kase:
- Your Kase contains Boxes.
- Each Box stores Decks that can be related to each other.
- A Deck collects similarly structured Cards.
- And a Card is where you put data Entries.
One of Kase's tentpole features since its first release, Terminology can be changed from "Deck of Cards" to "Collection of Items", or "Table of Records".
Before you explore further, knowing these common controls will be helpful:
- If unsure, tap-and-hold on a button to see its context menu.
e.g. The Picker button's context menu.
- Pull down on the content to refresh.
Pulling down on the Box of Decks content shows the refresh control.
Kase is insipired by...
- AppleWorks Database (for Apple II)
- ease of use, simplicity
- Superbase (for Amiga)
- GUI-based VCR-like browse controls
- ThinkDB (later as SmartList) (for PalmOS)
- mobile-sized, quick selections, and flexibility
but not so much by...
Bento(for Mac and iOS)
- no real relationships
- not user friendly, expensive
Microsoft Access(for Windows)
- too many to list...
The year was 2014. It had been 7 years since the iPhone's debut. iOS 8 had just be announced. Yet we didn't have a decent personal database app. I got tired of waiting and started creating Kase. (At the time, it was called Dave.)