Dataans

Why dataans?

Dataans - Data answer. The data is answer to all your questions :)

Motivation

Have you noticed how convenient and easy it is to take notes in Telegram or any other messaging app? The idea was to create a note-taking app where notes are small markdown snippets grouped in spaces. Such notes are easy to create, read, remember, and edit. In addition, there are several other particularly important features:

Desktop app. Usually, the browser has dozens of opened tabs across multiple windows. It becomes hard to find the tab with notes (even when it's pinned).

FYI, the app window is also hard to find when you have a dozen other windows :raised_eyebrow:.

Yes, you are right. This is why the second most important feature is the drop-down mode (quake mode). You don't need to track the window location/position. You just open/hide it using the global configurable shortcut :sunglasses:.

Cross platform. This app supports Windows and Linux. It can be compiled on macOS too, but it wasn't tested on it. So, you can try to use it on macOS but you can face more bugs.

There are many similar existing apps but all of them have one or more major flaws. You can read more about motivation and features in the blog post: https://tbt.qkation.com/projects/dataans/.

App philosophy

Did you hear about the worse-is-better philosophy? If not I encourage you to read The Rise of Worse is Better article.

TL;DR. This is a citation from the mentioned article above:

The worse-is-better philosophy:

• Simplicity -- the design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface.
• Correctness -- the design must be correct in all observable aspects. It is slightly better to be simple than correct.
• Consistency -- the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency.
• Completeness -- the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. Consistency can be sacrificed to achieve completeness if simplicity is retained.

:thinking: What does it mean for the app? It means that the implementation is always straightforward, only common use cases are covered, only wanted and valuable features are implemented.

If you lack any functionality or you face a bug, then report it (issue or discussion). Any reasonable/valuable bugs/features will be fixed/implemented!

Installation

You can download the app installer here: https://github.com/TheBestTvarynka/Dataans/releases. Or alternatively you can build the app from source code: https://github.com/TheBestTvarynka/Dataans/tree/main/dataans#installation

Contributing

Feel free to contribute. Contributions are very welcome :blush:.

Read more in the CONTRIBUTING.md document.

Meta

Pavlo Myroniuk - the.best.tvarynka@gmail.com.

Distributed under the MIT license.