# Expo Svelte > Svelte 5 on React Native Fabric, with no React: write Android and iOS apps as Svelte components. This is its guide. Every page is also available as Markdown, at the address listed. ## Getting started - [Introduction](https://svelte-native.alfayez.dev/docs/introduction.md): Write Android and iOS apps as Svelte 5 components that become real native views, laid out and drawn by the platform. - [Creating a project](https://svelte-native.alfayez.dev/docs/creating-a-project.md): Create a SvelteKit project, add Expo Svelte and run the app on a phone or an emulator. - [Project structure](https://svelte-native.alfayez.dev/docs/project-structure.md) - [Coming from the web](https://svelte-native.alfayez.dev/docs/coming-from-the-web.md): Svelte on a phone is the Svelte you know: the same compiler, the same runes, the same template syntax. What is different is everything the browser used to... ## Core concepts - [Routing](https://svelte-native.alfayez.dev/docs/routing.md): Expo Svelte has SvelteKit's filesystem-based router: the directories under src/routes are the screens of your app. Web routes are +page.svelte and... - [Styling](https://svelte-native.alfayez.dev/docs/styling.md): There is no CSS engine on the device. Each component takes a style prop: a plain object with React Native's style keys, in camelCase, with numbers for sizes.... - [Loading data](https://svelte-native.alfayez.dev/docs/loading-data.md): A native screen is not rendered on a server and has no load function. It loads its own data when it appears, in one of two ways: with fetch, or with... - [State management](https://svelte-native.alfayez.dev/docs/state-management.md): State works as in any Svelte app: $state in a component, shared state in .svelte.ts modules, and context for state that belongs to part of the tree. A few... - [HTML elements](https://svelte-native.alfayez.dev/docs/html-elements.md): You can write a native screen with HTML elements.
,

,