Just want to clarify... please don't go too overboard with it... Keeping the information presented in a clear and comparable manner should be the highest priority!
How it works is twitch users enter prompts by using the chat using the “!p” prefix. When a user enters a prompt, the “countdown” timer starts. Every user in the chat can add to the prompt. When the timer completes, an image is generated from the prompt and stable diffusion that’s run on the cloud.
Hey, author here. Thanks for the feedback, sorry about the lack of marketing material - I'll get better at it. Let me address some issues you brought up:
- "all i see is a video of someone fiddling with setting for an already completed app."
The demo isn't starting with an "already completed app". Graphite generates a default app based on your GraphQL schema, and it is up to the user to further customize it to their needs. That's why it looks "already completed".
- "where are the demo showing how to easy it will be to connect your graphql service to this."
Connecting to the GraphQL services was shown in the beginning of the demo video when I typed in the GraphQL URL.
- "where is the demo showing how to actually build a screen with data being pulled from graphql"
Every screen in the demo video showed data being pulled from GraphQL. Graphite generates the queries behind the scenes automatically without the user even knowing.
your video has no sound, voice over or explanation _what_so_ever_. again... you built the thing, so you know what's going on. how am i, as a potential customer, suppose to know what this is and does. you can defend yourself til you're blue in the face but that doesn't make the video any more clear to a potential customer. I would suggest that you look at these other product demonstration videos for inspiration.
i'm not trying to be a jerk. you have most likely put an incredible amount of time and energy into bringing this product to life. don't let it fail because you refuse to take another day and demonstrate it properly.
You have to manually edit the display for every single instance of an item, rather than just being able to set it for all items of that type? That seems tedious and error-prone.
Thanks for the feedback, I get where you're coming from. I thought a lot about this. If you set it by type, then it wouldn't make sense either. Take pokemon() and pokemon() { evolutions } for example. For pokemon() you would expect a profile like component, and for evolutions you would expect a list item component, even though they are the same type (Pokemon). That being said, reusable components is on the roadmap, this is just the beginning.
Good point, it generates a web app! It's built with native tech so eventually native apps. I've heard that suggestion a lot, video coming soon. Thanks for the feedback!
Thanks for the UI advice, I'll work on this.