Anytype Docs
English
English
  • 👋Getting Started
    • Welcome
      • Mission
    • Install & Setup
      • Mobile
      • Vault
      • Key
      • Spaces
    • Objects
      • Blocks
      • Links
    • Types
      • Properties
      • Templates
    • Queries
      • Collections
    • Widgets
      • All Objects
    • Collaboration
  • Web Publishing
  • 📽️Use Cases
    • 🧠PARA Method
    • ✏️Daily Notes
    • 🍎Study Notes
    • 🎬Movie Database
    • ✈️Travel Wiki
    • 🗨️Language Flashcards
    • 🍛Recipe Book & Meal Planner
  • 🤖Advanced
    • Memberships
    • Features
      • Raycast Extension (macOS)
      • Custom CSS
      • Dates
      • Graph
      • Other Features
    • Data & Security
      • Import & Export
        • Migrate from Notion
        • Migrate from Evernote
      • Privacy & Encryption
      • Networks & Backup
        • Local-only
        • Self-hosted
      • Storage & Deletion
        • Bin
      • Data Erasure
      • Analytics & Tracking
    • Settings
      • Vault Settings
      • Space Settings
      • Keyboard Shortcuts
    • Community
      • Forum
      • Open Any Initiative
      • ANY Experience Gallery
      • Nightly Ops
      • Product Workflow
    • Help
      • FAQs
        • Any Timeline
      • Troubleshooting
        • AnySync Netcheck Tool
      • Beta Migration
    • Connect
Powered by GitBook
On this page
  • Why we build what we build
  • Work process
  • Discovery ⟶ Delivery
  • We hear you!

Was this helpful?

Edit on GitHub
  1. Advanced
  2. Community

Product Workflow

PreviousNightly OpsNextHelp

Last updated 1 year ago

Was this helpful?

Why we build what we build

The community has been the cornerstone of our work since Day 1. Today, we will attempt to open the product processes behind Anytype. This will be the first step and we hope to continue it in the future with more details if it is deemed valuable to the community.

There are always two critical questions regarding product work:

Before jumping to these ones, let's cover the basics.

Work process

  • Our year is divided into three seasons. Our aim is to have two-three releases per season.

  • Product team has two parts for each season: delivery and discovery.

  • During delivery, we focus on executing our plans, while in discovery, we gather insights for future planning.

Discovery ⟶ Delivery

The discovery process is typically behind the scenes, but it's crucial part since only during this part we can understand What? Why? How? .

During the planning for each season, we consider two types of features:

Strategic importance

  • Multi-spaces, with any level of work granularity

  • Multiplayer and truly secure collaboration between people

  • Experience library and community use cases

  • Files as an object as new dimension of file work

  • Log in process and account security

We hear you!

Things that will be covered based on the community requests:

…And much more!

On our , you can find the features that have been delivered or have gone through the discovery process and are due to be delivered.

🤖
public roadmap
Calendar & Timeline views
Make “toggle” a feature of every block instead of/in addition to a block type
Automatic Bi-directional linking + Rollups
Support for inline creation and display of sets
Web Clipper
Open and modify attached files directly instead of downloading them
Notification System: Larger Proposal for Discussion
Add a “sidebar” for viewing/editing multiple pages at once /
Add Tabs to show multiple pages
Share menu on mobile apps
Deeplinking
Widgets for Mobile Devices
Custom Storage Location
Voice Recorder
Ability to simultaneously edit Relations for multiple objects in a Set
Ability to insert Relations Inline with text
Scheme of year planing process