native-update 1.4.8 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/Readme.md +13 -1
- package/android/src/main/java/com/aoneahsan/nativeupdate/BackgroundUpdatePlugin.kt +15 -0
- package/android/src/main/java/com/aoneahsan/nativeupdate/BackgroundUpdateWorker.kt +23 -7
- package/android/src/main/java/com/aoneahsan/nativeupdate/LiveUpdatePlugin.kt +152 -4
- package/android/src/main/java/com/aoneahsan/nativeupdate/NativeUpdatePlugin.kt +14 -1
- package/android/src/main/java/com/aoneahsan/nativeupdate/NotificationActionReceiver.kt +10 -1
- package/android/src/main/java/com/aoneahsan/nativeupdate/SecurityManager.kt +18 -18
- package/cli/AGENTS.md +29 -0
- package/cli/CLAUDE.md +51 -0
- package/dist/esm/__tests__/security-enforcement.test.d.ts +1 -0
- package/dist/esm/__tests__/security-enforcement.test.js +95 -0
- package/dist/esm/__tests__/security-enforcement.test.js.map +1 -0
- package/dist/esm/core/config.d.ts +6 -15
- package/dist/esm/core/config.js +1 -4
- package/dist/esm/core/config.js.map +1 -1
- package/dist/esm/core/security.d.ts +11 -3
- package/dist/esm/core/security.js +19 -6
- package/dist/esm/core/security.js.map +1 -1
- package/dist/esm/definitions.d.ts +38 -24
- package/dist/esm/definitions.js.map +1 -1
- package/dist/esm/firestore/firestore-client.js +4 -0
- package/dist/esm/firestore/firestore-client.js.map +1 -1
- package/dist/esm/firestore/schema.d.ts +2 -0
- package/dist/esm/firestore/schema.js.map +1 -1
- package/dist/esm/index.d.ts +1 -2
- package/dist/esm/index.js +0 -2
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/live-update/download-manager.d.ts +36 -5
- package/dist/esm/live-update/download-manager.js +61 -22
- package/dist/esm/live-update/download-manager.js.map +1 -1
- package/dist/esm/live-update/update-manager.d.ts +12 -1
- package/dist/esm/live-update/update-manager.js +38 -10
- package/dist/esm/live-update/update-manager.js.map +1 -1
- package/dist/esm/live-update/version-manager.d.ts +9 -0
- package/dist/esm/live-update/version-manager.js +40 -0
- package/dist/esm/live-update/version-manager.js.map +1 -1
- package/dist/esm/plugin.js +95 -175
- package/dist/esm/plugin.js.map +1 -1
- package/dist/esm/web.d.ts +18 -1
- package/dist/esm/web.js +69 -24
- package/dist/esm/web.js.map +1 -1
- package/dist/plugin.cjs.js +1 -1
- package/dist/plugin.cjs.js.map +1 -1
- package/dist/plugin.esm.js +1 -1
- package/dist/plugin.esm.js.map +1 -1
- package/dist/plugin.js +2 -2
- package/dist/plugin.js.map +1 -1
- package/docs/AGENTS.md +38 -0
- package/docs/CHANGELOG.md +167 -0
- package/docs/CLAUDE.md +101 -0
- package/docs/MIGRATION.md +87 -0
- package/docs/README.md +13 -2
- package/docs/deployment/HOSTINGER_DEPLOY.md +329 -0
- package/docs/features/laravel-nova-backend/ASSESSMENT-SUMMARY.md +96 -0
- package/docs/features/laravel-nova-backend/IMPLEMENTATION-PLAN.md +504 -0
- package/docs/features/laravel-nova-backend/credentials.ignore.md +34 -0
- package/docs/features/laravel-nova-backend/progress-tracker.json +184 -0
- package/docs/guides/no-cost-backend-implementation-plan.md +77 -0
- package/docs/guides/no-cost-firestore-google-drive-backend.md +60 -0
- package/docs/project-knowledge-base/01-system-overview.md +218 -0
- package/docs/project-knowledge-base/02-routes-pages-forms-users.md +346 -0
- package/docs/project-knowledge-base/03-tech-stack-modules-services.md +347 -0
- package/docs/project-knowledge-base/04-data-models-integrations.md +307 -0
- package/docs/project-knowledge-base/05-docs-corpus-inventory.md +193 -0
- package/docs/project-knowledge-base/06-operations-testing-legal-content.md +170 -0
- package/docs/project-knowledge-base/README.md +90 -0
- package/docs/project-profiles/native-update-capacitor-update-platform-project-profile-last-updated-2026-03-16.md +454 -0
- package/docs/project-profiles/native-update-capacitor-update-platform-project-profile-last-updated-2026-03-24.md +66 -0
- package/docs/project-profiles/native-update-capacitor-update-platform-project-profile-last-updated-2026-03-25.md +67 -0
- package/docs/seo-aeo-rules.json +3043 -0
- package/docs/tracking/seo-checklist-tracker.json +333 -0
- package/ios/Plugin/BackgroundUpdate/BackgroundUpdatePlugin.swift +50 -6
- package/ios/Plugin/LiveUpdate/LiveUpdatePlugin.swift +238 -8
- package/ios/Plugin/NativeUpdatePlugin.swift +8 -0
- package/ios/Plugin/Security/SecurityManager.swift +13 -14
- package/package.json +31 -32
- package/docs/play-console-rejection-rules.json +0 -428
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
# Native Update AI Knowledge Base
|
|
2
|
+
|
|
3
|
+
## Metadata
|
|
4
|
+
|
|
5
|
+
- **Project:** Native Update
|
|
6
|
+
- **Knowledge Base Purpose:** High-context reference set for AI tools, planning, development, QA, legal review, content generation, and portfolio/social reuse
|
|
7
|
+
- **Coverage Goal:** Provide a practical, current map of the product, codebase, docs corpus, routes, forms, users, modules, integrations, and operating assumptions
|
|
8
|
+
- **Reference Date:** 2026-03-16
|
|
9
|
+
- **Last Updated:** 2026-03-16
|
|
10
|
+
- **Update Cadence:** Every 2 weeks minimum while the project is active, plus any time major product or docs changes land
|
|
11
|
+
- **History Policy:** Keep update history in this file and keep only the latest 10 entries
|
|
12
|
+
|
|
13
|
+
## Folder Purpose
|
|
14
|
+
|
|
15
|
+
This folder is the canonical high-context AI reference set for the Native Update project. It is meant to answer questions like:
|
|
16
|
+
|
|
17
|
+
- What does the product do?
|
|
18
|
+
- What features exist now?
|
|
19
|
+
- Which users exist?
|
|
20
|
+
- Which pages, routes, and forms are present?
|
|
21
|
+
- Which services, stores, modules, and native layers exist?
|
|
22
|
+
- What is the recommended backend and data model?
|
|
23
|
+
- Which docs already exist in `/docs` and what do they cover?
|
|
24
|
+
- What legal, marketing, testing, and planning context is already documented?
|
|
25
|
+
|
|
26
|
+
This folder is intentionally different from the public docs. Public docs explain usage. This knowledge base explains the whole project to an AI system or future collaborator.
|
|
27
|
+
|
|
28
|
+
## File Map
|
|
29
|
+
|
|
30
|
+
- `01-system-overview.md`
|
|
31
|
+
Product scope, capabilities, platform coverage, user types, URLs, and decision context.
|
|
32
|
+
|
|
33
|
+
- `02-routes-pages-forms-users.md`
|
|
34
|
+
Website routes, dashboard/admin routes, page purposes, major interactions, forms, and access rules.
|
|
35
|
+
|
|
36
|
+
- `03-tech-stack-modules-services.md`
|
|
37
|
+
Repo architecture, package structure, frontend services, stores, plugin modules, CLI commands, native modules, and backend components.
|
|
38
|
+
|
|
39
|
+
- `04-data-models-integrations.md`
|
|
40
|
+
Firestore schema, document purposes, authentication model, Google Drive flow, manifest publishing flow, and system boundaries.
|
|
41
|
+
|
|
42
|
+
- `05-docs-corpus-inventory.md`
|
|
43
|
+
Full inventory of the current `/docs` folder, grouped and described so AI can understand what knowledge already exists.
|
|
44
|
+
|
|
45
|
+
- `06-operations-testing-legal-content.md`
|
|
46
|
+
Testing posture, production/release considerations, legal pages, SEO/content context, and known constraints for planning or messaging.
|
|
47
|
+
|
|
48
|
+
## Primary Project URLs
|
|
49
|
+
|
|
50
|
+
- Marketing website: `https://nativeupdate.aoneahsan.com`
|
|
51
|
+
- Docs entry: `https://nativeupdate.aoneahsan.com/docs`
|
|
52
|
+
- Contact page: `https://nativeupdate.aoneahsan.com/contact`
|
|
53
|
+
- NPM package page: `https://www.npmjs.com/package/native-update`
|
|
54
|
+
|
|
55
|
+
## High-Level Product Definition
|
|
56
|
+
|
|
57
|
+
Native Update is an open-source Capacitor update platform. It combines:
|
|
58
|
+
|
|
59
|
+
- OTA/live updates for web assets
|
|
60
|
+
- native app update handling
|
|
61
|
+
- in-app review prompting
|
|
62
|
+
- background update checks
|
|
63
|
+
- release manifests and rollout control
|
|
64
|
+
- security validation and signing support
|
|
65
|
+
- a web dashboard for app/build management
|
|
66
|
+
- example backends and example apps
|
|
67
|
+
- CLI tooling for release workflows
|
|
68
|
+
|
|
69
|
+
## Recommended Use Of This Folder
|
|
70
|
+
|
|
71
|
+
- Use this folder as the first-stop AI context before generating plans, code proposals, QA checklists, legal summaries, portfolio content, SEO drafts, social content, or roadmap suggestions.
|
|
72
|
+
- Use the public `/docs` folder when exact implementation or end-user guidance is needed.
|
|
73
|
+
- If any detail in this folder and the source code conflict, the source code is the stronger authority and this folder should be updated.
|
|
74
|
+
|
|
75
|
+
## Update Checklist
|
|
76
|
+
|
|
77
|
+
- Re-check all routes in `website/src/router.tsx`
|
|
78
|
+
- Re-check user/auth/admin assumptions in auth context and route guards
|
|
79
|
+
- Re-check forms and fields on dashboard pages
|
|
80
|
+
- Re-check package versions and tech stack
|
|
81
|
+
- Re-check Firestore types and backend assumptions
|
|
82
|
+
- Re-check `/docs` inventory for added/removed files
|
|
83
|
+
- Re-check any new `CLAUDE.md` files in nested subprojects
|
|
84
|
+
- Update `Reference Date`, `Last Updated`, and `Update History`
|
|
85
|
+
|
|
86
|
+
## Update History
|
|
87
|
+
|
|
88
|
+
| Date | Summary |
|
|
89
|
+
|------|---------|
|
|
90
|
+
| 2026-03-16 | Initial AI knowledge-base folder created with project-wide coverage across product, routes, forms, modules, data models, docs corpus, and operations context. |
|
|
@@ -0,0 +1,454 @@
|
|
|
1
|
+
# Native Update - Capacitor Update Platform Project Profile
|
|
2
|
+
|
|
3
|
+
## Document Metadata
|
|
4
|
+
|
|
5
|
+
- **Project Name:** Native Update
|
|
6
|
+
- **Project Type:** Open-source Capacitor plugin + update management platform
|
|
7
|
+
- **Primary Domain:** Mobile app infrastructure / developer tooling / OTA delivery
|
|
8
|
+
- **Owner / Creator:** Ahsan Mahmood
|
|
9
|
+
- **Primary Contact:** aoneahsan@gmail.com
|
|
10
|
+
- **Package Name:** `native-update`
|
|
11
|
+
- **Current Package Version Reference:** `1.4.9`
|
|
12
|
+
- **License:** MIT
|
|
13
|
+
- **Primary Website:** `https://nativeupdate.aoneahsan.com`
|
|
14
|
+
- **Reference Date:** 2026-03-16
|
|
15
|
+
- **Last Updated:** 2026-03-16
|
|
16
|
+
- **Filename Rule:** Always keep `last-updated-YYYY-MM-DD` in the filename
|
|
17
|
+
- **Status Reference:** This profile reflects the repository state visible on 2026-03-16 from source code, docs, package metadata, tests, website pages, and example apps. Some older docs in the repo describe earlier pre-production stages.
|
|
18
|
+
|
|
19
|
+
## Executive Summary
|
|
20
|
+
|
|
21
|
+
Native Update is a full update-management solution for Capacitor apps that combines over-the-air web asset updates, native app store update flows, in-app review prompts, background update checks, security tooling, developer CLI utilities, example backends, and a web dashboard into one ecosystem. The project is designed to help developers ship fixes faster, reduce release friction, improve app quality, and maintain tighter control over the mobile update lifecycle across Android and iOS.
|
|
22
|
+
|
|
23
|
+
This project is not just a plugin. It is positioned as a complete developer platform around update delivery, release management, rollout control, verification, and user engagement for hybrid mobile apps built with Capacitor.
|
|
24
|
+
|
|
25
|
+
## Short Positioning Lines
|
|
26
|
+
|
|
27
|
+
### One-Line Version
|
|
28
|
+
|
|
29
|
+
Native Update is an open-source Capacitor update platform that unifies OTA updates, app store updates, in-app reviews, background checks, security verification, and release management in one package.
|
|
30
|
+
|
|
31
|
+
### Two-Line Version
|
|
32
|
+
|
|
33
|
+
Native Update helps Capacitor developers ship JavaScript, HTML, and CSS fixes instantly, manage native store updates intelligently, and improve ratings through in-app review flows. It combines plugin infrastructure, security tooling, CLI automation, example backends, and a management dashboard into one developer-friendly system.
|
|
34
|
+
|
|
35
|
+
### Resume / CV Summary
|
|
36
|
+
|
|
37
|
+
Built **Native Update**, an open-source Capacitor update platform that streamlines OTA delivery, native app updates, in-app review prompts, secure bundle signing, rollout management, and dashboard-based release operations for hybrid mobile apps.
|
|
38
|
+
|
|
39
|
+
## Resume-Ready Achievement Bullets
|
|
40
|
+
|
|
41
|
+
- Built an open-source Capacitor update platform that combines OTA updates, app store update flows, and in-app reviews in a single developer-focused package.
|
|
42
|
+
- Implemented cross-platform native support with Swift for iOS and Kotlin for Android, backed by TypeScript APIs for Capacitor apps.
|
|
43
|
+
- Designed secure update delivery with checksum validation, signature verification, HTTPS enforcement, certificate pinning support, and bundle integrity controls.
|
|
44
|
+
- Created a full release workflow including CLI tooling for bundle creation, signing, verification, key generation, backend scaffolding, local server startup, and deployment monitoring.
|
|
45
|
+
- Developed a companion dashboard and marketing site for app management, build uploads, rollout control, analytics visibility, and configuration generation.
|
|
46
|
+
- Added example implementations for React + Capacitor, Node.js + Express, and Firebase-based backend flows to reduce adoption friction.
|
|
47
|
+
- Structured the system for production-oriented release operations with channels, staged rollouts, rollback support, background update checks, and multiple update strategies.
|
|
48
|
+
- Wrote extensive documentation covering installation, APIs, migration, security, deployment, troubleshooting, and end-to-end usage.
|
|
49
|
+
- Built automated coverage across TypeScript, iOS, Android, and end-to-end testing layers to validate update lifecycle flows and failure scenarios.
|
|
50
|
+
- Positioned the product as an open-source alternative for teams that want more control, transparency, and flexibility in mobile update infrastructure.
|
|
51
|
+
|
|
52
|
+
## Portfolio Website Description
|
|
53
|
+
|
|
54
|
+
Native Update is a developer infrastructure product I built for Capacitor applications. It solves one of the biggest operational challenges in hybrid mobile apps: shipping updates safely, quickly, and with less dependency on slow release cycles. The platform combines OTA updates for web assets, native app update guidance, in-app review requests, background update scheduling, release channels, rollback support, security validation, CLI tooling, and a web dashboard. It is designed for teams that want a modern, open-source, security-conscious update workflow across iOS and Android.
|
|
55
|
+
|
|
56
|
+
## LinkedIn Profile Description
|
|
57
|
+
|
|
58
|
+
Creator of **Native Update**, an open-source Capacitor update platform for OTA delivery, native app store updates, in-app reviews, secure bundle signing, rollout control, analytics-ready release workflows, and dashboard-driven update management.
|
|
59
|
+
|
|
60
|
+
## Vision
|
|
61
|
+
|
|
62
|
+
To make modern mobile update infrastructure accessible, open, secure, and practical for every Capacitor developer, from solo builders to growing product teams.
|
|
63
|
+
|
|
64
|
+
## Mission
|
|
65
|
+
|
|
66
|
+
To remove the operational complexity of shipping updates across hybrid mobile apps by providing one unified system for update delivery, release control, app version guidance, review collection, and developer tooling.
|
|
67
|
+
|
|
68
|
+
## Problem It Solves
|
|
69
|
+
|
|
70
|
+
Capacitor developers often face a fragmented update workflow:
|
|
71
|
+
|
|
72
|
+
- OTA updates may require custom infrastructure or expensive third-party services.
|
|
73
|
+
- Native app store updates are handled separately from web asset updates.
|
|
74
|
+
- Review prompts are often implemented as one-off logic without reusable strategy.
|
|
75
|
+
- Security around bundle delivery, signatures, and validation is easy to get wrong.
|
|
76
|
+
- Release teams need rollout control, channels, rollback logic, and visibility into the update process.
|
|
77
|
+
|
|
78
|
+
Native Update solves this by bringing these concerns into one coordinated product.
|
|
79
|
+
|
|
80
|
+
## Core Product Value
|
|
81
|
+
|
|
82
|
+
Native Update delivers value at multiple levels:
|
|
83
|
+
|
|
84
|
+
- **Speed:** Faster bug fixes and content changes through OTA delivery.
|
|
85
|
+
- **Control:** Better release discipline with channels, staged rollout concepts, and rollback support.
|
|
86
|
+
- **Security:** Stronger trust with signing, checksums, HTTPS enforcement, and validation layers.
|
|
87
|
+
- **Experience:** Smoother app update prompts and in-app review flows.
|
|
88
|
+
- **Productivity:** CLI tools, examples, docs, and a dashboard reduce implementation overhead.
|
|
89
|
+
- **Ownership:** Open-source approach and self-controlled infrastructure options reduce platform lock-in.
|
|
90
|
+
|
|
91
|
+
## What The Project Includes
|
|
92
|
+
|
|
93
|
+
### 1. OTA / Live Updates
|
|
94
|
+
|
|
95
|
+
- JavaScript, HTML, and CSS update delivery
|
|
96
|
+
- Multiple update strategies: immediate, background, manual
|
|
97
|
+
- Delta update support
|
|
98
|
+
- Version management
|
|
99
|
+
- Automatic rollback patterns
|
|
100
|
+
- Update channels such as development, staging, and production
|
|
101
|
+
- Progress tracking and event listeners
|
|
102
|
+
|
|
103
|
+
### 2. Native App Updates
|
|
104
|
+
|
|
105
|
+
- App version check flows
|
|
106
|
+
- Immediate and flexible update modes
|
|
107
|
+
- Store-aware logic for Android and iOS
|
|
108
|
+
- Direct app store navigation support
|
|
109
|
+
- Version priority and minimum-version handling
|
|
110
|
+
|
|
111
|
+
### 3. In-App Reviews
|
|
112
|
+
|
|
113
|
+
- Native review prompt integration
|
|
114
|
+
- Smart timing concepts
|
|
115
|
+
- Rate limiting
|
|
116
|
+
- Platform-specific review handling for iOS and Android
|
|
117
|
+
- Fallback handling for web environments
|
|
118
|
+
|
|
119
|
+
### 4. Background Updates
|
|
120
|
+
|
|
121
|
+
- Background update checks
|
|
122
|
+
- Native notification support
|
|
123
|
+
- Battery-aware scheduling controls
|
|
124
|
+
- Cross-platform background update architecture
|
|
125
|
+
|
|
126
|
+
### 5. Security Tooling
|
|
127
|
+
|
|
128
|
+
- Bundle signing workflow
|
|
129
|
+
- Public/private key generation
|
|
130
|
+
- Checksum validation
|
|
131
|
+
- Signature verification
|
|
132
|
+
- Certificate pinning support
|
|
133
|
+
- HTTPS-only security posture
|
|
134
|
+
|
|
135
|
+
### 6. Developer Tooling
|
|
136
|
+
|
|
137
|
+
- CLI commands for initialization and release workflows
|
|
138
|
+
- Included command surface such as `init`, `bundle-create`, `bundle-sign`, `bundle-verify`, `keys-generate`, `backend-create`, `server-start`, and `monitor`
|
|
139
|
+
- Bundle creation utilities
|
|
140
|
+
- Bundle verification tooling
|
|
141
|
+
- Local server tooling
|
|
142
|
+
- Monitoring command support
|
|
143
|
+
|
|
144
|
+
### 7. Dashboard and Platform Layer
|
|
145
|
+
|
|
146
|
+
- App management
|
|
147
|
+
- Build upload flows
|
|
148
|
+
- Channel configuration
|
|
149
|
+
- Rollout control
|
|
150
|
+
- Analytics-oriented management layer
|
|
151
|
+
- Google Drive integration
|
|
152
|
+
- Configuration generation for easier setup
|
|
153
|
+
|
|
154
|
+
### 8. Documentation and Examples
|
|
155
|
+
|
|
156
|
+
- Installation and quick-start guides
|
|
157
|
+
- API references
|
|
158
|
+
- Security and deployment guides
|
|
159
|
+
- Migration documentation
|
|
160
|
+
- Troubleshooting material
|
|
161
|
+
- Example apps and backend templates
|
|
162
|
+
|
|
163
|
+
## Technical Highlights
|
|
164
|
+
|
|
165
|
+
- **Frontend / Platform:** Capacitor, TypeScript, web-compatible plugin layer
|
|
166
|
+
- **Native iOS:** Swift
|
|
167
|
+
- **Native Android:** Kotlin
|
|
168
|
+
- **CLI / Tooling:** Node.js-based command-line utilities
|
|
169
|
+
- **Dashboard Website:** React, Vite, TypeScript, Firebase, Google integration
|
|
170
|
+
- **Testing:** Vitest, XCTest, JUnit/Kotlin tests, end-to-end test coverage
|
|
171
|
+
- **Architecture Style:** Modular plugin system with feature-specific domains for live updates, app updates, reviews, background tasks, security, and Firestore-backed manifests
|
|
172
|
+
|
|
173
|
+
## Architecture Strengths
|
|
174
|
+
|
|
175
|
+
- Clear separation between live update logic, app update logic, review logic, background scheduling, and security layers
|
|
176
|
+
- Support for both plugin consumers and platform operators
|
|
177
|
+
- Strong documentation footprint for onboarding and maintenance
|
|
178
|
+
- Practical delivery model with example backends and example apps
|
|
179
|
+
- Designed for real release workflows instead of only simple code demos
|
|
180
|
+
|
|
181
|
+
## Proof Points Visible In The Repository
|
|
182
|
+
|
|
183
|
+
- Native iOS and Android implementation directories are present and populated
|
|
184
|
+
- A CLI package exists with multiple release-oriented commands
|
|
185
|
+
- The repo contains website/dashboard pages, admin views, and dashboard views
|
|
186
|
+
- Example apps exist for React + Capacitor, Node + Express, and Firebase
|
|
187
|
+
- Feature docs, API docs, security docs, migration docs, and testing docs are present
|
|
188
|
+
- Source tree includes modules for live updates, app updates, app reviews, background updates, core infrastructure, security, and Firestore integration
|
|
189
|
+
- The repository includes automated tests across TypeScript, iOS, Android, and E2E flows
|
|
190
|
+
|
|
191
|
+
## Why This Project Stands Out
|
|
192
|
+
|
|
193
|
+
- It treats updates as a platform problem, not just a plugin method call.
|
|
194
|
+
- It combines product, infrastructure, security, and developer experience in one repo.
|
|
195
|
+
- It supports both immediate developer adoption and future platform expansion.
|
|
196
|
+
- It is open-source, which increases trust, inspectability, and adaptability.
|
|
197
|
+
- It is especially relevant for hybrid app teams that need fast iteration without losing control over release quality.
|
|
198
|
+
|
|
199
|
+
## Underrated / Hidden Strengths
|
|
200
|
+
|
|
201
|
+
- The project is usable as both a package and a portfolio-grade product ecosystem.
|
|
202
|
+
- The presence of example backends lowers the barrier to real-world adoption.
|
|
203
|
+
- The dashboard direction makes the project stronger than a typical library-only release.
|
|
204
|
+
- Security tooling is built into the story, which improves credibility with serious teams.
|
|
205
|
+
- The combination of update delivery and review prompting ties technical operations to growth outcomes.
|
|
206
|
+
- The project creates multiple content angles: engineering, DevTools, mobile delivery, open source, security, release management, and product growth.
|
|
207
|
+
|
|
208
|
+
## Target Users
|
|
209
|
+
|
|
210
|
+
- Capacitor developers
|
|
211
|
+
- Hybrid mobile app teams
|
|
212
|
+
- Startups shipping mobile products
|
|
213
|
+
- Agencies building cross-platform apps for clients
|
|
214
|
+
- Developers migrating from fragmented update workflows
|
|
215
|
+
- Teams that want more control than closed managed services offer
|
|
216
|
+
|
|
217
|
+
## Ideal Use Cases
|
|
218
|
+
|
|
219
|
+
- Rapid bug-fix releases without full app store delay
|
|
220
|
+
- Controlled staged rollouts across dev, staging, and production
|
|
221
|
+
- Secure update delivery for mobile products
|
|
222
|
+
- Managing both OTA and native version updates from one system
|
|
223
|
+
- Improving app ratings with better-timed native review prompts
|
|
224
|
+
- Giving product teams a dashboard for release operations
|
|
225
|
+
|
|
226
|
+
## User Benefits
|
|
227
|
+
|
|
228
|
+
- Faster delivery of fixes and improvements
|
|
229
|
+
- Reduced user friction during app update flows
|
|
230
|
+
- Better app stability through rollback-aware design
|
|
231
|
+
- More confidence in update authenticity and bundle integrity
|
|
232
|
+
- Easier setup through docs, examples, and CLI support
|
|
233
|
+
- Better lifecycle control across development, testing, and production environments
|
|
234
|
+
|
|
235
|
+
## Business Benefits
|
|
236
|
+
|
|
237
|
+
- Reduced time-to-fix for production issues
|
|
238
|
+
- Better release confidence and governance
|
|
239
|
+
- Lower reliance on manual update handling
|
|
240
|
+
- Improved retention potential through smoother app maintenance
|
|
241
|
+
- Better app store growth potential through review-request tooling
|
|
242
|
+
- Stronger technical credibility for teams using a secure, documented update workflow
|
|
243
|
+
|
|
244
|
+
## Web, Mobile, and Platform Scope
|
|
245
|
+
|
|
246
|
+
### Current Scope
|
|
247
|
+
|
|
248
|
+
- **Mobile:** Strong core focus through Capacitor plugin support for Android and iOS
|
|
249
|
+
- **Web:** Dashboard, docs website, and web fallback behavior
|
|
250
|
+
- **CLI / DevTools:** Local developer tooling and release operations support
|
|
251
|
+
|
|
252
|
+
### Future Expansion Potential
|
|
253
|
+
|
|
254
|
+
- Multi-tenant SaaS management
|
|
255
|
+
- Enterprise SSO
|
|
256
|
+
- Advanced rollout strategies
|
|
257
|
+
- A/B testing for update delivery
|
|
258
|
+
- More framework examples and adapters
|
|
259
|
+
- CI/CD templates and deeper automation
|
|
260
|
+
- Larger self-service release operations platform
|
|
261
|
+
|
|
262
|
+
## Best Angles To Market This Project
|
|
263
|
+
|
|
264
|
+
- Open-source alternative in mobile update infrastructure
|
|
265
|
+
- Full-stack product built from plugin layer to dashboard layer
|
|
266
|
+
- Security-first OTA workflow for Capacitor
|
|
267
|
+
- Developer tooling project with real operational value
|
|
268
|
+
- Release-management system for hybrid apps
|
|
269
|
+
- Productized engineering project with ecosystem thinking
|
|
270
|
+
|
|
271
|
+
## Best Talking Points For Interviews, Portfolio, and Profiles
|
|
272
|
+
|
|
273
|
+
- I built an end-to-end update management ecosystem rather than a single isolated feature.
|
|
274
|
+
- I worked across TypeScript, Swift, Kotlin, CLI tooling, dashboards, docs, and release workflows.
|
|
275
|
+
- I focused on both engineering depth and product usability.
|
|
276
|
+
- I designed for real adoption by including examples, docs, tooling, and management interfaces.
|
|
277
|
+
- I addressed both technical reliability and business outcomes like speed, user trust, and app growth.
|
|
278
|
+
|
|
279
|
+
## Suggested Portfolio Tags
|
|
280
|
+
|
|
281
|
+
- Capacitor
|
|
282
|
+
- TypeScript
|
|
283
|
+
- Swift
|
|
284
|
+
- Kotlin
|
|
285
|
+
- React
|
|
286
|
+
- Vite
|
|
287
|
+
- Firebase
|
|
288
|
+
- Google Drive Integration
|
|
289
|
+
- OTA Updates
|
|
290
|
+
- Mobile DevTools
|
|
291
|
+
- Open Source
|
|
292
|
+
- Developer Platform
|
|
293
|
+
- Mobile Infrastructure
|
|
294
|
+
- Release Management
|
|
295
|
+
- App Store Optimization
|
|
296
|
+
|
|
297
|
+
## SEO Pack
|
|
298
|
+
|
|
299
|
+
### Primary SEO Keywords
|
|
300
|
+
|
|
301
|
+
- Capacitor OTA updates
|
|
302
|
+
- Capacitor native update plugin
|
|
303
|
+
- Capacitor app updates
|
|
304
|
+
- Capacitor in-app review plugin
|
|
305
|
+
- OTA update platform for Capacitor
|
|
306
|
+
- hybrid app update management
|
|
307
|
+
- mobile app release management
|
|
308
|
+
- secure OTA updates for mobile apps
|
|
309
|
+
- Capacitor rollout management
|
|
310
|
+
- open source mobile update platform
|
|
311
|
+
|
|
312
|
+
### Secondary SEO Keywords
|
|
313
|
+
|
|
314
|
+
- Swift Kotlin Capacitor plugin
|
|
315
|
+
- app store update workflow
|
|
316
|
+
- bundle signing for mobile apps
|
|
317
|
+
- checksum verification for app updates
|
|
318
|
+
- certificate pinning update delivery
|
|
319
|
+
- Capacitor developer tools
|
|
320
|
+
- Capacitor dashboard
|
|
321
|
+
- Firebase Google Drive update backend
|
|
322
|
+
- mobile update CLI
|
|
323
|
+
- CodePush alternative for Capacitor
|
|
324
|
+
|
|
325
|
+
### Suggested SEO Title
|
|
326
|
+
|
|
327
|
+
Native Update - Open-Source Capacitor OTA, App Update, and Review Platform
|
|
328
|
+
|
|
329
|
+
### Suggested SEO Meta Description
|
|
330
|
+
|
|
331
|
+
Native Update is an open-source Capacitor platform for OTA updates, app store update flows, in-app reviews, secure bundle delivery, rollout control, CLI tooling, and dashboard-based release management.
|
|
332
|
+
|
|
333
|
+
### Suggested OG / Social Title
|
|
334
|
+
|
|
335
|
+
Native Update: Complete Update Infrastructure for Capacitor Apps
|
|
336
|
+
|
|
337
|
+
### Suggested OG / Social Description
|
|
338
|
+
|
|
339
|
+
An open-source update platform for Capacitor apps with OTA delivery, native app updates, in-app reviews, security tooling, dashboard management, and developer-friendly release workflows.
|
|
340
|
+
|
|
341
|
+
### Suggested URL Slug
|
|
342
|
+
|
|
343
|
+
`native-update-capacitor-update-platform`
|
|
344
|
+
|
|
345
|
+
## Social Content Hooks
|
|
346
|
+
|
|
347
|
+
- Building a complete update platform for Capacitor instead of a single plugin
|
|
348
|
+
- Why OTA updates need security, rollback logic, and release discipline
|
|
349
|
+
- How Native Update combines app store updates and web asset updates in one system
|
|
350
|
+
- Why open-source mobile infrastructure matters
|
|
351
|
+
- The engineering challenge of unifying TypeScript, Swift, Kotlin, CLI, and dashboard workflows
|
|
352
|
+
- How developer tools can directly improve product velocity
|
|
353
|
+
- What makes Native Update a practical alternative to fragmented update stacks
|
|
354
|
+
- Lessons from building docs, examples, and management tooling around one package
|
|
355
|
+
|
|
356
|
+
## Content Themes For Future Posts
|
|
357
|
+
|
|
358
|
+
- Product launch posts
|
|
359
|
+
- feature breakdown posts
|
|
360
|
+
- architecture deep dives
|
|
361
|
+
- security-focused posts
|
|
362
|
+
- open-source journey posts
|
|
363
|
+
- developer experience posts
|
|
364
|
+
- roadmap posts
|
|
365
|
+
- behind-the-scenes build logs
|
|
366
|
+
- dashboard showcase posts
|
|
367
|
+
- migration and comparison posts
|
|
368
|
+
|
|
369
|
+
## Social Proof / Credibility Points
|
|
370
|
+
|
|
371
|
+
- Open-source MIT-licensed project
|
|
372
|
+
- Cross-platform implementation
|
|
373
|
+
- Dedicated website and dashboard presence
|
|
374
|
+
- Example apps and backend templates
|
|
375
|
+
- CLI tooling for real release workflows
|
|
376
|
+
- Security-focused update verification story
|
|
377
|
+
- Broad documentation coverage
|
|
378
|
+
- Multi-layer testing strategy
|
|
379
|
+
|
|
380
|
+
## 20 Recommended Hashtags
|
|
381
|
+
|
|
382
|
+
#CapacitorJS
|
|
383
|
+
#CapacitorPlugin
|
|
384
|
+
#MobileDevelopment
|
|
385
|
+
#AppUpdates
|
|
386
|
+
#OTAUpdates
|
|
387
|
+
#OpenSource
|
|
388
|
+
#TypeScript
|
|
389
|
+
#AndroidDevelopment
|
|
390
|
+
#iOSDevelopment
|
|
391
|
+
#SwiftLang
|
|
392
|
+
#KotlinAndroid
|
|
393
|
+
#HybridApps
|
|
394
|
+
#DeveloperTools
|
|
395
|
+
#SaaS
|
|
396
|
+
#Firebase
|
|
397
|
+
#ReleaseManagement
|
|
398
|
+
#AppStoreOptimization
|
|
399
|
+
#SoftwareEngineering
|
|
400
|
+
#BuildInPublic
|
|
401
|
+
#IndieHackers
|
|
402
|
+
|
|
403
|
+
## Generic Hashtags Provided By Project Owner
|
|
404
|
+
|
|
405
|
+
#Aoneahsan
|
|
406
|
+
#AhsanMahmood
|
|
407
|
+
#Zaions
|
|
408
|
+
#BestOpenSourceCommunityProject
|
|
409
|
+
#TopFree
|
|
410
|
+
#SaaSApp
|
|
411
|
+
|
|
412
|
+
## Recommended Hashtag Mix Strategy
|
|
413
|
+
|
|
414
|
+
- Use 3 to 6 broad hashtags from the recommended list.
|
|
415
|
+
- Add the 6 owner-branded hashtags when the post is personal-brand focused.
|
|
416
|
+
- Rotate hashtags based on audience: developer, startup, mobile, open-source, or product-building.
|
|
417
|
+
- Avoid stuffing all hashtags into every post; keep them relevant to the post angle.
|
|
418
|
+
|
|
419
|
+
## Suggested Profile / Resume Headline Variants
|
|
420
|
+
|
|
421
|
+
- Building Native Update, an open-source Capacitor update platform for OTA delivery, app updates, and in-app reviews
|
|
422
|
+
- Creator of Native Update: secure OTA and release-management infrastructure for Capacitor apps
|
|
423
|
+
- Full-stack engineer behind Native Update, a developer platform for hybrid mobile update workflows
|
|
424
|
+
- Open-source builder creating update infrastructure, release tooling, and dashboard workflows for Capacitor teams
|
|
425
|
+
|
|
426
|
+
## Suggested Project Categories
|
|
427
|
+
|
|
428
|
+
- Developer Tools
|
|
429
|
+
- Mobile Infrastructure
|
|
430
|
+
- Open Source SaaS
|
|
431
|
+
- Release Engineering
|
|
432
|
+
- App Operations
|
|
433
|
+
- Product Engineering
|
|
434
|
+
|
|
435
|
+
## Suggested Cautions For Future Content
|
|
436
|
+
|
|
437
|
+
- Do not present roadmap items as already shipped features.
|
|
438
|
+
- If a post references current project status, verify it against the latest repo state first.
|
|
439
|
+
- If metrics such as installs, users, stars, revenue, or active deployments are not verified, do not invent them.
|
|
440
|
+
- When comparing to other tools, focus on positioning and architecture rather than unsupported superiority claims.
|
|
441
|
+
|
|
442
|
+
## Weekly Maintenance Rule For This File
|
|
443
|
+
|
|
444
|
+
- Update this file every week when the project is active.
|
|
445
|
+
- Keep the filename date current.
|
|
446
|
+
- Update the `Reference Date`, `Last Updated`, and `Update History`.
|
|
447
|
+
- Keep only the latest 10 history entries in this file.
|
|
448
|
+
- Revise positioning, shipped features, roadmap notes, and SEO metadata when the project changes.
|
|
449
|
+
|
|
450
|
+
## Update History
|
|
451
|
+
|
|
452
|
+
| Date | Summary |
|
|
453
|
+
|------|---------|
|
|
454
|
+
| 2026-03-16 | Initial detailed portfolio, resume, SEO, and social-content project profile created from repository review. |
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
# Native Update - Capacitor Update Platform Project Profile
|
|
2
|
+
|
|
3
|
+
## Document Metadata
|
|
4
|
+
|
|
5
|
+
- **Project Name:** Native Update
|
|
6
|
+
- **Project Type:** Open-source Capacitor plugin + update management platform
|
|
7
|
+
- **Primary Domain:** Mobile app infrastructure / developer tooling / OTA delivery
|
|
8
|
+
- **Owner / Creator:** Ahsan Mahmood
|
|
9
|
+
- **Primary Contact:** aoneahsan@gmail.com
|
|
10
|
+
- **Package Name:** `native-update`
|
|
11
|
+
- **Current Package Version Reference:** `1.4.9`
|
|
12
|
+
- **License:** MIT
|
|
13
|
+
- **Primary Website:** `https://nativeupdate.aoneahsan.com`
|
|
14
|
+
- **Reference Date:** 2026-03-24
|
|
15
|
+
- **Last Updated:** 2026-03-24
|
|
16
|
+
- **Filename Rule:** Always keep `last-updated-YYYY-MM-DD` in the filename
|
|
17
|
+
- **Status Reference:** This profile reflects the repository state visible on 2026-03-24 from package metadata, source layout, docs, tests, dashboard docs, and example apps.
|
|
18
|
+
|
|
19
|
+
## Verification Snapshot
|
|
20
|
+
|
|
21
|
+
- **Tests:** `yarn test --run` passed with 81 tests
|
|
22
|
+
- **Build:** `yarn build` passed
|
|
23
|
+
- **Known Warning:** Node `DEP0169` deprecation warnings surfaced during Yarn/build execution
|
|
24
|
+
|
|
25
|
+
## Executive Summary
|
|
26
|
+
|
|
27
|
+
Native Update is a full update-management solution for Capacitor apps that combines over-the-air web asset updates, native app store update flows, in-app review prompts, background update checks, security tooling, CLI utilities, example backends, and a web dashboard into one ecosystem. The project is positioned as both a reusable plugin and a broader release-operations platform for hybrid mobile products.
|
|
28
|
+
|
|
29
|
+
## Current Positioning
|
|
30
|
+
|
|
31
|
+
Native Update helps Capacitor teams ship fixes faster, manage native store updates more intelligently, improve review prompting, and centralize release operations through a dashboard-driven workflow. It is stronger than a simple plugin because it includes the operational layer around updates, not just device APIs.
|
|
32
|
+
|
|
33
|
+
## Core Product Value
|
|
34
|
+
|
|
35
|
+
- **Speed:** OTA delivery for faster fixes and content changes
|
|
36
|
+
- **Control:** Channels, rollout concepts, rollback support, and update strategy choices
|
|
37
|
+
- **Security:** Signing, checksums, HTTPS posture, and validation tooling
|
|
38
|
+
- **Productivity:** CLI tooling, docs, examples, and dashboard support
|
|
39
|
+
- **Ownership:** Open-source and self-controlled infrastructure options
|
|
40
|
+
|
|
41
|
+
## Proof Points In Current Repo State
|
|
42
|
+
|
|
43
|
+
- Native Android and iOS implementations are present
|
|
44
|
+
- CLI package is present
|
|
45
|
+
- Example apps exist under `example-apps/`
|
|
46
|
+
- Website/dashboard project exists under `website/`
|
|
47
|
+
- Security, migration, production-readiness, and API docs are present
|
|
48
|
+
- Current automated package verification passed on 2026-03-24
|
|
49
|
+
|
|
50
|
+
## Resume / CV Summary
|
|
51
|
+
|
|
52
|
+
Built **Native Update**, an open-source Capacitor update platform that unifies OTA delivery, native app updates, in-app reviews, signing and verification, release tooling, example backends, and dashboard-driven update operations for hybrid mobile apps.
|
|
53
|
+
|
|
54
|
+
## Resume-Ready Achievement Bullets
|
|
55
|
+
|
|
56
|
+
- Built an open-source Capacitor update platform combining OTA updates, app store update flows, and in-app reviews in one developer-facing package.
|
|
57
|
+
- Implemented cross-platform native support alongside TypeScript APIs, CLI tooling, example backends, and a dashboard-oriented product layer.
|
|
58
|
+
- Added security-focused update delivery features including checksum validation, signature verification, and release workflow tooling.
|
|
59
|
+
- Structured the project around operational update management, not only plugin methods, with docs and examples for real adoption.
|
|
60
|
+
|
|
61
|
+
## Update History
|
|
62
|
+
|
|
63
|
+
| Date | Type | Notes |
|
|
64
|
+
| --- | --- | --- |
|
|
65
|
+
| 2026-03-24 | Refreshed | Updated metadata, verification snapshot, and repo-state summary to match current package state. |
|
|
66
|
+
| 2026-03-16 | Previous | Prior project profile version. |
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# Native Update - Capacitor Update Platform Project Profile
|
|
2
|
+
|
|
3
|
+
## Document Metadata
|
|
4
|
+
|
|
5
|
+
- **Project Name:** Native Update
|
|
6
|
+
- **Project Type:** Open-source Capacitor plugin + update management platform
|
|
7
|
+
- **Primary Domain:** Mobile app infrastructure / developer tooling / OTA delivery
|
|
8
|
+
- **Owner / Creator:** Ahsan Mahmood
|
|
9
|
+
- **Primary Contact:** aoneahsan@gmail.com
|
|
10
|
+
- **Package Name:** `native-update`
|
|
11
|
+
- **Current Package Version Reference:** `1.4.9`
|
|
12
|
+
- **License:** MIT
|
|
13
|
+
- **Primary Website:** `https://nativeupdate.aoneahsan.com`
|
|
14
|
+
- **Reference Date:** 2026-03-25
|
|
15
|
+
- **Last Updated:** 2026-03-25
|
|
16
|
+
- **Filename Rule:** Always keep `last-updated-YYYY-MM-DD` in the filename
|
|
17
|
+
- **Status Reference:** This profile reflects the repository state visible on 2026-03-25 from package metadata, source layout, docs, tests, dashboard docs, and example apps.
|
|
18
|
+
|
|
19
|
+
## Verification Snapshot
|
|
20
|
+
|
|
21
|
+
- **Tests:** `yarn test:run` passed with 81 tests
|
|
22
|
+
- **Build:** `yarn build` passed
|
|
23
|
+
- **Remediation:** Root package manager standardized on Yarn-only commands, with npm and pnpm removed from the root package path
|
|
24
|
+
|
|
25
|
+
## Executive Summary
|
|
26
|
+
|
|
27
|
+
Native Update is a full update-management solution for Capacitor apps that combines over-the-air web asset updates, native app store update flows, in-app review prompts, background update checks, security tooling, CLI utilities, example backends, and a web dashboard into one ecosystem. The project is positioned as both a reusable plugin and a broader release-operations platform for hybrid mobile products.
|
|
28
|
+
|
|
29
|
+
## Current Positioning
|
|
30
|
+
|
|
31
|
+
Native Update helps Capacitor teams ship fixes faster, manage native store updates more intelligently, improve review prompting, and centralize release operations through a dashboard-driven workflow. It is stronger than a simple plugin because it includes the operational layer around updates, not just device APIs.
|
|
32
|
+
|
|
33
|
+
## Core Product Value
|
|
34
|
+
|
|
35
|
+
- **Speed:** OTA delivery for faster fixes and content changes
|
|
36
|
+
- **Control:** Channels, rollout concepts, rollback support, and update strategy choices
|
|
37
|
+
- **Security:** Signing, checksums, HTTPS posture, and validation tooling
|
|
38
|
+
- **Productivity:** CLI tooling, docs, examples, and dashboard support
|
|
39
|
+
- **Ownership:** Open-source and self-controlled infrastructure options
|
|
40
|
+
|
|
41
|
+
## Proof Points In Current Repo State
|
|
42
|
+
|
|
43
|
+
- Native Android and iOS implementations are present
|
|
44
|
+
- CLI package is present
|
|
45
|
+
- Example apps exist under `example-apps/`
|
|
46
|
+
- Website/dashboard project exists under `website/`
|
|
47
|
+
- Security, migration, production-readiness, and API docs are present
|
|
48
|
+
- Current automated package verification passed cleanly on 2026-03-25
|
|
49
|
+
|
|
50
|
+
## Resume / CV Summary
|
|
51
|
+
|
|
52
|
+
Built **Native Update**, an open-source Capacitor update platform that unifies OTA delivery, native app updates, in-app reviews, signing and verification, release tooling, example backends, and dashboard-driven update operations for hybrid mobile apps.
|
|
53
|
+
|
|
54
|
+
## Resume-Ready Achievement Bullets
|
|
55
|
+
|
|
56
|
+
- Built an open-source Capacitor update platform combining OTA updates, app store update flows, and in-app reviews in one developer-facing package.
|
|
57
|
+
- Implemented cross-platform native support alongside TypeScript APIs, CLI tooling, example backends, and a dashboard-oriented product layer.
|
|
58
|
+
- Added security-focused update delivery features including checksum validation, signature verification, and release workflow tooling.
|
|
59
|
+
- Structured the project around operational update management, not only plugin methods, with docs and examples for real adoption.
|
|
60
|
+
|
|
61
|
+
## Update History
|
|
62
|
+
|
|
63
|
+
| Date | Type | Notes |
|
|
64
|
+
| --- | --- | --- |
|
|
65
|
+
| 2026-03-25 | Remediation | Updated verification snapshot to the Yarn-only root package workflow after removing npm and pnpm from the root package path. |
|
|
66
|
+
| 2026-03-24 | Refreshed | Updated metadata, verification snapshot, and repo-state summary to match current package state. |
|
|
67
|
+
| 2026-03-16 | Previous | Prior project profile version. |
|