Skip to content

cameloper/WasNeues

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

222 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

1. Vision

Origin Story

“I like trying out different cuisines and exploring their dishes. I’m at a local indian restaurant once in a while and I usually want to try something new but I have trouble remembering everything I’ve already tried there.

I’ve been thinking about how great it would be if there was an App where I could log my experiences, that wasn’t bound to single category like letterboxd or untapped and that wasn’t bloated with (competitive) social features but instead focused solely on my own tracking.”

Many apps exist for tracking specific categories of experiences:

  • movies (Letterboxd)
  • beer (Untappd)
  • books (Goodreads)

However, these apps are category-specific and often heavily social.

The goal of WasNeues is to provide a personal experience tracker that:

  • works across any category
  • focuses on personal memory and discovery
  • avoids social feeds, followers, and competition
  • keeps the interface simple and private

2. Overview

WasNeues is a personal discovery log that allows users to:

  • organize items into categories
  • record things they try
  • log experiences
  • rate and review them
  • remember where the experience happened

Examples of use cases:

Category Thing Experience
Drinks/Category Negroni Tried at Bar XYZ
Movies Interstellar Watched at Babylon
Books Profit over people Finished reading
Drinks Ayran Sütaş
Food/Indian Palak Paneer Tried at Royal Kitchen

The app is designed as a private knowledge base of experiences.

3. Goals

Primary Goals

  1. Help users remember things they tried
  2. Allow users to log experiences quickly
  3. Provide simple organization through categories
  4. Maintain a clean, distraction-free interface
  5. Enable personal reflection through ratings and reviews

Non-Goals (MVP)

The following are explicitly out of scope for MVP:

  • social features
  • public profiles
  • followers
  • global rankings
  • recommendations
  • ads

4. Target Users

Individuals who enjoy exploring:

  • food
  • drinks
  • movies
  • books
  • places
  • products
  • hobbies

etc.

They want to remember what they tried and track their impressions.

5. Core Concepts

The app is built around four main entities.

Category

A hierarchical organizational structure.

Examples:

  • Drinks
  • Movies
  • Books
  • Restaurants

Categories can contain:

  • subcategories
  • things

Thing

A specific item within a category.

Examples:

  • Karnıyarık
  • Negroni
  • Interstellar

A thing can have multiple experiences.

Experience

A record of interacting with a thing.

Each experience may include:

  • date
  • rating
  • review
  • associated provider

Provider

The place or service where an experience occurred.

Examples:

  • restaurant
  • cinema
  • bar
  • brewery
  • online service

Providers may include location information.

6. MVP Feature Set

6.1 Category Management

Users must be able to:

  • create categories
  • create subcategories with unlimited depth
  • edit categories
  • delete categories
  • assign themes/icons

6.2 Thing Management

Users must be able to:

  • add a thing to a category
  • edit a thing
  • delete a thing
  • view things inside a category

6.3 Experience Logging

Users must be able to:

  • add experiences for a thing
  • rate the experience
  • optionally write a review
  • record the provider
  • record the date

Rating

Star rating system (0,5 to 5 stars with 0,5 increments)

6.4 Provider Management

Users must be able to:

  • create providers
  • edit providers
  • view experiences at providers

6.5 Activity Timeline

The app must show a chronological list of experiences.

Users can:

  • open the experience
  • edit it
  • delete it

6.6 Category Browsing

Users must be able to navigate categories and subcategories.

Example hierarchy:

Drinks Cocktails Negroni
Martini
Beer Pilsner
Weizen

Users can:

  • drill down
  • view things
  • create new things

6.7 Onboarding

The app should introduce the concept of experience tracking.

During onboarding, the app will show example categories such as:

  • Drinks
  • Movies
  • Books
  • Restaurants
  • Places
  • Software

Users may:

  • select categories to import
  • skip entirely

No categories are preinstalled by default.

6.8 Data Import / Export

Users must be able to export and import their data.

Export

Export all data to a file.

Possible format:

JSON

Export must include:

  • categories
  • things
  • providers
  • experiences

Import

Users must be able to restore data from a previously exported file.

Requirements:

  • restore relationships
  • preserve IDs
  • validate data

6.9 Settings

Settings will be hosted in the native iOS Settings app.

Examples of settings:

  • appearance (dark/light/system)
  • iCloud Sync

The app will include a button to open its settings page.

6.10 Support / Donations

The app will include a “Buy me a coffee” option.

Implementation:

  • external donation page

7. Navigation Structure

Main navigation uses a tab bar.

Tabs:

  • Browse
  • Providers
  • Activity
  • More

Browse

  • categories
  • things

Providers

  • list of providers
  • provider details

Activity

  • chronological experience log

More

  • settings link
  • import/export
  • donation link

8. Non-Functional Requirements

8.1 Privacy

The app must prioritize user privacy.

Requirements:

  • no social features
  • no public profiles
  • no analytics requiring personal data
  • all data stored locally

8.2 Performance

Requirements:

  • smooth scrolling
  • quick creation of items
  • immediate UI updates

The app should handle:

  • hundreds of things
  • thousands of experiences

without noticeable slowdown.

8.3 Offline Capability

The app must work fully offline.

All core functionality must be available without internet access.

8.4 Reliability

Requirements:

  • prevent duplicate entries where appropriate
  • validate user input
  • prevent data corruption

8.5 Data Durability

User data must not be easily lost.

Mechanisms:

  • export functionality
  • safe local persistence

8.6 Usability

The interface must remain:

  • simple
  • fast
  • uncluttered

User actions should require minimal steps.

8.7 Accessibility

The app should support:

  • Dynamic Type
  • VoiceOver
  • standard iOS accessibility features

8.8 Platform Consistency

The app should follow Apple Human Interface Guidelines.

Requirements:

  • SwiftUI native UI
  • standard navigation patterns
  • system typography
  • native interactions

9. Future Features (Post-MVP)

The following features are planned but not part of MVP.

iCloud Sync

Allow users to synchronize their data across devices.

Requirements:

  • automatic sync
  • conflict resolution
  • optional toggle

Photos for Experiences

Users may attach photos to experiences.

Examples:

  • food
  • drinks
  • places

Map View

Visualize providers on a map.

Use cases:

  • see where experiences occurred
  • discover previously visited places

Statistics

Examples:

  • most tried things
  • top rated things
  • most visited providers
  • category insights

(maybe) Widgets

iOS widgets showing:

  • recent experiences
  • favorites
  • reminders to log new experiences

10. Summary

WasNeues is designed as a simple, private, and flexible experience tracker.

Its key differentiators are:

  • category-agnostic design
  • focus on personal memory
  • absence of social pressure
  • minimal and fast interface

The MVP focuses on delivering the core experience tracking workflow, while future versions may expand into synchronization, visualization, and deeper insights.

About

A personal discovery log to remember various types of experiences

Topics

Resources

Stars

Watchers

Forks

Contributors

Languages