Roadmap

@jacobreal list public extra-exports jacobcole-net systematicawesome Updated 2026-04-10

Roadmap

#connectordoc #ideaflowpan        systematicawesome.jacobcole.net > roadmap.jacobcole.net
started by [email protected]
Ideaflow Roadmap
See also: Current •  Path to Product-Market Fit (formerly: Path to Series A) V1.4 (May 18 2020) • businessroadmap.jacobcole.net • Productfeedback.jacobcole.net • ideaflowproject.jacobcole.net •User Profiles and Feedback Doc

2022-09-30 Current Roadmap (Sprint Planning)

#goal 100 active users whose value from ideaflow is quick capture + 10 power users.

Sprint Planning Outline From Jacob

Key insight: Just having the basic ThoughtStream and search that works stably and quickly and offline is a huge value prop and awesome!

Q4 2022
- Offline (polish) #category
- Fast Load Time

- [[linear 1] linear 2] Sync doesn’t always happen automatically when i open my laptop after having used my ipad. Needs refresh

-
- Polish - we could get away with ditching any one of these, but I think we need at least some for the sake of polish:

Goal: 10 power users + 100 auxiliary active users

Late Q[n]4 2022
- Explore Audio Capture
- See if iOS native app necessary for speed
- Unlinked references

—-

Tags:, legend, ??, means, J, thinks, it’s, fixed, but, hasn’t, checked
—-

Top priorities for sprint planning from teammates besides Jacob:

Taylor: from #day-to-day pinned note Table stakes

-

Thoughts on Tradeoffs for Sprint Planning

Jacob: i’m ok ditching folder polish for MVP launch. I think we could get people on the app without folders at all if needed. Of course want to fix soon

——

2022-08-05 Roadmap

Q3 2022
- Offline (polish)
- Fast Load Time
- Condensed View
- Reverse relations

  • Bug fixes
  • UX tweaks

Goal: 10 power users + 100 auxiliary active users

Q4 2022
- Explore Audio Capture
- See if iOS native app necessary for speed

——
Hackathon ideas:
Taylor goal /ankify or related; a la https://davidbieber.com/tags/spaced-repetition/ – taylor attached to anki

Medium term priorities:
Taylor Jacob Medium Term Priorities #Conversation Aug 5 2022

Bat-Jacob 2022-04-29 Features

Most Important

Offline – offline shipped best guess — next week

Condensed
Reverse relations inline

? leave-on audio notes like otter.ai

Ability to copy paste in text

Bug fixes – eg expand relation after filter

Back button accurate position

Important

Bug fixes “Jump to” working in timeline
scroll position history — back button — @ and ~ — fix bug
share sheet - way to copy all notes on same screen
keeping newline divisoins in refs
audio notes - bat thinks won’t matter till way later
thinking users absolutely need suggestions like entanglement
ability to include hash in refs
Auto url title extraction

Kinda Important

? 1+ references notes colored differently
bug fixes
ios siri thoughtstream xyz
way to take photo
~ and @ shorthand for notetaking
autocomplete in search bar
popup for quick capture - not fundamental

—

—

—

#v1.1

  • Reference

All items are tentative in order/timeline. Items followed by a ? indicates very tentative order.
- Development Phases

  • Ideaflow Phase 1: the (single-user) Thoughtstream Web Interface

  • Ideaflow Phase 1.5: Entanglement-Style Bullet view (attempt 2)

  • Ideaflow Phase 1.6a?:  Auto Tagging/Extraction Tools

  • Ideaflow Phase 1.6b?:  Augment Chrome Extension

  • Ideaflow Phase 2: Collaborative Thoughtstreams – hopes to be as low friction as texting someone!

  • Ideaflow Phase 2.1?: List and Suggestion Box View

  • Ideaflow Phase 2.2?: Graph/Mind Map View

  • Ideaflow Phase 3: Rich(ish) Collaborative Documents – replace docs like chronicpain.jacobcole.net

  • Future Plans?

  • Command line for the web / third-party output extensions / integration with big co CRMs

  • Social network centered around sharing ideas
  • Web crawling + manual effort to create a structured, queryable version of all the Web
  • “The Annealing Machine”

  • Ideaflow as primary filesystem

  • Everything gets a URL

Intro

  • Ideaflow is a large vision that will contain many distinct but ultimately interconnected products

  • What we are building right now, ideaflow.app,  I'm calling Ideaflow Phase 1, or the (single) Thoughtstream Web Interface

  • It's built for one purpose: to become your go-to scratchpad to capture ideas, quotes, or resources you come across while moving fast, and that you don’t want to lose

  • In MVP form, it only needs to be flat (no hierarchy), though may contain purely visual tab indents in notes

  • It's like a “command line for your thoughts”

  • Design Principle: it's trying to be like a text file, but just a tiny bit better #designPrinciple

  • I also see it as a component part of the interface of future product phases I hope we build

  • e.g. It could become an always-available drop-down at top right of an Entanglement-style bullet view

  • Later phases will be discussed below

