I am also an early adopter of Tamagui and can say that documentation has gone much better than it was before, but still needs lots of improvements. I myself struggle with many packages we have installed with Tamagui, and at this point I don't know which one to keep and which can be removed.
We are working on documentation more actively than before. Please do reach out to me with any questions or feedback. Now that I'm full-time for the first time this is something I can actually focus on.
Thanks Nate! One immediate feedback I would like to give is to improve the configuration/setup documentation, like config/v1/v2/v3, packages like @tamagui/animations-react-native/babel-plugin/config/font-inter/react-native-media-driver etc. There is very less about these packages on the documentation or maybe not easily accessible.
Thanks - noted to the team. We're moving a lot faster now that I'm full-time and I finally have two really great devs alongside. Look forward to improving this and having people say "actually it's really good now" in a few months time.
I was building a very similar solution two years back after seeing the struggle of managing the assets for the design teams. Mostly people were using google-drive to share/collect/update the assets which was not very systematic. I envision my solution to fix this with the similar insiparation of VCS and proper integration with existing design tools, but after some time realized that the solution was not good enough and it quickly became too technical for the design folks.
I mean this is the struggle. And props to you for building that. It's an ugly problem.
I actually do think (and have personal evidence now to believe) that most functions adjacent to engineering can learn distributed version control. Once you start using it, you really don't want to go back.
We've internally adopted trunk based development for our assets and it gets rid of 99% of the confusing parts of version control to not use branches (I know blasphemy). My designer just pulls and pushes on the main branch and I do the same -- we've had very very few merge conflicts and none that couldn't be resolved in 30 seconds.
I feel silly now having spent so much time on branching as a feature. It makes a lot of sense for plain text and code but it probably doesn't matter that much (for small teams) for visual things. Merging has proven to be invaluable to us though.
Every clone in git is a branch. People like to enterprisify things, resulting in miserable people, wasted time, and money flowing into consulting firms.
Exactly! This was actually Linus' point when he was explaining git to companies still on cvs. "You're all already using branches anyway".
I think if you're in a low-trust enterprise environment, branches kind of make sense because you get the additional scrutiny of code-review and merges occur on a centralized server but if you're in a four person team where you trust everyone just use the main branch and resolve locally.
> Remember, git replaced tarballs
I would refine that to say 3-way-merging replaced tarballs but yes!
> 3) In the keynote, the demo of logging into to other services like Spotify appears to just be stealing the auth tokens from the laptop and shipping them to the R1 device. Not a good sign.
I don't think the tokens are getting transferred to the device. It seems everything happens on the cloud, so the tokens must have been stored on the cloud too.
I think the tokens are stored on device. I think what is happening is that this is effectively an Android device (or web browser) that you are somewhat normally logging into apps on. Then the LAM (which is running on device) is interacting with those authenticated apps behind the scenes, and only showing you the slick black screen with the rabbit and results on it.
Few suggestions:
1. Change/Update your logo. I find it hard to read it the font is not best for alphabets.
2. In the product itself, the brand name is reversed for the shopkeeper. I initially thought maybe it's some smart name that could be read in reverse as well (like 1300135 lol). It is overengineered, just keep it simple it.
3. Add a real use-case demo in your website. It is currently filled with garbage/gibberish.
I know, I understand the thought process behind it. But the font selection ruined it completely. If someone picks the device, optically the first letters in the logo looks like "SOW" and brains tries to read the word.
Edit: Also looks like it has a display underneath for "TO". As I said, this is overengineering, removing it will save cost.
I've been thinking about this for 12 hours. This product is going to change everything (sales going to skyrocket). The only problem I see if how Apple projected it in the entire demo.
They are projecting this to be like a mobile phone which will always be the part of day-to-day activity, but in reality this is not.
This is a single person device which will be only used when no one is around and mostly for work. Nothing else. You can't expect someone to have this on his head all the time for all the thing.
