NativeScript / NativeScript/nx
[Question] shared core codebase with different {N} frontends for mobile?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 68
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I wonder if this Nx plugin could satisfy the requirement to create multiple variants of a {N} application where core parts (non-UI) are shared and the concrete variants have custom (Angular) application tier logic and UI.
The variants would need their own metadata (final app name, signing, bundle identifiers, package names, etc.) so they would come with their own build & packaging time configuration (Info.plist, AndroidManifest.xml, code signing etc.)
Would that work?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the Nx plugin's support for NativeScript and Angular application variants, then determine whether shared non-UI code and per-variant metadata, signing, and packaging configuration are supported. Done means a clear answer about whether this architecture works and what configuration it requires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100