Native Theme Config API should match Web Theme Config API

[JeffWScott]

It would be really nice if I could reuse my theme settings JSON file that I have for the web version with the native version.
I don't know why you wouldn't do this when you already have a theme configurator for the web version.

Web (./web/tailwind.config.ts)

const {heroui} = require('@heroui/theme');
const herouiTheme = require('../shared/styles/heroui.theme.json');

/** @type {import('tailwindcss').Config} */
export default {
	content: [
		"./index.html",
		"./src/**/*.{js,ts,jsx,tsx}",
		"../node_modules/@heroui/theme/dist/**/*.{js,ts,jsx,tsx}"
	],
	darkMode: "class",
	plugins: [
		heroui(herouiTheme)
  	]
};

Native (./mobile/app/_layout.tsx)

import "./global.css"
import { HeroUINativeProvider } from 'heroui-native';
import theme from '../../shared/styles/heroui.theme.json'

export default function RootLayout() {
  return (

    <HeroUINativeProvider
      config={theme}
    > ...

In addition I see we have moved from content-1, content-2 etc for card backgrounds to "surface". I don't know why we would rename these (maybe there is a platform reason?) but we should aim to keep as much of the heroUI ideas transposable.

[vvv-sss]

Hey!

Regarding tailwind.config — it will not be used soon. HeroUI v3 and HeroUI Native will manage everything through CSS variables inside the global.css file.

Surface comes from the new design system, and its purpose is to provide the proper layer hierarchy.

[JeffWScott]

Thanks for the response.
That's interesting, I didn't know you were moving to a new design system (I do prefer surface to content BTW)

I see that Button in Native has no "color" attribute (only variant), is that also part of the new design system? Is it all in flux right now or can I read up on any of the decisions anywhere?

Would you say that a consistent API across web an UI is one of the goals for release?

[vvv-sss]

New design system is coming with v3 (https://v3.heroui.com/docs/introduction). We're trying to keep the API as consistent as possible between web and mobile, that's our goal