one of the Co-founders of Lykdat here.

After keeping Retail Intelligence in incubation for over two years of intensive and fine-tuning it, we're thrilled to introduce our AI-powered solution to the public.

At the core of our goal is to provide a retail market research solution that is affordable to most researchers. The industry right now is filled with extremely expensive alternatives (*whispers: not mentioning names).

It's important for us to get feedback so we've made a free demo page available to community to try hands on the solution:

https://pinsight.lykdat.com/demo

wishing luck with it

Thank you!

it's more or less offline since it's completely frontend based.

Probably the fact that you don't have to do it with Google Sheet if it's not your Jam.

Co-founder of Lykdat here;

Similarly to what we've done with our Image Search API(https://blog.lykdat.com/our-global-image-search-api-is/), we are taking a leap to make our Deep Tagging API available for free. So if you have any interesting Fashion AI ideas you are looking to implement, I'd be looking forward to seeing how our free solutions can help speed up your process to putting together a Proof of Concept.

Hi, yes you can. Just save the number and add it to your group

what does "post extraction" refer to here exactly?

I believe they are asking if, after extracting all the pieces (it's shipped as a self-extracting archive), does it do the things it needs to do to comply with GPL/AGPL? Like supplying the source code, or how to get the source code.

Installation essentially - the linked website doesn't link to licensing info for third-party dependencies. I was wondering if the licensing info (and source code of this product) were included in the installation bundle or available from the running product - since this is a requirement of the GPL license used in some of the dependencies.

The Windows app is an unsigned executable - not planning on running it myself.

While there hasn't been any actual deep dive into this on my part yet, as the App does all its bit on the user's machine, the code itself also does live on the user machine post-installation. There has been no additional effort made to obfuscate the code that powers the App.

What could possibly be missing at the moment is a written instruction that documents where to locate the code base on the user's machine post-installation

Very much different yes. Doc Converter doesn't re-use any of pdf2docx's GUI feature. Doc Converter's UI is instead built with Electron.

Hi, thank you for pointing out the room for improvement on the FAQ. What it attempted to communicate is that the App will indeed stop working after the License expires, so it will have to be renewed at that point

That's terrible. Writing "Buy Now" is dishonest. More like "One Year License Now".

Its license is also linked to the computer it was activated on. Change computers... too bad!

It's particularly egregious where there don't seem to be any substantive further improvements planned, and the underlying engine was not built by you.

I can see how the "Buy Now" text could be misleading. Tbh, that's just the default text that comes with the Paypal button, and it wasn't deliberated crafted that way to mislead buyers. I'll roll out an update to make it more explicit.

> there don't seem to be any substantive further improvements planned

About that, the truth is, it often starts with a use-case as simple as "convert PDF to Word". Improvements usually would come from user feedback, and continuous maintenance. While I deliberately started out to keep the App simple, there's a good chance that features and functionality would expand when user feedback gets in the mix.

I'm saying this from my experience with maintaining IGdm (https://github.com/igdmapps/igdm)

That's awful. Never do this to desktop apps. Their whole point is about reliability and ownership.

Hmm, I haven't used libpdf to know enough, but just from glance through its documentation, it seems libpdf is more suitable for creating and reading PDF files. If this is correct, then it'll be missing the bridge to converting the read content of the PDF file to a Word document

yes, it does indeed use pdf2docx under the hood. From a technical point of view, it doesn't do anything new asides from straddling Python and Electron into one App.

However, from an everyday user point of view, it does make it rather simple to convert pdf to word document. An everyday user won't be up for doing that via cli commands. And every alternative user friendly solution requires uploading your documents to servers (which could spark privacy concerns)

> And every alternative user friendly solution requires uploading your documents to servers (which could spark privacy concerns)

If the customer base is less technically adept, wouldn't most of them not care and just upload it to a cloud service? I ask sincerely - recently I've realized I don't have as firm of a grip on the 'average consumer' as I thought.

I just started testing fixpdfs.com, and some of the first feedback I heard when I asked users about pricing was "I'd rather download an app that does this than pay a subscription"

I would only trust my PDFs to Adobe, Microsoft, AWS, etc: the big players, very well-known, that are not going to use the content of the PDFs against me. And of course I'd rather use something that runs completely on my laptop.