Skip to content

feat: migrate mobile starter to NativePHP 4 SuperNative UI - #7

Merged
simonhamp merged 8 commits into
NativePHP:mainfrom
vipertecpro:codex/supernative-welcome
Jul 31, 2026
Merged

feat: migrate mobile starter to NativePHP 4 SuperNative UI#7
simonhamp merged 8 commits into
NativePHP:mainfrom
vipertecpro:codex/supernative-welcome

Conversation

@vipertecpro

@vipertecpro vipertecpro commented Jul 16, 2026

Copy link
Copy Markdown
Contributor
  • upgrade to Laravel 13 and NativePHP Mobile 4
  • register Native UI and replace the web welcome route with an EDGE component
  • recreate the welcome screen with native styling and dark mode
  • add a centered bundled NativePHP logo
  • add native rendering and accessibility coverage

Closes #6

- upgrade to Laravel 13 and NativePHP Mobile 4
- register Native UI and replace the web welcome route with an EDGE component
- recreate the welcome screen with native styling and dark mode
- add a centered bundled NativePHP logo
- add native rendering and accessibility coverage
@vipertecpro

Copy link
Copy Markdown
Contributor Author

Android Screenshot Light Android Screenshot Dark

iPhone Screenshot Light iPhone Screenshot Dark

@simonhamp simonhamp left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @vipertecpro!

This just needs a few changes for the imminent UI package release

Comment thread app/Providers/NativeServiceProvider.php Outdated
Comment thread resources/images/nativephp-logo.svg Outdated
Comment thread resources/views/layouts/app.blade.php Outdated
Comment thread resources/css/app.css Outdated
Comment thread composer.json Outdated
Comment thread package.json Outdated
Comment thread vite.config.js Outdated
@vipertecpro

Copy link
Copy Markdown
Contributor Author

I’ve left the provider namespace and Composer package unchanged because NativePHP/mobile-ui#8 is still open and nativephp/mobile-ui has not been published yet.

- Style the welcome screen entirely with native-ui theme tokens
  (bg/text/border-theme-*) and mirror the palette in config/native-ui.php,
  replacing hardcoded hex classes and per-element dark: variants
- Add a11y-hints to the welcome link rows and bundle the custom fonts
  the screen references
- Split NativeHomeTest into focused tests: rendering, theme-token-driven
  styling (asserted against config), full accessibility audit, and the
  browser bridge; add an arch test for NativeComponent conventions
- Fix the test env (APP_KEY in phpunit.xml) and refresh the published
  nativephp v4 config and Boost guidelines

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
shanerbaner82 and others added 3 commits July 21, 2026 08:57
Commit the Boost-published skill packs so the starter's CLAUDE.md skills
reference works on a fresh clone, and gitignore the per-developer
.claude/settings.local.json.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@PovilasKorop

Copy link
Copy Markdown

@simonhamp @shanerbaner82 don't want to add pressure as you're busy, but I think I would prioritize this, as this starter kit is literally the FIRST line in the docs of quick start :) https://nativephp.com/docs/mobile/4/getting-started/quick-start

@simonhamp
simonhamp merged commit 77a5fb9 into NativePHP:main Jul 31, 2026
@vipertecpro

Copy link
Copy Markdown
Contributor Author

Public Packagist only carries mobile-ui up to 0.2.0 (served from public GitHub). 0.3.0 exists only on the authenticated plugins.nativephp.com registry, so anyone cloning the starter and running composer install without credentials for that host gets:
The '.../mobile-ui-...zip' URL required authentication (HTTP 401).

Screenshot 2026-07-31 at 8 31 47 PM

@simonhamp

Copy link
Copy Markdown
Member

Thanks @vipertecpro, I'm looking into this now

@vipertecpro

Copy link
Copy Markdown
Contributor Author

Following up now that mobile-ui is on Packagist — there's one leftover that breaks a fresh clone. composer install currently fails with an HTTP 401 because composer.json still declares the private registry:

"repositories": [
    { "name": "nativephp-plugins", "type": "composer", "url": "https://plugins.nativephp.com" }
]

Since a custom repo outranks Packagist, Composer resolves the packages through plugins.nativephp.com (auth-gated) instead of the now-public Packagist copies, so a clean clone hits:

The '.../...zip' URL required authentication (HTTP 401).

Dropping that repositories block lets all three packages resolve from public Packagist — after doing it locally, composer install succeeds with no login and the suite stays green (8 passed / 81 assertions).

@PovilasKorop

PovilasKorop commented Aug 1, 2026

Copy link
Copy Markdown

Yup, confirming what @vipertecpro said above.

I'm getting:

  - Downloading nativephp/mobile-ui (0.3.0)
 0/1 [>---------------------------]   0%    Authentication required (plugins.nativephp.com):

@simonhamp

Copy link
Copy Markdown
Member

@vipertecpro @PovilasKorop this is now resolved. You may need to composer cc and/or remove composer.lock and re-run composer update

@vipertecpro

Copy link
Copy Markdown
Contributor Author

@PovilasKorop @simonhamp Please check this out #9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants