Cross platform stack (web & mobile)

Do you folks have any recommendations on what an optimal stack from a developer point of view would be for a cross platform app (web & mobile) with backend included and full type safety? Technologies/libs I have been considering to use but I'd gladly take other suggestions. FE Related:
- Solito
- React Query
- Zustand (very uncertain on this point though)
- Firebase (considering this or AWS Amplify for authentication but would gladly get
other suggestions)
- NativeBase
- Potentially Dripsy for styling things outside of NativeBase
(I really don't like inline styling so Tailwind for styling is something I'm less likely to use over alternatives such as Dripsy but I could be convinced)
- Moti
- Solito
- React Query
- Zustand (very uncertain on this point though)
- Firebase (considering this or AWS Amplify for authentication but would gladly get
other suggestions)
- NativeBase
- Potentially Dripsy for styling things outside of NativeBase
(I really don't like inline styling so Tailwind for styling is something I'm less likely to use over alternatives such as Dripsy but I could be convinced)
- Moti
BE Related: (I've worked more with FE so this is a bit of a black hole for me)
- tRPC
- Prisma
- PlanetScale
- tRPC
- Prisma
- PlanetScale
Other things
- Zod
- AppCenter
- Vercel (or potentially AWS Amplify
- Github
- Sentry
- Fastlane
- Expo
- Zod
- AppCenter
- Vercel (or potentially AWS Amplify
- Github
- Sentry
- Fastlane
- Expo
40 Replies
Samathingamajig
Samathingamajigā€¢2y ago
GitHub
GitHub - t3-oss/create-t3-turbo: Clean and simple starter repo usin...
Clean and simple starter repo using the T3 Stack along with Expo React Native - GitHub - t3-oss/create-t3-turbo: Clean and simple starter repo using the T3 Stack along with Expo React Native
Wezter
Wezterā€¢2y ago
Yeah that's using Tailwind which I'm a bit sceptical about and it also isn't the complete stack right just a starting point if I'm not missing something? šŸ˜„
Unknown User
Unknown Userā€¢2y ago
Message Not Public
Sign In & Join Server To View
Wezter
Wezterā€¢2y ago
Oh I had missed that he's gonna have a talk there, I'll definietly have to check it out! šŸ˜„
Unknown User
Unknown Userā€¢2y ago
Message Not Public
Sign In & Join Server To View
Wezter
Wezterā€¢2y ago
I just dislike having a lot of inline styling, if there were something like styled components with better performance that works well cross platform I think I'd very much prefer that.
Wezter
Wezterā€¢2y ago
Things like this just makes me so annoyed to see šŸ˜… I'd very much rather have a tag that's called something
const CenteredLink = styled(a)`
// put styling here
const CenteredLink = styled(a)`
// put styling here
brr
brrā€¢2y ago
There is a extension* to collapse all the styles, but yeah it does look ugly
Wezter
Wezterā€¢2y ago
Yeah I know there's a plugin for it but then I'd much rather have it somewhere else than in my JSX personally, it just gets so cluttered šŸ˜…
brr
brrā€¢2y ago
agreed, I think you can also define all the styles in a function outside your component and then just call it so it can be like an external style sheet afaik I'm not 100% sure on this, but I think I seen it somewhere
Wezter
Wezterā€¢2y ago
I haven't found anything that's cleaner than Dripsy so far but was hoping someone here might have some good suggestions ^^ I looked a bit at Tamagui but their styled function is a bit limiting so far
Unknown User
Unknown Userā€¢2y ago
Message Not Public
Sign In & Join Server To View
brr
brrā€¢2y ago
you can put the styles outside your function or in another document
const styles = `bg-slate-100 rounded-xl p-8 dark:bg-slate-800 text-red-300`;
const styles = `bg-slate-100 rounded-xl p-8 dark:bg-slate-800 text-red-300`;
then import and
return <div className={styles}>random text</div>;
return <div className={styles}>random text</div>;
intellisense won't really work though this way afaik
Wezter
Wezterā€¢2y ago
I mean for personal projects I would most likely go for something like Tailwind because it's way faster to work on yourself but it's way less easy to overview in my opinion. If it's a rounded button I would much rather see <StyledButton ... /> that than a pressable with 10 styling props and then the onPress, text etc. Yeah and you still lose the understanding of what this div actually is and you have to write className for everything and then I could just have used stylesheets I feel like ^^
brr
brrā€¢2y ago
yeah I agree, tbh I'm quite new to tailwind was looking for something react query related and this thread popped up lol, someone might have better / cleaner solutions
Want results from more Discord servers?
Add your server