Fundamentally, the problem is not the fact LogoFox is a logo maker. Because this applies also to logo designers. A due diligence is done on a case-by-case basis by someone specialized in doing this. We process thousands of logos, we naturally can't make a due diligence for every single one logo created.
Hi, Alan from LogoFox here. I understand your concern regarding the IP terms.
I will make it straight and simple.
1) We use third-party icons from The Noun Project. We use their Pro API which gave us the right to use and sell the icons in part of the logos. Those icons are from thousand designers around the world. Normally when a designer uploads an icon on The Noun Project, they gave their IP. But, how can we be sure the icon uploaded is really their own creation? We can't.
2) We use hundreds of fonts. We check the license for all of them. But even with that, there is still a small risk of license infringement.
3) Thousand of logos are created every hour on LogoFox. Some will probably look similar to existing logos out there. For obvious reasons, we can't personally take the liability for the logo generated on the site. You have to make your due diligence.
Those 3 reasons mainly explain our current terms. This allows us to protect ourselves from any liability problems that may occur. Those liabilities also exist with a logo designed by a logo designer. The difference is, we don't deal with one logo a week but with thousand. So we adapted our terms accordingly. I hope you understand.
TLDR: no matter if your logo comes from a logo maker or a designer. You have to make your due diligence.
I wanted to make a quick way to motivate me when I don't feel to work. Pretty simple idea !
But what I'm the most proud is the generating of quotes. So I passed a csv and then, the quotes are generating almost automatically (regarding the author and keyword). Make it really simple to generate 100 quotes+.
I developed my first SWA with angular 2 + firebase database/hosting.
In one hand, the dev process is really easy and fast (firebase deploy to upload your website).
In the other end, if you want to be fully serverless it's start to getting more complicated. Using external service to manage form (form.io), page pre-rendering (prerender.io), notification...
I don't know why analytic, crash report are only available on Android/iOS because when you are able to do your sdk on 2 platforms. 1 more shouldn't be that hard.
Mmm interesting...I won't choose to buy ads for a landing page for 3 reasons.
- I personally tried and people coming from ads don't convert as well as qualified than people coming from a guest post for example.
- You are sure you will never see again your money (even for validating an idea. It's a waste of money)
- It's time consuming when you've never done it before, and when you don't know precisely what people should you target
So 2 way to do it :
Start from an audience and build the perfect product for them. And then enlarge your niche.
1) 2 weeks to call 100 of small business, entrepreneur...any people that use spreadsheet
2) From there, you will have already a good idea if people are interest in your idea and what people exactly want your product
3) And you can only start to make a plan with your 5000$ from here.
Pros :
- 2 weeks of work
- Be sure to have an audience interested by your product
- Know exactly what feature you have to do
Use case demo : make lot of use case of different spreadsheet and webapp. And send maximum traffic on it.
Drawback :
- you have to make a landing page -> time/money
- you have to send traffic -> time/money
- It can quickly become overwhelming because of the large number of different people with different need.