I developed a saas software (https://www.chatpapers.ai), aim to improve reading experience, which has two main features: chat with pdfs & generate mind maps.
The question is: Most of my users are interested in mind map generation but not chat with pdfs, many of them type commands in the input area (which is designed to ask questions about the pdf) and try to generate a mind map according to their commands, but this feature has not been developed. How should I improve it?<p>I have 3 options:<p><pre><code> 1. Add intent detection to the chat module, support both mind map generation with commands & retrieve information from the pdf in a same input box, which may increase the latency and take wrong actions.
2. Remove the chat with pdf feature and turn the product to mind map generation, which mignt strange because the product name is chatpapers.
3. Design a new product to focus on mind map generation, and keep this product as it is.</code></pre>
Which could be better? Or any other suggestions?
This is just what I'd do -- not saying it's the best thing to do.<p>With a new product, you're still working out what aspects of it appeal to customers more than others.<p>My habit has been to find that out as quickly as possible, then focus the product to just do that as well as possible. If I were in your shoes, I'd focus like a laser on the mind maps. Once that's nailed down and polished, I'd consider bringing in the other aspects.<p>The advantage of doing this is twofold: by focusing on a single thing, you can really excel at that thing and attract more customers because it rocks so much. Then, once you have solid customer base, you have a receptive existing audience for expanded capabilities (and to guide you as to what form is best for those new capabilities).
Why not ask the customers? It's great you have some traction and their actions are leading you to a direction where they find value. Lean into that!<p>In any event, no need to make drastic changes. Maybe idea 1, but definitely not wholesale changes like 2 and 3. There are plenty more options on the table, such as:<p>* make two submit buttons in chat area (chat vs mindmap)<p>* support very specific mindmap commands and use simple string matching for intent detection (not models)<p>* create a way for people to choose either chat or mindmap commands for the right hand sidebar<p>* add more example inputs (like the "show me a summary") to guide the users<p>* etc
I live by the Unix philosophy, so one simple tool that does one thing
very well is how I roll.<p>I could literally see myself on the command line typing<p>pdf2mm -i report.pdf -o report.xml -f "sales, drivers"<p>where -f is a list of strings to direct focus (seed the "centre of the
map")<p>Dump .xml or .opml<p>Get this right and you'd have no problem offering that as a paid Web
service and throw the cmdline util out there for free please. :)