Background on Types of Notetaking

  • Notetaking is a broad term and refers to a lot of different workflows, including the below.

    1. Taking notes during a lecture in class. Requires features including the following: Outlining, Drawing – e.g. OneNote/Evernote target this

  • 1a. Taking notes while reading a complex philosophy book. Requires Outlining, and ideally Relations – e.g. Roam targets this

  • 1b. General shared company meeting notes. Requires Collaboration, Outlining, and at least some way to fudge todos in. Google Docs, Notion target this.

    1. Keeping a todo list – apps for this range from heavy (Omnifocus), to light (Workflowy, iOS Notes). Ideaflow Phase 1 may support checkboxes etc. incidentally but it’s not the target use case persay.
    1. Personally quickly jotting down ideas, insights, resources, articles you don’t want to forget; keeping reference lists (e.g. of ideas, quotes, restaurants, epiphanies, insights, articles or comments from various newsfeeds); also queueing up suggestions you want to give to various companies, organizations; things you want to say to various people next time you see them – Ideaflow Phase 1 targets this. Alternatives include iOS notes, Simplenote, Roam (esp. see Daily Notes feature), Slacking yourself, keeping a giant text file, TheBrain.com

  • 3a. Very casual shared notes from calls/discussions

  • 1:1 calls. Existing workflows: texting each other links, FB messages

  • Team Zoom calls. Existing workflows: Initially, Zoom chat, then copy paste to Slack
  • Zoom or Clubhouse group discussions/salons; Zoom classes as well. Existing workflows: LinkedIn/FB/Telegram group chat

  • Ideaflow Phase 2 hopes to be as low friction for this as texting someone!

  • 3b. Slightly more formal notes for interesting group conversations, idea brainstorming sessions at work, etc.  Note that this may be distinct from 1b. “General company meeting notes”.

  • Zoom or Clubhouse group discussions/salons: Setting up a Google doc with notes like http://salon.jacobcole.net/ or http://systematicawesome.jacobcole.net/ . Roam is planning to becoming a tool for this as well.

  • Ideaflow Phase 2 ideally hopes to be a tool for this as well, but slightly less important than the 3a. use case. This might wait for Ideaflow Phase 3: Rich(ish) Collaborative Documents

  • 4. Keeping “dossiers” on people (see also https://en.wikipedia.org/wiki/Farley_file ). Tools that Target this:  getdex.com CRM, Affinity CRM, Roam (sorta), and Ideaflow Phase 1.5 (Bullet view, will discuss later) will target this.

  • 5. Creating high quality reference sources on various topics, like http://chronicpain.jacobcole.net/ . Requires precisely the same features as “1b. General shared company meeting notes. Requires Collaboration, Outlining, and at least some way to fudge todos in. Google Docs, Notion target this.” Ideaflow Phase 3: Rich(ish) Collaborative Documents explicitly addresses this

Timeline

Jan 31
- Ideaflow Phase 1 “Thoughtstream Web”

  • Use case: Targets Notetaking Use Case 3

  • “3. Quickly jotting down ideas, resources, articles you don’t want to forget; keeping reference lists (e.g. of ideas, quotes, restaurants, epiphanies, insights, articles or comments from various newsfeeds);also queueing up suggestions you want to give to various companies, organizations; things you want to say to various people next time you see them  – Ideaflow Phase 1 targets this. Alternatives include iOS notes, Simplenote, Roam (esp. see Daily Notes feature), keeping a giant text file, TheBrain.com”

  • “It's built for one purpose: to become your go-to scratchpad to capture ideas, quotes, or resources you come across while moving fast, and that you don’t want to lose”

  • Workflow: Generally, I expect it to be used as an always-open desktop application (separated from Chrome via the Tools >  create shortcut >  “open as window” feature for easy command-tab access)  or iOS home screen native application

  • Product Notes

  • “In MVP form, it only needs to be flat (no hierarchy), though may contain purely visual tab indents in notes”

  • It's like a “command line for your thoughts”

  • Design Principle: it's trying to be like a text file, but just a tiny bit better #designPrinciple

  • Estimated additional features needed to complete this phase

  • [ ] Some minimal onboarding docs, initial text on screen, or tutorial

  • [ ] Sundry bug fixes – mostly captured by P1 in Linear, and some of the new ones recently mentioned in #jacob-raw-thoughts

  • Target Users

  • Super on-the-go notetakers like David Bieber, Alex List, Jacob

  • Hypothesis

  • [There exist at least a few (3?) people[p]](#cmnt16)[q] that really need better a tool for Use Case 3.

  • Complaints about existing tools

  • include: need lower-friction tool than Roam daily notes

  • Faster load time on Web than Roam

  • Better on mobile than Roam

  • Different workflow / fewer extraneous features than Roam

  • “I'm not the person Roam was built for” ~Adam Towers

  • Success Condition:   Alpha users will use it a ton over course of 1 mo

  • Possible success metrics

  • Roam metric: used > 4 days / week

  • 10 actions / day (most session duration numbers are kind of hard to leverage and measure these days. Number of actions are a bit more significant.)

  • 20+ notes a week on average
  • [Time: Spending over one hour per week on the app[r]](#cmnt18)[s]

  • Subjective metrics (e. “I would be very sad if this tool were to go away”)

  • [Note: Perhaps we should suggest people to use other tools for other workflows[t]](#cmnt20)[u], E.g. Workflowy for outlining class notes, and other todo trackers like omnifocus for tasks, so we can isolate this behavior?

  • Possible Outcome 1:

  • I hypothesize that finishing just the P1 features – which I see as the bare minimum for a quality app experience — will be sufficient to achieve this.

  • Possible Outcome 2:

  • Alternate hypothesis: the subset of users who currently like the iOS app won’t be satisfied with mobile web, and demand mobile web improvements OR sync with iOS app.

  • Jacob, David Bieber, Danish blockers primarily around snappy/quality experience

  • Navigation / design tweaks would be needed esp. on iOS e.g. Hashtags bar, clicking on hashtags to filter

  • Note: to get me (Jacob) personally to fully migrate from Thoughtstream iOS would additionally require relations, and possibly a few more changes

  • Possible Outcome 3:

  • Nobody actually likes the workflow of having a giant text file they prepend thoughts to. Maybe we skip to trying out Phase 1.5 Bullet View, then?

  • Feb 28

  • Product goals:

  • Mainstay Improvements

  • Very high-quality iOS experience (e.g. # on bar above keyboard), synced with web app, whether its wrapped react native, or Swift

  • Single user multi-device / multi-window sync. It doesn't have to be real time but maybe could even just pull every 3 seconds?

  • Relations

  • Implement bidirectional relations/improve relation experience

  • Make relations work in search bar

  • Great onboarding tutorial/walkthrough teaching the desired workflow

  • Changelog

  • If time, version history?

  • New Features

  • Relations

  • Inline expansion of relations in ideaflow.app (I’m calling Thoughtstream Web).

  • Not necessarily inline expansion of tags @’s and ~’s, but possibly – it would be great to experiment  

  • UX improvement experiments

  • e.g. Zen Mode: Mode where each new day creates many line breaks so you don't see past day’s notes on the screen, or you can click an expand button on any note to have it pop up to the size of a near-full-screen modal, requested esp. by Ben

  • Phase 1.5: Entanglement-style bullet view interface experiment

  • Highly requested by VC’s

  • Targets Notetaking Use Case 4

  • “4. Keeping “dossiers” on people (see also https://en.wikipedia.org/wiki/Farley_file ). Tools that Target this:  getdex.com CRM, Affinity CRM, Roam (sorta), and Ideaflow Phase 1.5 (Entanglement view, will discuss later) target this.”

  • Built off of core Thoughtstream Web codebase; ideally, minimal changes needed.

  • Design Possibilities:

  • View could be accessible via separate tab or menu

  • Thoughtstream Web interface could become an always-available top righthand bar drop-down when this view is active

  • Key features

  • Like Thoughtstream Web, but with the following changes

  • Starting to type a new note, e.g. “Ben Williams”, would initiate autocomplete.

  • Relation labels

  • e.g.

  • Ben Williams

  • Founder of: Auxparty

  • Lived in: Colorado

  • May require us to support labels inside <>’s on Thoughtstream Web, which isn’t a bad thing.

  • E.g. “He who has a why to live can bear almost any how”  ~Nietzsche “He who stands for nothing Falls for anything” ~Martin Luther King

  • May require design work on mobile

  • No date dividers by default

  • Target Users

  • People who need to network and remember people

  • CEO’s like Vlad from Lunchclub and their Chiefs of Staff

  • VCs like GFC’s Don Stalter, First Round’s Bill Trenchard
  • Superconnectors like Aku and Jacob

  • People with memory problems who also need to network: e.g. Sigward, who runs an accelerator

  • Success Condition:  Alpha users will use it a ton over course of 1 mo

  • Possible success metrics

  • Roam metric: used > 4 days / week

  • 10 actions / day (most session duration numbers are kind of hard to leverage and measure these days. Number of actions are a bit more significant.)

  • 20+ notes a week on average
  • [Time: Spending over one hour per week on the app[v]](#cmnt22)[w]

  • Subjective metrics (e. “I would be very sad if this tool were to go away”)

  • Ops Tasks:

  • Import Jerry/ Mark Trexler’s Brains

  • Onboard Jerry

  • Onboard Mark carranza?

  • Mar 30

  • Mainstay Improvements

  • Offline sync with iOS app

  • New Features

  • Tweaks

  • Experiment with treating separate lines of any note as implicit bullets, in a visually subtle way – jacob has mocks on this

  • Child notes / true hierarchical outlining, a la Workflowy

  • Could be built off of Inline expansion of relations

  • Would include features like zooming in like Workflowy has, Or maybe we would Implement zooming in with a modal

  • Thoughtstream Web interface could become an always-available top righthand bar drop-down when you're zoomed in?

  • Ideaflow Phase 1.6a?:  Auto Tagging/Extraction Tools

  • Audio note support and auto transcription

  • Reverse voice search

  • automatic extraction of title from URL

  • automatically tag link to article as #article #biology

  • process images / photos

  • OCR

  • object recognition and searchability

  • Screenshots

  • E.g.  Facebook post for Twitter tweet extract entities

  • Automatic backup of any linked web page

  • Phase 2: Collaborative Thoughtstreams

  • Use cases:

  • “3a. Very casual shared notes from calls/discussions”

  • 1:1 calls. Existing workflows: texting each other links, FB messages

  • Team Zoom calls. Existing workflows: Initially, Zoom chat, then copy paste to Slack
  • Zoom or Clubhouse group discussions/salons; Zoom classes as well. Existing workflows: LinkedIn/FB/Telegram group chat

  • Ideaflow Phase 2 hopes to be as low friction for this as texting someone!

  • “3b. Slightly more formal notes for interesting group conversations, idea brainstorming sessions at work, etc.  Note that this may be distinct from 1b. “General company meeting notes”.”

  • Zoom or Clubhouse group discussions/salons: Setting up a Google doc with notes like http://salon.jacobcole.net/ or http://systematicawesome.jacobcole.net/ . Roam is planning to becoming a tool for this as well.

  • Ideaflow should be the buddy tool every group chat – Create a Collaborative Thoughtstream for each one

  • E.g. anytime you have a big facebook or telegram group chat

  • Every community (e.g. SF Salon,  StartX) should have an ideaflow  
  • Even every 1:1 chat, e.g. Jacob & JM’s texting history

  • Each should have a collaborative thoughtstream that is distinct from a chat, because the chat may include transient information like “hey are you here yet”

  • Features:

  • Ideally, typing #book Eye of the World in a facebook group chat would cause it to get persisted to the group’s Ideaflow

  • This may be possible a la http://texts.com/

  • Future: Eventually we should probably build our own chat app to compete with FB & telegram ; Ideally it would be a new multichat client like texts.com

  • Should have memorable, typable urls, like sfsalon.ideaflow.app

  • These should be instant to create

  • I bought the domain if.new, kinda like docs.new :-)

  • Should be a list of all the created ones somewhere

  • Maybe like shared.ideaflow.app or thoughtstreams.io could be the url? And it would also of course have a big friendly create new button

  • We should have a “people tab” that’s basically a spreadsheet like http://people.worldquestguild.connectordocs.com/  where people can fill in their interests

  • Biz Ops Work

  • Build Global Idea Bank and migrate onto Ideaflow

  • Build database of all projects going on at MIT, Stanford, and other universities and migrate onto Ideaflow

  • April 30

  • Phase 3: Collaborative Rich Documents

  • Use Case:

  • “5. Creating high quality reference sources on various topics, like http://chronicpain.jacobcole.net/ . Requires precisely the same features as “1b. General shared company meeting notes. Requires Collaboration, Outlining, and at least some way to fudge todos in. Google Docs, Notion target this.”

  • Features

  • Headings and subheadings, some level of rich text, real-time collaborative text editor. Etherpad or Hackpad (or heck, Dropbox paper) would be a fine base functionality set. But I’d want a view where I can filter the doc, maybe in a pop-up by tags

  • 3 Differences between thoughtstream web editor and a minimalist docs editor

  • Hierarchies (achievable natural as an extension of inline expansion)

  • “Different” Features

  • Linkifying hyperlinks

  • Headings

---

#v0.1

Ben feedback:
Here’s my feedback:
Background: Notetaking is a broad term and refers to a lot of different workflows,
You listed three workflows, but I’m still not 100% clear on what workflows we are targeting and which ones we are not supporting. It would be awesome to have a clear guideline on that so we can all be on the same page for testing purposes

test the hypothesis that there exist at least a few people that really need an ultra low friction tool especially for the third category
who do we think these people are? Where do you think we can find them? What tools are they currently using to try to solve their needs? What are those tools missing? How many people is a few?[ae]

“Perhaps we should suggest people to use other tools”
If we can define the use case we are supporting, I think it makes it much easier to do this

Alternate hypothesis: the subset of users who currently like the iOS app won’t be satisfied with mobile web, and demand mobile web improvements OR sync with iOS app.
How many users on mobile do we have that currently meet the all three criteria that you listed?
 Subjective metrics (e. “I would be very sad if this tool were to go away”)
20+ notes a week on average
Spending over one hour per week on the app
Since we don’t track anything on mobile, do we have a way to know this?[af]

#Old road maps[ag]

Web Product Roadmap

Q3 2020
Q4 2020
Dec 2020
 make great thoughtstream experience
         perfect text editing, fast loading, sync mobile and web
                 launch to Alpha users like David Bieber, Danish, Andrew P, Ali

Q1 2021
        Make great ontology editor (bullet view) experience
         make great subdomain+docs  experience

Q2 2021

After Q2 2021
Integration with Google Docs

Mocks

figma sketch

Week of Nov 4 - 6
Week of Nov 9 - 13
Week of Nov 16 - 20

11/4
11/5
11/6
11/9
11/10
11/11
11/12
11/13
11/16
11/17
11/18
11/19
11/20
Milestones

Finalize Press Kit
Contact reporter for exclusive

Briefing with reporter

Priming email to F/F
Press Release Launch

Key Areas
Press Kit

Finalize Press Kit

Press relations

ID reporter
Contact Reporter

Briefing with reporter

Distribution

-

Social media

Others

Team Responsibilities
Jacob
Review positioning
Review PR draft
Approve Press kit

Briefing prep
Briefing prep
Briefing

Vince
Positioning
Positioning
Draft PR
Press Kit edits
Refine blog
Prep Jacob
Prep Jacob

JM
Positioning
Positioning
Draft PR
Press Kit edits
Refine blog

Arielle
- Review positioning
- ID reporters
- Review positioning
- ID reporters
Review blog
- Select reporters
Contact reporter
Prep Jacob
Prep Jacob

Christine

Websites[ah]

Ideaflow.io (homepage).
https://ideaflow.app/
https://apps.apple.com/us/app/thoughtstream/id1330828366
Augment chrome extension

Notes from http://productfeedback.jacobcole.net/

Top Priorities for December[ai] Alpha Launch/Share to Investors. Also Touchstones #designPrinciple

Target people:
- Bill trenchard (investor, new user),
- Danish (uses Web app on desktop some, thoughtstream native app on iOS),
- Jacob  (uses Web app on desktop, thoughtstream native app on iOS) ,
- David Bieber (uses thoughtstream iOS native, Roam on desktop)
- Ali Tarraf (mgmt consultant)

Detail Breakout examples (more tweaks below)

Lowest friction knowledge capture
- Mobile

  • Quick login and stay logged in on mobile
  • Bottom up autocomplete on mobile

  • Bar with # and @ etc

  • Instant load time

High quality text editor experience
- iOS web app has to feel as good as native[al]

Ben & everyone use the new app actively
- Jacob, Danish[ap] blockers primarily around snappy/quality experience

Gee-wow touches[ar]
- Inline expansion
- Import Jerry/ Mark Trexler’s Brains

Future/Defer
?never lose anything[as], history? – export covers this?
Offline mode
Changelog
Sort by Date

Marketing and Communications[at]

Press Release Workplan

Week of Nov 4 - 6
Week of Nov 9 - 13
Week of Nov 16 - 20

11/4
11/5
11/6
11/9
11/10
11/11
11/12
11/13
11/16
11/17
11/18
11/19
11/20
Milestones

Finalize Press Kit
Contact reporter for exclusive

Briefing with reporter

Priming email to F/F
Press Release Launch

Key Areas
Press Kit

Finalize Press Kit

Press relations

ID reporter
Contact Reporter

Briefing with reporter

Distribution

-

Social media

Others

Team Responsibilities
Jacob
Review positioning
Review PR draft
Approve Press kit

Briefing prep
Briefing prep
Briefing

Vince
Positioning
Positioning
Draft PR
Press Kit edits
Refine blog
Prep Jacob
Prep Jacob

JM
Positioning
Positioning
Draft PR
Press Kit edits
Refine blog

Arielle
- Review positioning
- ID reporters
- Review positioning
- ID reporters
Review blog
- Select reporters
Contact reporter
Prep Jacob
Prep Jacob

Christine

Positioning Prompt #1

Help Wanted

Roadmap

Team Pulse

  • Total Employees = 3 full time (really), + 2 (parttime david)+ 1 (albert), Contractors FT (1 JM) (contractor occasional: evan, vince, jen, aku, ?jenni), ,  [#]
  • Total Employees = [#]
  • New hires or losses, team mood, wins or concerns on the culture front.

Financials

  • Burn rate: ~$180k/mo (on budget)
  • Runway: ~3 years based on our current roadmap

Spencer Jacob Call Notes

Foundations

snappy experience
team that is energized creative hacking enjoying working
together
iterating rapidly with "users" internal or external
--
humanity: could get all basic needs met in 1 day with perfect coordination
even the big societal disagreements are tips on the iceberg

--

Could get substantial market share with just

Could get a lot of happy users just by cloning things

Prefers - 10x value

Foundation: basic text file sync ios and web app

Spencer: native mobile app is a must at least ios
                ? Fast knowledge capture e.g. rec?
        Some sort of bullet view

Can it be used by someone who is dictating/ quadruplegic

  1. make sure relations work in the search bar when you click on them  as per evan’s mock. Weird bugs atm.
    0.1 Can we pretty please have a mode where reverse relations are created automatically

“What man actually needs is not a tensionless state but rather the striving and struggling for a worthwhile goal, a freely chosen task. What he needs is not the discharge of tension at any cost but the call of a potential meaning waiting to be fulfilled by him.” ~Viktor Frankl #quote <> “He who has why to live can bear almost any how…

Tags:, book, Shabhala, –, the, sacred, path, of, the, warrior
Tags:, spiritualWarriorship

#yogaPerson spencer kim

“He who stands for nothing falls for anything” ~Martin Luther King #quote <> “He who has a why…

Tags:, book, Stealing, Fire

“He who has a why to live can bear almost any how” ~Nietzsche #quote
<> “He who stands for nothing…
<> “What man actually needs is not a tensionless

  • Inline expansion of relations as per Evan mock (other part) and jacob-ts-listview’

  • Labeled relations

  • If it’s not too tough to implement, from a logical progression standpoint, we should make it so that

Charlie Cheever Ideaflow is typable in thoughtstream
When you expand (inline expansion) it might say:

Charlie Cheever Ideaflo...
| + investor of: Ideaflow – Company founded at MIT <...>... Bat M...
| + early employee:Bat Manson
| …
      Literal text matches (“Unlinked references”)
      | Charlie Cheever Quora
      | Charlie Cheever Expo
      | a cool ios hacker is Charlie Cheever, who lives in palo alto  <> Feross

Ideaflow – Company founded at MIT   Charlie… Bat M...

Unlinked references with aggregation (Spencer version)

Charlie Cheever Ideaflo...
| + investor of: Ideaflow – Company founded at MIT <...>... Bat M...
| + early employee:Bat Manson
| …
      Literal text matches (“Unlinked references”)
      | Charlie Cheever Quora... Expo...

Unlinked references with aggregation (jacob version dirty)

Charlie Cheever Ideaflo...
| + investor of: Ideaflow – Company founded at MIT <...>... Bat M...
| + early employee:Bat Manson
| …
     Relations derived from literal text matches
|investor of: Ideaflow
|cofounder of: Quora
|founder of: Expo
    Literal text  “contains” matches (“Unlinked references”)
      | a cool ios hacker is Charlie Cheever, who lives in palo alto  <> Feross

Unlinked references with aggregation (jacob version clean)

Charlie Cheever Ideaflo...
| + investor of: Ideaflow – Company founded at MIT <...>... Bat M...
| + early employee:Bat Manson
| - investor:Charlie Cheever
|investor of: Ideaflow
     Relations derived from literal text matches
|cofounder of: Quora
|founder of: Expo
    Literal text  “contains” matches (“Unlinked references”)
      | a cool ios hacker is Charlie Cheever, who lives in palo alto  <> Feross

Charlie Cheever Ideaflo...
| + investor of: Ideaflow – Company founded at MIT <...>... Bat M...
| + early employee:Bat Manson
| - investor:Charlie Cheever
|investor of: Ideaflow
     Relations derived from literal text matches
|cofounder of: Quora
|founder of: Expo
    Literal text  “contains” matches (“Unlinked references”)
      | a cool ios hacker is Charlie Cheever, who lives in palo alto  <> Feross

  • Labeled relations more like bullet view

Charlie Cheever Ideaflo...
|  Ideaflow  – Company founded at MIT

Charlie Cheever Ideaflo...
|investor of: Ideaflow, Forge, Quora

  • Aggressive autocomplete of WHOLE NOTE (TOGGLABLE) – this is the possibly defining difference between the “2 windows” in jacob’s workflow

Below is with “Entanglement Mode” on – aggressive autocomplete

Charli

+ Charlie Cheever

  • Charlie Cheever Ideaflo...

  • Charlie Cheever Ideaflo…
    |investor of:Ideaflow
    |friends with: Mark Zuckerberg
    |founder of: Expo

Key difference between entanglement And thought stream as it is right now is how aggressive the autocomplete is

Jacob Cole:
        The point about being two views is almost a distraction by the way – as long as you’re able to have two windows open of the same application you don’t even need to views I don’t think for my optimal workflow
        All we need is basic in line expansion (+ unlinked references as Showable)
        *2 views
        Context and local scoping is a future point we can discuss
        Which I internally think of as a special “child-of” relation
        Anyway we can discuss Monday
        2pm doable?
Spencer Kim:
        thanks, that’s helpful
        Can we do 230?
Jacob Cole:
        Ya
        (Last point that we can go over in our next discussion: because I see child relationships as a special case of other relationships, I think it probably actually makes sense to support labeled relation ships before child relationships)

-

a cool ios hacker is Charlie Cheever, who lives in palo alto  <> Feross

ios hackernamedCharlie Cheever, wholivesinpalo alto

Who ( named( subject: ios hacker, direct object: Charlie Cheever), in(lives, palo alto) )

Tags:, tt, catchup, brody, <>, spencer, kim, linguistics, neurobiology

  • 1 1

1+1

1 1 +

Scratch Backup

  • Labeled relations

  • If it’s not too tough to implement, from a logical progression standpoint, we should make it so that

Charlie Cheever Ideaflow is typable in thoughtstream
When you expand (inline expansion) it might say:

Charlie Cheever Ideaflo...
|  Ideaflow – Company founded at MIT <...>...

Ideaflow – Company founded at MIT   Charlie…

  • Labeled relations more like bullet view

Charlie Cheever Ideaflo...
|  Ideaflow  – Company founded at MIT

Charlie Cheever Ideaflo...
|investor of: Ideaflow, Forge, Quora

Team Questions for next Roadmap Iteration

  • Business Strategy

  • viable paths however

  • Key Metric

  • Number of Power Users “Earlyvangelists”

  • Number of users who login more than four days/week (and take at least one write or search action?)

  • Strategy

Bat
- Would appreciate more business considerations rather than product features, need more Macro considerations on how to get to a good Series A
- Specific Questions: Key considerations for Series A? Will we do a Series A? How will we take into account user feedback & priority? How many users by when? What profile of users? Do we plan to sell / when will we sell? If you knew very little about the product & everything about the market, what would you do?
- Bat: Let's say users are overwhelmed by cognitive load presented by text file UI, this means we have to change the product which can make the product roadmap collapse on itself. Always risky to have a 6 month product roadmap, which is why startups are great & big corps are shit. I know it's important that we should have big opinions around product features, but this is a common cause for company collapse, for no one is paying attention to product-market fit.

  • Investor Expectations for Shone were very misaligned which is why they skipped on the series A
  • Jacob: Yes, idea is likely 1 or 2 of our investors would pre-empt a series A if they saw a few thousand users excited / if investors were excited using the app themselves. Majority of investors is 10k MAUs

Spencer
- It would be helpful if you built a completely different document than this
- Spencer’s recommendation from slack:

  • Concretely what would be helpful to understand is the business decision tree and I think something as simple as a chart or quick bullet points with some timelines and very high-level descriptions would be awesome
  • i.e. what exactly we are aiming for? What steps we are planning to get there? and along that path how we know (via metrics or otherwise) whether to keep moving forward or to try another direction
  • This would help answer some questions I have like — what is the current hypothesis we are trying to validate? and which user cohort does that target? Specifically what is our strategy for reaching and onboarding these users (PR?, personal networks)? What metrics (# of users, notes per day, etc.) do we need to reach to know we’ve validated this hypothesis? What is the goal after we get the traction we want (e.g. series A)? Instead if the experiment flops, which path do we go down and to what degree does that delay/change our goals?

Ben
- Re: Background: Notetaking is a broad term and refers to a lot of different workflows,

  • You listed three workflows, but I’m still not 100% clear on what workflows we are targeting and which ones we are not supporting. It would be awesome to have a clear guideline on that so we can all be on the same page for testing purposes

  • Re: test the hypothesis that there exist at least a few people that really need an ultra low friction tool especially for the third category

  • Who do we think these people are? Where do you think we can find them? What tools are they currently using to try to solve their needs? What are those tools missing? How many people is a few?

  • Re:  “Perhaps we should suggest people to use other tools”

  • If we can define the use case we are supporting, I think it makes it much easier to do this

  • Re: Alternate hypothesis: the subset of users who currently like the iOS app won’t be satisfied with mobile web, and demand mobile web improvements OR sync with iOS app.

  • How many users on mobile do we have that currently meet the all three criteria that you listed?

  • Subjective metrics (e. “I would be very sad if this tool were to go away”)

  • 20+ notes a week on average

  • Spending over one hour per week on the app

  • Since we don’t track anything on mobile, do we have a way to know this?

RPC Paper2Graph

[a]not possible afaik
[b]kk. curious if it would be doable if we put the app in a react native wrapper?
[c]yes.
[d]this is a duplicate, search is not working at all on develop
[e]so relevance sorting? Finally? Same for search then?
[f]I personally still prefer date sorting, with prefix matches lifted -- when we tried relevance sorting on thoughtstream ios, I found it hard to find recently created notes. I'm open to trying though
[g]What you spec is relevance sorting imho. Aka a ranking computed on length and position of the match (title/starting by/containing), frequency and freshness. What do you think relevance sorting would do differently from what you suggest?
[h]Do you want 2 buttons? This one and the general back button taylor has been working on?
[i]we discussed and said that "\n--\n" was a better note splitter criteria. If you want to convert from \n\n to "\n--\n" you only need one search and replace.
[j]not designed it will be hard to implement something in the next month if we dont even have polished mockups with open ended question
[k]I'm content with Sam's design https://www.figma.com/file/YBUbNIHBVfV6MT3aiLez3z/Visual-design-upgrade?node-id=3%3A31358
What do you think?
[l]if only we kept the select all to work as intended...we wouldnt have to surface a barely used button to the interface :)
[m]+1
[n]q3 is already over. Delivering a correct audio capture experience is like 6 months - it is its own app. Otter.ai took several years to provide such an experience...
[o]The main thing I was getting at with this is that sometimes these messages a) can't be dismissed and b) don't provide suggested solution (e.g. graphql one). I agree we should surface errors to users e.g. to tell them something is wrong and they should refresh, but they need to be somewhat interpretable by users and have provide steps to resolve (even if the step is just: "contact [email protected] for assistance)
[p]how many roughly 5 / 10 / 100 ?
[q]3?
[r]most session duration numbers are kind of hard to leverage and measure these days. Number of actions are a bit more significant.
[s]Done
[t]The market of users ready to take their notes in more than one place is intuitively under 1% imo. Sounds risky to address/target/create such a demo.
Would like to check numbers on that
[u]How about people who use iOS notes for ideas and reference lists but OneNote for lecture notes?
[v]most session duration numbers are kind of hard to leverage and measure these days. Number of actions are a bit more significant.
[w]Done
[x]how many roughly 5 / 10 / 100 ?
[y]3?
[z]what is the 3rd category, keeping reference lists?
[aa]most session duration numbers are kind of hard to leverage and measure these days. Number of actions are a bit more significant.
[ab]Done
[ac]The market of users ready to take their notes in more than one place is intuitively under 1% imo. Sounds risky to address/target/create such a demo.
Would like to check numbers on that
[ad]How about people who use iOS notes for ideas and reference lists but OneNote for lecture notes?
[ae]David Bieber, Alex List, Ben San Souci, me, and several others at least
[af]we at least have David Bieber, Alex List, Ben San Souci, me, and several others using thoughtstream to these criteria @[email protected] Can look into metrics
[ag]Should we ignore this?
[ah]?
[ai]we launch to investors then! Need to reconcile with the first page
[aj]please detail what you mean by holistically snappy. Are we talking about performance of the whole app?
At Apple we say make it work then make it beautiful then make it fast.
[ak]we usually dont write down not buggy. I know its not the intent, but that comes of as condescending and uneducated. Nobody in a team purposely make something buggy. It's always a question of threshold.
99% of apps have bugs, 99.99% of startup products have bugs and they still makemoney... so not buggy cannot be a goal per say.
Usually we dont talk about bug fixes in roadmaps and let engineering fix what has to be fixed
[al]as our native? please detail.
Its very subjective, I know for instance i would never use the current mobile app, it has too many undefined behavior and functional quirks that i can never be in the flow with it
[am]so... no error? :)
[an]duplicate of the paragraph above
[ao]is a duplicate of the paragraph above
[ap]could we get the feedback from danish eventually? From what I read he had issues with the color scheme...
[aq]Is a bit small to be in a roadmap. You have a team of 3 and a roadmap is for 1 quarter, so south of 200 days of work. This is half a day of work. What I read is more an product principle: never loose notes, which should be an invariant all among our journey. What do you think?
[ar]those are more roadmap worthy, they only miss the why and associated detail/specs/analysis
[as]sounds like a dup of can't start loosing content, or is it different?
[at]already present in the page before?
[au]There were 4 nodes that had duplicates