It's funny I had a similar idea but with dashcams, for the automotive industry. You could pay people to install additional cameras to there cars and pay them by the miles driven. I'm sure car manufacturers would love this training data.
It's a great reminder of how well MacOS 9 UI and UX were designed, and how space efficient the whole OS was on screen.
Even the window handle bars were subtly shadowed, the window shadows evolved when they were collapsed. Like Windows 95 at the time, Mac OS 9 was a beautiful work of interaction design.
As a French founder, am I authorized to do a business trip in the US (meet local customers, pitch product features, invite prospects at a restaurant) with a simple ESTA?
> It does not have an ability to independently think and imagine/dream
We neither if we're not supplied with energy. By the way, haven't we tried to replicate an inner dialogue by prompting the AI to recursively converse with itself? This could resemble imagination, don't you think?
> It suffers from catastrophic forgetting under certain internal circumstances (in addition to changing what dataset we trained it on)
I believe that the persistence of previous answers is what currently distinguishes us the most from the "AI". As soon as we're able to make the realtime discussions part of an ever evolving dataset constituting the AI itself, the gap will get thinner and thinner. But even then, are people suffering from Alzheimer sentient? I believe they are. Isn't it comparable with what happens when an AI catastrophically forgets?
I really dig the product and demo. Nevertheless, I feel there are crucial points missing in your landing page:
- Where is the code hosted?
- Where is it executed?
- Are my tasks versioned in a GIT repo?
- How do you manage secrets?
I've got the chance to be one of the interviewed. I really like the way this is going. Their idea for extensions building and distribution is really clever and I appreciate how they've been tackling the developer experience.
If this behavior is to be implemented through request headers, I'd prefer not to mess with Content-Type because it may be needed in the request: you could still want to PREVIEW but ask for a preferred content-type, like text/xml or application/json
It's a non-issue for most French people like myself. In France, the Tesla cars are in the luxury price segment. There's no need to incentive the car that only wealthy people can afford.
To be honest and having been there before you, it's not a good idea. You entered a crowded space with a product that do not yield blatant differentiation. Your marketing, brand image and storytelling are the only things that will lead users to your app.
I don't think web developers will elect a newborn CMS, trust that it doesn't fail for the 5 or more years, if you don't convince them your CMS and the company behind it is future proof. And on that matter, your landing page and your documentation matter more than everything else. Invest time and money in it.
It looks really neat! What's your plan on making this project viable in the long run? Do you envisage to monetize hosting, or maybe create a community vs. paid edition?
Hey there, congratulations for the launch. I just wanted to give a quick hint that bothered us a lot. I see in this screen (https://www.uxtweak.com/statics/overview/rpl-record.png) that you provide a script tag with data attributes. Don't do that! You'll notice that a lot of your potential users are using a tag manager like GoogleTagManager. Those platform rewrite JS on the fly and do not take these attributes into account. Good luck!
