sun · live day
rise set
elevation0.0°
local time00:00
locationdetecting…
night mix0%
scrub 24h
0006121824
mode
§ work · app · one day

UnLog

A focused daily logging webapp for tracking what matters — without the noise.

published 2026-06-08

About

This application started from a personal need to list ideas and prioritise them. When you need to generate additional income, one needs to know what to prioritise. However, prioritisation becomes complex when the subject is complex — and humans are complex.

UnLog provides a structured workflow to capture attributes, evaluate ideas against criteria, build a portfolio and plan milestones — all in one focused place.

Workflow

The workflow starts with an Attributes page where important characteristics or results are defined. Attributes are also grouped together. An example might be a group of Strengths and a group of Wins. The Strengths group might have Communication and Problem Solving as attributes. The Wins group may have "Developed part counting system" as a successful project you pioneered. The attributes capture what the subject has to offer and will next be used to prioritize ideas. Step 1: Create Attribute Groups under the Attributes → Attribute Groups submenu and then populate Attributes.

Before continuing it is necessary to mention that Attributes or any other entries does not have to be perfect before continuing to next steps further down the workflow. The application is built to adapt to any change made anywhere in the workflow.

Another useful feature is to add a Gemini API key in the Settings page and enable attribute and criteria rating population with Gemini. This way an LLM can check how well attributes and criteria relate (based on names and descriptions) and automatically fill the ratings for all the attributes and all the criteria for each idea. Ratings can be changed anytime but it can be very laborious to manually enter ratings.

With attributes defined, ideas can be populated. That is done on the ideas page. But before starting with ideas, criteria should also be defined for further weighing of ideas. Criteria is different from attributes in the sense that attributes weigh ideas based on qualities of the subject while criteria weigh it further based on external factors like demand, cost to manufacture or technical feasibility. Step 2: Add criteria under the Ideas → Criteria submenu and then add Ideas.

Ratings are necessary to weigh ideas and generate the priorities. A rating is required to indicate how well an attribute or criteria relate to an idea. A score of ten resembles the highest relation, and 0 the lowest. The idea priorities are then calculated and sorted from highest priority to the lowest. Step 3: Add and modify attribute and criteria ratings in the idea detail view or under the Ideas → Attribute/Criteria Ratings.

Portfolio items are next created and linked back to ideas. A portfolio item can be a product, project or service. Items are then linked back to one or more ideas to establish their priorities. Step 4: Create Portfolio Items in the Portfolio page.

Milestones are created, linking to Portfolio Items. Tasks are created, linking to a Milestone. Dependencies can be created between Milestones and Tasks. Step 5: Create Milestones and Tasks under the Milestones → Tasks submenu.

Privacy & Deployment

The typical information that gets entered into this app can be sensitive. The app was therefore designed to be used in multiple ways.

cloud

Online Managed

The cloud version of the app can be accessed online. It uses GitHub and Supabase for authentication and the back-end. Anyone can log in and use it. It is the easiest but least private since the database managers can see users' data.

self-hosted

Online Self Managed

Users can also fork the project on GitHub and set up Supabase only they have access to.

local

Local Self Managed

There is also a built-in server that can be run locally. It does need a Postgres database and does not have auth at the moment.

offline

Offline Front-End Only

The app can also be built in an offline version where it does not make any back-end calls but allows for storing state in browser local storage and exporting/importing of state in files.

§ Application · Leadership

UnLog

A focused daily logging webapp for tracking what matters — without the noise.

published 2026-06-08

About

This application started from a personal need to list ideas and prioritise them. When you need to generate additional income, one needs to know what to prioritise. However, prioritisation becomes complex when the subject is complex — and humans are complex.

UnLog provides a structured workflow to capture attributes, evaluate ideas against criteria, build a portfolio and plan milestones — all in one focused place.

Workflow

The workflow starts with an Attributes page where important characteristics or results are defined. Attributes are also grouped together. An example might be a group of Strengths and a group of Wins. The Strengths group might have Communication and Problem Solving as attributes. The Wins group may have "Developed part counting system" as a successful project you pioneered. The attributes capture what the subject has to offer and will next be used to prioritize ideas. Step 1: Create Attribute Groups under the Attributes → Attribute Groups submenu and then populate Attributes.

Before continuing it is necessary to mention that Attributes or any other entries does not have to be perfect before continuing to next steps further down the workflow. The application is built to adapt to any change made anywhere in the workflow.

Another useful feature is to add a Gemini API key in the Settings page and enable attribute and criteria rating population with Gemini. This way an LLM can check how well attributes and criteria relate (based on names and descriptions) and automatically fill the ratings for all the attributes and all the criteria for each idea. Ratings can be changed anytime but it can be very laborious to manually enter ratings.

With attributes defined, ideas can be populated. That is done on the ideas page. But before starting with ideas, criteria should also be defined for further weighing of ideas. Criteria is different from attributes in the sense that attributes weigh ideas based on qualities of the subject while criteria weigh it further based on external factors like demand, cost to manufacture or technical feasibility. Step 2: Add criteria under the Ideas → Criteria submenu and then add Ideas.

Ratings are necessary to weigh ideas and generate the priorities. A rating is required to indicate how well an attribute or criteria relate to an idea. A score of ten resembles the highest relation, and 0 the lowest. The idea priorities are then calculated and sorted from highest priority to the lowest. Step 3: Add and modify attribute and criteria ratings in the idea detail view or under the Ideas → Attribute/Criteria Ratings.

Portfolio items are next created and linked back to ideas. A portfolio item can be a product, project or service. Items are then linked back to one or more ideas to establish their priorities. Step 4: Create Portfolio Items in the Portfolio page.

Milestones are created, linking to Portfolio Items. Tasks are created, linking to a Milestone. Dependencies can be created between Milestones and Tasks. Step 5: Create Milestones and Tasks under the Milestones → Tasks submenu.

Privacy & Deployment

The typical information that gets entered into this app can be sensitive. The app was therefore designed to be used in multiple ways.

cloud

Online Managed

The cloud version of the app can be accessed online. It uses GitHub and Supabase for authentication and the back-end. Anyone can log in and use it. It is the easiest but least private since the database managers can see users' data.

self-hosted

Online Self Managed

Users can also fork the project on GitHub and set up Supabase only they have access to.

local

Local Self Managed

There is also a built-in server that can be run locally. It does need a Postgres database and does not have auth at the moment.

offline

Offline Front-End Only

The app can also be built in an offline version where it does not make any back-end calls but allows for storing state in browser local storage and exporting/importing of state in files.