[{"data":1,"prerenderedAt":294},["ShallowReactive",2],{"blog-kindle-highlights":3,"related-building-capacities-how-it-started-how-we-developed-tables":103},{"id":4,"title":5,"authorKey":6,"body":7,"category":81,"date":82,"dateFormatted":83,"description":84,"extension":85,"icon":86,"iconColor":86,"imagePath":87,"keywords":88,"meta":92,"navigation":93,"path":94,"readingTime":95,"relatedArticles":96,"seo":100,"stem":101,"__hash__":102},"blog/blog/kindle-highlights.md","My workflow to work with Kindle highlights","michael",{"type":8,"value":9,"toc":73},"minimark",[10,14,17,22,28,31,35,40,43,47,52,55,59,64,67,70],[11,12,13],"p",{},"One feature I'm really looking forward to in Capacities: an integration with Readwise to sync all my Kindle highlights automatically.",[11,15,16],{},"I've recently been playing with my Amazon Kindle highlights and exported them via email from my iPad. It is a great way to review all my highlights after finishing a book...",[18,19,21],"h2",{"id":20},"learning-new-vocab","Learning new vocab",[11,23,24],{},[25,26],"img",{"alt":21,"src":27},"/blog/kindle-highlights/new-vocab.jpg",[11,29,30],{},"For my reading in French, this mostly involves unknown vocab, which I highlight in a certain color. Using our AI integration in Capacities, I was able to generate a neat markdown table with the German translation of each word and an example sentence in French. I was amazed at how well this worked and how suited the example sentences were.",[18,32,34],{"id":33},"deepening-my-understanding","Deepening my understanding",[11,36,37],{},[25,38],{"alt":21,"src":39},"/blog/kindle-highlights/deepen-understanding.jpg",[11,41,42],{},"For another book, I was more interested in highlighted sections. I did some manual formatting to make them look nice and added toggles to the chapter headings. You can see the result in the screenshot. For me, this is a great way to work through the key sections of a book and deepen my understanding.",[18,44,46],{"id":45},"keeping-track-of-key-personalities","Keeping track of key personalities",[11,48,49],{},[25,50],{"alt":21,"src":51},"/blog/kindle-highlights/key-personalities.jpg",[11,53,54],{},"Whenever I highlight a person using the color blue, I go on to create a person object for my people database. This way, I remember the key personalities involved in a topic and can do further research on them.",[18,56,58],{"id":57},"let-the-ai-assistant-explain-concepts","Let the AI assistant explain concepts",[11,60,61],{},[25,62],{"alt":21,"src":63},"/blog/kindle-highlights/explain-concepts.jpg",[11,65,66],{},"For example, when I was encountering the Cantillon effect, I asked the AI assistant to briefly explain the concept to me:",[11,68,69],{},"While this works already really well, it requires a certain amount of manual formatting. That's why I am looking forward to a Readwise integration to fully automate this process.",[11,71,72],{},"Let me know what you think!",{"title":74,"searchDepth":75,"depth":75,"links":76},"",2,[77,78,79,80],{"id":20,"depth":75,"text":21},{"id":33,"depth":75,"text":34},{"id":45,"depth":75,"text":46},{"id":57,"depth":75,"text":58},"team-product","2024-04-06","April 6, 2024","I've recently been playing with my Kindle highlights and exported them via email from my iPad.","md",null,"/blog/kindle-highlights/kindle-highlights.jpg",[89,90,91],"Kindle","Readwise","books",{},true,"/blog/kindle-highlights","3 min",[97,98,99],"building-capacities","how-it-started","how-we-developed-tables",{"title":5,"description":84},"blog/kindle-highlights","T1cLBZMNMEAJPIgR8vy96CDK9oMwwQFmyhSK4BPR9hk",[104,154,215],{"id":105,"title":106,"authorKey":107,"body":108,"category":81,"date":139,"dateFormatted":140,"description":141,"extension":85,"icon":86,"iconColor":86,"imagePath":142,"keywords":143,"meta":146,"navigation":93,"path":147,"readingTime":148,"relatedArticles":149,"seo":151,"stem":152,"__hash__":153},"blog/blog/building-capacities.md","How we decide which new features to add","steffen",{"type":8,"value":109,"toc":137},[110,113,116,119,122,125,128,131,134],[11,111,112],{},"We often get asked how we decide which features we add to @CapacitiesHQ. 🗺️",[11,114,115],{},"Here’s the answer. 👇",[11,117,118],{},"Very important: Every feature starts with a need or problem. There should never be a feature if it’s not solving a real problem. This cannot be stressed enough. Otherwise, you’re building a product with no real value and a lot of clutter.",[11,120,121],{},"We draw most feature inspiration from our community's feedback and by using the product ourselves. This helps us identify problems and friction points that stop users from getting their work done. We sometimes joke that our community is our first employee: a rigorous tester, opinion consolidator, and key source of inspiration.",[11,123,124],{},"Feature requests and explicit product improvements can be added to our feedback board, voted and commented on by other users. We review and cluster all requests and analyze their importance. This helps us to get a better understanding of the different needs and problems of our users.",[11,126,127],{},"In long and intense discussions, we combine all requests, comments, and ideas with our intuition and vision for what Capacities should become. We always radically aim for usefulness and simplicity – Capacities should just work and help, nothing else.",[11,129,130],{},"When features are big and fundamental, we share proposals or plans in our community for feedback. This ensures that we constantly have our users at the table with us. We fine-tune and iterate until we find a draft that fits into the greater picture.",[11,132,133],{},"Then we start creating. After a first draft, we introduce an early version to a small, selected group of alpha testers. In intense and incredibly helpful discussions, we optimize the last 20% in a combined effort. We refine the feature by addressing issues, polishing details, and enhancing interactions.",[11,135,136],{},"After a feature is released to all users, it’s not done. We constantly improve, iterate, and measure how it fits into users' workflows. Every feature is part of a continuous evolution of the overall product. We constantly strive to build a unified and consistent product – a beautiful environment to think and work in: a Studio for your Mind.",{"title":74,"searchDepth":75,"depth":75,"links":138},[],"2024-03-04","Mar 6, 2024","What's our decision making process? Here's the answer.","/blog/building-capacities.jpg",[144,145],"Feature development","Build in public",{},"/blog/building-capacities","2 min",[150,98],"why-the-name-capacities",{"title":106,"description":141},"blog/building-capacities","yUEsybivkdEpilRjL0YjnGhgRSjIYeDYSFuYsPOVPcQ",{"id":155,"title":156,"authorKey":107,"body":157,"category":81,"date":202,"dateFormatted":203,"description":204,"extension":85,"icon":86,"iconColor":86,"imagePath":205,"keywords":206,"meta":209,"navigation":93,"path":210,"readingTime":148,"relatedArticles":211,"seo":212,"stem":213,"__hash__":214},"blog/blog/how-it-started.md","Why did we decide to build Capacities?",{"type":8,"value":158,"toc":200},[159,171,174,177,180,183],[11,160,161,162,166,167,170],{},"Everything started at university in Germany. Michael and I studied computer science and electrical engineering and realized this big divide between the ",[163,164,165],"strong",{},"technologies we were learning about"," and the ",[163,168,169],{},"technologies we were learning with",".",[11,172,173],{},"It struck us how unnatural most processes were: exchanging files, monolithic large documents, presentations, etc. We knew that there must be a better way. Today's technologies are so powerful. We knew we could build something simple and intuitive yet powerful and versatile. Something so natural that all friction and issues magically disappear, something that does not force us into adjusting our thinking to it but something that is an extension of ourselves.",[11,175,176],{},"All solutions out there did not meet what we had in mind. Some where based on traditional principles; they inherit a lot of biases from computer architectures: Folders, files, tables, and hierarchies. Others were complicated to get started with, had overwhelming degrees of freedom, or required commands and special syntax. They were not simple enough.",[11,178,179],{},"We decided to start from scratch. We threw away all assumptions about computers and how we work with them. We started with the human being in the center and got inspired by our natural way of interacting with our environment. That’s where everything started.",[11,181,182],{},"Read more:",[184,185,186,194],"ul",{},[187,188,189],"li",{},[190,191,193],"a",{"href":192},"/about/principles","Our principles",[187,195,196],{},[190,197,199],{"href":198},"/about/manifesto","Our manifesto",{"title":74,"searchDepth":75,"depth":75,"links":201},[],"2024-03-13","Mar 13, 2024","Knowledge work can be overwhelming. There must be a better way, so we decided to do it ourselves.","/blog/how-it-started.jpg",[207,208],"Origin story","Knowledge management",{},"/blog/how-it-started",[150,97],{"title":156,"description":204},"blog/how-it-started","FFhq00AomCENeh-0oz0gzxW2I7k72YKgMY0Sd5-HBhk",{"id":216,"title":217,"authorKey":6,"body":218,"category":281,"date":282,"dateFormatted":283,"description":284,"extension":85,"icon":86,"iconColor":86,"imagePath":285,"keywords":286,"meta":288,"navigation":93,"path":289,"readingTime":148,"relatedArticles":290,"seo":291,"stem":292,"__hash__":293},"blog/blog/how-we-developed-tables.md","How we developed tables in Capacities",{"type":8,"value":219,"toc":277},[220,223,227,230,256,259,263,266,269],[11,221,222],{},"Recently, we launched tables in Capacities. It's a major addition to our app, and we developed the whole feature in just a couple of weeks. I wanted to share a little bit about the process and why we think it's one of the best table implementations in any note-taking app.",[18,224,226],{"id":225},"figuring-out-what-to-build","Figuring out what to build",[11,228,229],{},"From the beginning, we wanted it to stand out from table implementations in other note-taking apps while making no compromise on the UI/UX side of things. So these were our requirements:",[184,231,232,238,244,250],{},[187,233,234,237],{},[163,235,236],{},"A super nice UI/UX:"," keyboard accessibility, many shortcuts, using patterns already familiar to our users.\nMaking them pretty and well-formatted: Supporting a variety of formatting options and styles that allow users to make beautiful and useful",[187,239,240,243],{},[163,241,242],{},"Deep integration into the app:"," part of PDF export, rich-text in table cells, seamless copy and paste, linking to any content from within table cells, saving tables as objects, interaction with the AI assistant, familiar formatting options, export to CSV, reusing UI patterns our users already know, saving important tables as objects. For example, the table in this screenshot was generated by our AI assistant in the app.",[187,245,246,249],{},[163,247,248],{},"A powerful extra feature:"," We added formulas like in Excel to make it stand out from other note-taking apps. It allows for a whole range of new use cases. While this will never replace a tool like excel, it is very useful for doing some calculations and the fly and have them right inside your note-taking app. This also works great as a \"Pro\" feature.",[187,251,252,255],{},[163,253,254],{},"Being versatile:"," Having a flexible data model that is not too rigid and structured. Supporting simple inline tables for layout purposes all the way to tables-as-objects that users can open in full-page and revisit frequently.",[11,257,258],{},"We found that this is a combination that is not present in any other note-taking app and really makes @CapacitiesHQ\nstand out.",[18,260,262],{"id":261},"how-we-built-it","How we built it",[11,264,265],{},"We made the table feature the main project of a new employee. While this sounds risky, it allowed us to go the extra mile because he could spend all his time and effort on this one feature. We could then completely polish it with the input from the rest of the team. This focus gave us an enormous speed.",[11,267,268],{},"Another thing that made us super fast on the development side was reusing as much code and as many concepts as possible that already existed in the code base. This also allowed our new dev to get to know the codebase, use powerful abstractions, and learn by imitating what was already there.",[11,270,271,272,276],{},"Feel free to check out our new ",[190,273,275],{"href":274},"/whats-new/release-35","table implementation"," and let us know what you think!",{"title":74,"searchDepth":75,"depth":75,"links":278},[279,280],{"id":225,"depth":75,"text":226},{"id":261,"depth":75,"text":262},"dev","2024-03-11","Mar 11, 2024","Explaining our process and why we think it's one of the best table implementations in any note-taking app.","/blog/how-we-developed-tables/tables-cover.jpg",[144,287],"tables",{},"/blog/how-we-developed-tables",[97],{"title":217,"description":284},"blog/how-we-developed-tables","7fMYgPlcRfO9nXtEwOP-Tan_98apOd_KgV8I6kjoa_8",1780666696159]