I'm creating a no-code visual recognition platform believing that people should be able to share their expertise in the form of visual dictionary. To have an app identifying Pokemon cards, vehicles or garden species via image, you just need to input sample images and content of the objects. Then you'll be able to share the app with whom you want to.
Take a look and tell me why you would NOT use it. Could be issues on your side, like you just don't need it, or from the product itself.
http://lookuq.com/
Hi Mai,
Looks great. Site is nice (simple, stylish) and tech looks awesome. Can you please clarify relationship/difference from Google Lens. I think perhaps one is you can be more nuanced (e.g. 'which orchid is this' verses ' which flower is this'). Maybe I have this wrong but is it fair to say "sharitek" is for industry apps and "lookuq" for public apps?
I have one industry application in mind but to answer your question "what makes you not use it" the current answer has to be risk and uncertainty. It is not clear to me how much time/effort/cost would be required for my use case and how successful it would be.
Have you given any thought into running pilot projects where you are able to give active support to early adopters to gain traction?
Hi rab, very thorough comment! You are right about "sharitek" and "lookuq". Sharitek is more B2B, and Lookuq is broader and more oriented towards public use cases.
I am actually offering pilot projects and actively seeking early adopters to use Lookuq for free with support from us. The creator-side landing page is designed with that intention. I may not be clear enough, or have not shown enough support. I am also looking for places to recruit early adopters, who love to try out our product and gives us feedback. There have been a few sign-ups, but I haven't been able to kick off with any.
Any suggestions on piloting?
It seems a bit similar to Google Lens - I'm trying to think of some niche use case that wouldn't be covered by Google Lens but I can't. I still think it's super cool idea though!
I am also unsure about how many sample pictures I would need to train my own app, that's another point that makes me unsure.
Thanks a lot for your comment! I should definitely make clearer guide to creating a new app.
Finding niche use cases seem to be our biggest problem. We actually aim at hobbies that are shared among small communities. I need to spend some time thinking about it.