No video :(

Tamagui - The Best Stack for Universal Apps

Подписаться 54 тыс.

Просмотров 36 тыс.

50% 1

In this video I will talk through the decisions that we have made to setup a new monorepo for MY4X4. This monorepo will be based on Tamagui and will allow us to build our API and Web app using Next.js along with a React Native app with Expo.
We will discuss tRPC, Prisma, Kinde Auth and the reasons why we chose them. In the following videos we will work through setting up each one of these pieces.
The repo is available here:
github.com/ken...

Опубликовано:

4 окт 2023

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 28

@user-lk4nd8sf8o 10 месяцев назад

This video was great. Filled in some missing pieces for my mental model of what Tamagui was doing for me in certain places. Looking forward to more videos about your app. Thanks!

@lucasvazquez-sk1lv 7 месяцев назад

Amazing video, so great to hear your explanation about the toolset along the video

@kengreeff 7 месяцев назад

Thank you, glad it was useful :)

@franciscokloganb 2 месяца назад

I feel like Tamagui is flat out impossible to customize. I have read the docs over and over again, and still can't make createThemBuilder work. There's always something breaking because of misconfigured relationships between "palette", "template", "parent" and some theme key.

@kengreeff 2 месяца назад

Definitely has a steep learning curve. Probably why this video has performed so well

@yaroslavdraha9251 8 месяцев назад

Awesome intro!

@kengreeff 8 месяцев назад

Thank you :)

@maso4u 9 месяцев назад

Hey Ken, great insight btw. quick question though; 24:34 you mentioned how the "features" convention doesn't sit well with you and you prefer "screens" why is that the case for you?

@kengreeff 9 месяцев назад

Definitely just a personal preference thing. I guess it is because I think of a feature being anything from the ability to like a picture to a full sets of screens or actions, similar to a “feature request”. Small “features” would be components rather than full screens in my view. What’s your opinion?

@maso4u 9 месяцев назад

@@kengreeff my view was more so along those lines that features - as far as ui is concerned - are a set of functionalities that the app renders within different screens/pages. If you look at the screenshots from tamagui takeout the webapps auth screens/pages have the authentication features (login, signup, forgot password) on the left and the onboarding slideshow feature on the right

@ashuvssut23 20 дней назад

i dont like solito because we sometimes cant use react native libs directly with it. For example, when in need to use icons, I have to install expo-icons for native and some other icon lib(like react icons) for web

@kengreeff 20 дней назад

Thanks for sharing!

@kipfitpal 10 месяцев назад

Great video. How did you implement state management?

@kengreeff 10 месяцев назад

Since switching to tRPC we haven’t really needed global state. For local state we just reach for useState from react in a custom hook. When we need global state I’ll add a video for sure. What do you use for state management?

@uncleebenezer1928 10 месяцев назад

Xstate is doing cool things over there, if you'd be interested in implementing state machines..

@dreamecho100 9 месяцев назад

For me, if it's a global state I mostly use zustand

@FaysalBDev 2 месяца назад

how can we do SEO optimizations for Next if we are using the features folder?

@kengreeff Месяц назад

I’m not sure to be honest as I haven’t looked in to it. The features are shared and SEO isn’t really relevant for native apps. You would probably do it in the next/web folder directly