Single comment thread
See full discussion

Based on the main screenshot (with get.index.ts) I get the feeling that qery can be used for managing only the Database. Because it's a all-in-one solution it might be helpful if the example provided in the screenshot would include more "features" that qery provides, not just the Database helper/wrapper.

I suppose it requires a payment/account to fully run it, but it could be helpful if npx @qery/query create command had a "copy me" like button next to it - for fast clipboard copy. If that is the only command a user needs to start using qery, you might want to add some kind of trigger/label next to it - smth like "just try it. run this thing"

"Go live fast" - how much faster? Maybe it can be quantified somehow - e.g. 30% faster.

What steps did you take, and at what point did you encounter something that made you think it required payment or an account?

It was an assumption, I didn't try running the command or anything. Was just saying that for end user it's harder to run that command when it doesn't have a copy-to-clipboard button next to it and also no label like "try me" or "see it for yourself"

When you first faced the command, what did you do, and what thoughts crossed your mind?

I clicked on it and was expecting a copy to clipboard. I thought it is the first and only command I need to run to get started with qery.

I get it. I thought it was as easy as double-clicking and Ctrl + C. I was wrong! Thanks for the feedback!

Sure, it is easy :D But removing one step from making the user try it, I think it could be useful in the long term.

Home
Search
Messages
Notifications
More