SunghoYahng

I agree here. Actually, in most cases, it was enough to know only the definitions. I could come up with applications from definitions on the spot. The thing to watch out for is to get used to the way to solve problems and forget the definitions. I think this is a more frequent occurrence (especially when preparing for the exam.) Then the one will get trouble if they need other applications.

Yes I have plans because everyone says it would be better if there are video demos here. I wonder if product tours are not enough.

Thanks for the suggestion. The app already has export and import functions, so it would be nice to have established notes. But I also think people need a note-taking and organizing something by themselves for learning. I think that's why people take notes even though they have well-organized tons of books.

I'm not really sure what it means for the forking mechanism. I would be grateful if you could show me a link to the resource for the forking mechanism you mentioned.

As for the tree structure, the tree structure is already reflected to some extent. As with breadth-first search, the questions starts from the higher level, but when the parent node is in the wrong state, the child node does not appear in the problem. I'll search more about the half-life regression you mentioned!

Maybe the goals you've mentioned aren't about features. As for the success of the app, actually, it couldn't get popularity and is used only by very few people. Maybe I better put all of my brilliant plans behind, pay attention to marketing above all and decide the fate of this depending on the result... (it won't go away, but how much I should focus on it)

It's nice to see you on Reddit and see you here again.

For now, I will focus on functions as a basic SR program for the time being. So the next big updates are: The feature to manage contents through a tree structure, the feature to divide media such as images into multiple parts to make it questions, and of course mobile app.

And, actually, I have more ambitious goals than just the SR program. My goal for this is to build an integrated learning environment. In my opinion, the ability to hold personal knowledge can be small but right entry point for bigger things.

Specifically, the first is a ML-powered learning resource viewer. If you can simply view multiple formats (pdf, video, etc) in one place and make it work with LO on the spot, that would be good. But it can go further than that. Now, text readers are all bad, because I think they aren't taking full advantage of the digital interactivity. They are just putting paper books on the screen. I want to build a viewer that allows users to interact with texts using ML (like IDE for reading).

The second is a finder of learning resources. Now, the learning resources are quite scattered, and I think it would be nice to be able to manage various learning resources in one place. I think that way, I can build an app like Netflix for learning resources.

And like any other edtech software, I may be able to make it possible for users to collaborate with others in this app. But I don't have many ideas for this part yet.

Hey. For the past 2 years, I have been working on LearnObit (https://learnobit.com).

When I first started to learn coding, I used Anki and the old tried-and-tested Spaced Repetition algorithm, but it wasn't suitable for more complex, general topics like Mathematics or Physics. Because of that, Spaced Repetition has always been widely overlooked despite its proven effectiveness in learning.

I wanted to unlock this effectiveness for a wider audience by building LearnObit, a tool that combines tree-structure note-taking tools with Spaced Repetition so that you can apply it to more than just simple fact pairs.

And now it even has the feature to export data to Anki, so you can leave with your data when you decide not to use it! (Of course I don't want anyone to use it, but I couldn't help it, because people wouldn't start using it without this in the first place...)

Anyway, I'll be here anytime if you have any questions for me. Thanks for your time.

I didn't even know that the web app could be made on-premise. Thank you. I will look for this topic.

Thank you for your case. I'm still wondering what is the ground for people who want open source to fall into 'might pay' group. I would like if you explain that part more.

This seems right, provided that I can make the product good enough. It would be a much harder way to make it good enough than to make it opensource and gather users.

I should consider whether the early startup even without funding can afford to choose that path.

Maybe that's right. Thank you very much

That's so clear. Thank you. The words "consumers' solution solves nothing" touched my heart. However, I have no idea about how to solve the data retention problem except for being open source.

This is interesting. Thank you. But I wonder whether getting sponsorship is a business model that startups can have (and the way to succeed this way seems too long, so I wonder if I can sustain it). In the Github guide, the case of Travis CI is interesting. I'm going to dig it.

Thank you. But people didn't seem to hate paying, but to worry about locking their data into the product in its infancy.

You may want to mix different note formats as needed. For example, you can use Google keep for simple notes and Evernote for notes that need to be organized. It is also a good idea to use a tree-based note-taking tool to organize your refined knowledge. This is because the structure of knowledge follows the structure of the tree. I use this(Actually, I made it): https://learnobit.com

Thank you so much for the detailed feedback!

1) I agree with the advantages of open source, but this project is commercial, so I have to find a way to make money. :(

2) Right. If I die, I will disappear. It wasn't rigid enough.

3) Gathering all the features in this app is not the goal. As for Todolist, it was not intended to be for general planning, but rather to assist in organizing knowledge. In context, one of the app's goals is to create specialized tools for organizing knowledge. Other tree-structured apps (e.g. Workflowy, Dynalist) are not specialized for organizing knowledge; instead they have a general purpose that can be used everywhere. I think this limits their functionality. LearnObit will implement specialized functions for organizing knowledge, not for general purposes.

4) I am thinking about the structure of knowledge that is not the tree structure. What I'm now going to implement further is for 1:1 pairs, which fit conventional SRSs like Anki. The app will deal with this by implementing a spreadsheet-like interface. I also understand that there is knowledge with graph structures, as you say. But I don't have an idea yet about what interface to deal with. Perhaps I will come up with ideas later.

5) For the tool you want, https://roamresearch.com/ might be good. This is a tool that combines Workflowy and Wiki.

I'm sorry I didn't solve the problem until late. This situation was caused by Firefox's lack of support for RegEx's lookbehind assertion. I'm trying to create a non-lookbehind version for RegEx.

Actually, it's not. LearnObit is now for the desktop. I think it fits LearnObit to be on the desktop, where the user sits down in one spot and concentrates deeply on using it. I will release a mobile version later, though.

Thanks for the feedback so far. I didn't even notice that the app had this many problems.

I'm embarrassed to show you an incomplete app, but anyway I think now I've fixed all the parts which received the feedback, Including proofreading the entire contents of the landing page.

Okay. I understand now that the problem is to reduce the amount of complexity. And thank you for the compliment!

That's right. I fixed it. I forgot to set it up after adding the web version. Sorry for the inconvenience.

Thanks for the advice. I did not notice that it's that terrible level. I'll get this corrected overall.

Thanks for the feedback. The web version was added a while ago. I wanted people to use LearnObit as a desktop application. But I'll make it work in Firefox.

I've received the correction: Planning for learning will be non-stop, as your knowledge (not information) is manageable. Perhaps now the sentence is understandable.

Thank you so much for your suggestion; I didn't notice it. As you can see, I'm not a native English speaker. I'll make some corrections to the content on the landing page.

Hey.

For the past 2 years, I have been working on LearnObit ( https://learnobit.com): a new and rapid way to learn anything.

When I first started programming, I used Anki and the old tried-and-tested Spaced Repetition algorithm. This was great for word-pairing (such as when you learn French or another language), but didn't suit for more complex, general topics like Mathematics or Physics. Because of that, Spaced Repetition has always been widely over-looked despite its proven effectiveness in learning-retention.

I wanted to unlock this effectiveness for a wider audience by building LearnObit, a note-taking tool which lets you organize and structure complicated/layered information then manage this via Spaced Repetition as easily as you use flash cards today.

I'll be here anytime if you have any questions for me. Thanks for your time.