Your website is pretty much blank. Only words on the home page are about, login, and Elyxel. Also this post didn't explain what your project is. The about page contains a vague one sentence description.
You need to explain what problem you are fixing and how your product fixes it if you want to get any traction. People aren't going to signup if they don't know what they are signing up for.
I think you need to make it easier for people to get started. I almost didn't signup because I had to create an account before I could view any of the photos for sale. It would have been much easier to jump in if I could have just started browsing photos. Make make me signup after I have gone through a few pages of pictures.
The real kicker was when you asked for my credit card right away. I am a big fan of credit card up front on subscription services with a free trail. But I just wanted to see the product. There ins't anything for me to be excited about yet. Luckily I noticed that I could just click something in the menu to skip this step. I would put of asking for the card until you they go to make a purchase. You have my email address so you can already follow up if I abort at the CC step later.
Thanks for the feedback! I maybe need to make clearer that you actually can browse the pictures without signing up at https://brandfox.io/discover - the link is on the front page.
That's a good idea re the credit card part. The service is free to use and you're only charged if you purchase a picture but perhaps I could make that clearer and offer the option to skip (you can always do it in the settings later).
Thanks so much for the feedback and I hope the Board Game Tables business is treating you well. It looks mighty impressive from the site :)
Well, I guess if it really was out of a book, it would imply that the quality of the engine itself wasn't at fault, but rather a bad opening book. Also, without that line being thoroughly researched, it'd be difficult to say whether it's a blunder, or a clever sacrifice. Again, it could be an incomplete opening book which led the engine to offer the sacrifice, but then didn't have info on how to capitalise on it.
Though in this case, I think it's almost certainly a blunder, that line does not appear to be a well known opening.
There are opening books, and there are opening books. 1. Nf3 Nf6 2. e4 can no doubt be found in some opening books due to the sheer fact that someone, somewhere, played it, and it got archived. Then yes it's a line that could get selected at random.
It's not a serious opening though, it looks frivolous - could be played in simultaneous games, or in bullet chess for its surprise value etc.
Given the insame amount of opening theory research humanity has done by now, if e4 on the third move here was even remotely close to a clever sacrifice, chess community would have noted it by now.
Using important is only going to fix the problem if you have defined a style for that element. For example, if you have not defined a border then the client will still be able to add one.
Most sites use iframe for embeded widgets for this reason.
I think Stripe's checkout doesn't use iframe. They just define every single style with very specific rules. From what I remember.
He didn't find customers. He found 2K looky-loos. Customers are people who are paying for the product (or meet some activity threshold in a free product). He found 2K people who were willing to give their email address to learn more about what was being offered.
That is a positive sign, but they aren't customers. It seems like 2,00 people logged in and then found out the product wasn't what they were expecting.
I know this was the case for me. I signed up hoping for a really nice online IDE. I found a bunch of ssh stuff that made no sense to me.
It might be worth talking to the 2000 people and finding out why they signed up and what type of product they were hoping to find.
That's the point - if you don't have a product, you can't sell it. You can collect e-mail addresses, people may say they're interested in your product, but until you build it and users pay for it, nothing is sure. That's why I find the whole advice "sell it first, then build" a bit silly.
The idea sounds reasonable, although I think I'd struggle with the whole "actually getting up when the alarm goes off" problem.
I found a linked article on his page which addresses this problem, with a solution I'm going to have to try:
> This is going to sound really stupid, but it works. Practice getting up as soon as your alarm goes off. That’s right — practice. But don’t do it in the morning. Do it during the day when you’re wide awake.
You need to explain what problem you are fixing and how your product fixes it if you want to get any traction. People aren't going to signup if they don't know what they are signing up for.