@expo Next, align the Stack and Tabs APIs, at least in the sense of packages? 😬
Native Tabs and Headless Tabs
Native Stack and Headless Stack
Expo Router UI just sounds confusing.
Also change the API to match others (Tabs, Tabs.Trigger, instead of TabTrigger)
@congressdj Have also had very bad issues with the 12V battery - sometimes the screen just wouldn’t turn on, the reset didn’t do anything… Service center just said: We unplugged and plugged it back in to do a “hard reset”. Happened again after a few days.
Terrible experience overall.
@congressdj I also have very bad build quality… Like, the interior has been doing creaks and pops from the start. The front seat had to be adjusted twice, and some parts replaced due to rubbing/creaking/random noises.
@Baconbrix@buildwithdjdev I understand that, but currently Expo UI is separated by platform if I’m not mistaken.
Will there be a uniform API for these components across all supported platforms after the independant packages get out of alpha and beta?
@Baconbrix@buildwithdjdev Is the general plan to have Expo UI components handle all platforms in a universal way?
Say one Button component that displays a native to each platform button (Web/Android/iOS), or individual packages like there is currently (individual packages for SwiftUI / Jetpack Compose)?
Am I stupid or does @expo’s Font package not work on web?
I swear to god I have tried everything with their config method, but it just doesn’t run on web…
Are the docs just missing some disclaimer that it’s Android & iOS only?
@jpudysz Will create one tonight! It’s a pretty simple one if it’s an edge case… It follows the Quickstart in the docs to the dot, and not much else is done.
@jpudysz I just followed the docs:
- Made a blank Expo project (default template)
- Followed Quickstart (linking to ./app/global.css and ./app/uniwind-types.d.ts, added global.css to the top _layout)
- Changed the components folder to use className instead of style
@Baconbrix@expo A headless Stack should give you the options, but you choose what to do with them. No default gray background, no header… Stack, StackSlot, useStack, style it, ship it.
I love @expo. I love what it does, what it’s trying to accomplish, but damn do I hate the opinionated React Navigation…
Expo Router UI solves one of the two major painpoints, by giving us a headless Tabs, but for the love of god… Headless Stack components!
@Baconbrix
@Baconbrix@expo That is not the issue.
The issue isn’t the lack of customizability, but rather the fact that current Stack implementations force this styling upon you unless you remove it, whilst it should be the other way around.