Design and Applications

Querki is, first and foremost, intended to be useful. As a programmer, it's always tempting to come up with features just because they are technically cool, but that misses the point: a feature is desireable if and only if real users really want to use it for real problems.

So this section is one of the most important -- the pages in here discuss what Querki is supposed to look like to the typical user.

• To start with, check out the Glossary of Concepts. That explains the jargon we're using in Querki, and how the pieces relate to each other.
• Then, you may want to skim the ever-growing list of Use Cases. We aren't going to add any features unless they are justified by a Use Case, and we're going to be picking Use Cases mostly on the basis of what seems genuinely useful.
• Closely related to the Use Cases are the list of Features. Each Use Case requires some Features, and each Feature should be used in a number of Use Cases if it's interesting enough to build.
• Querki is largely about recording data, but that's only useful if you can get at that data afterwards. So one of the most important parts is going to be Querki Explorer, the interactive query editor that lets you examine and report on your Space with no programming skill required.