Skip to content

Latest commit

 

History

History
56 lines (40 loc) · 2.29 KB

README.stories.mdx

File metadata and controls

56 lines (40 loc) · 2.29 KB

import { Meta } from '@storybook/addon-docs' import StorybookLinkTransformer from './packages/@aetherspace/docs/helpers/StorybookLinkTransformer' import StorybookFontTransformer from './packages/@aetherspace/docs/helpers/StorybookFontTransformer' import ReadMe from './README.md'

🤔 So... why did I start with a hybrid first approach?

Consider this clip from the App.js conf intro talk by Charlie Cheever:

<iframe src="https://www.youtube.com/embed/te7bwfNsRKg?controls=0&start=2641&end=2748" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen ></iframe>


The stats don't lie:

  • More and more internet use on mobile vs. steady decline on desktop
  • 90% of that mobile internet use is coming from apps vs. mobile browsers
  • Mobile apps drive up to 3x more conversion rates than browsers (source)
  • Yet we seem to keep focusing on mostly building websites instead of apps
  • However, apps can still massively benefit from web (SEO, Discoverability, Landing pages)
  • So... why not go hybrid with Expo + Next.js from the get-go?

How Aetherspace helps you build smart from the start:

  1. Getting started -- Web & mobile with the GREEN stack
  2. Universal style & theming for Web, SSR & Mobile with tailwind -- Build your own Primitives
  3. Shared and platform specific routing for Expo & Next.js
  4. GraphQL and API routes -- Schemas and single sources of truth
  5. Automatic docs generation for components and data apis
  6. CI & near instant Deploys for web and App Stores -- With Expo & Turborepo