My technical index

A growing index of the technology, tools and systems I've learned while building websites and apps with ChatGPT. 🩷.

I'm not a professional developer, but these are some of the technologies, tools and systems I've learned about and worked with while creating my websites and apps with the help of ChatGPT.

• HTML5 — structure for your web apps, tools and websites.

• CSS3 — responsive layouts, cards, animations, loaders and Blogger fixes.

• JavaScript — application logic, Firebase integration, converters, caching and UI behaviour.

• DOM manipulation — dynamically adding/removing/updating page elements.

• LocalStorage — local caching and persistent browser data.

• SessionStorage — including your protected-app verification session..

• JSON — configuration, manifests, feeds and structured application data.

• Blogger XML — editing and repairing Blogger themes.

• Blogger template expressions — conditional content and homepage/post logic.

• Blogger JSON feeds — dynamically retrieving Blogger pages/posts.

• Blogger infinite scrolling — fetching and inserting additional posts dynamically.

• Git — source/version-controlled projects.

• GitHub — repositories and project hosting.

• GitHub Pages — hosting your web apps and PWAs.

• GitHub Actions — automated Android build workflows.

• GitHub Actions Secrets — securely supplying sensitive build credentials.

• Fine-grained GitHub Personal Access Tokens — allowing your builder controlled access to private repositories/workflows.

• Private GitHub repositories — protecting your Android build infrastructure.

• YAML/YML — GitHub Actions workflow configuration.

• CI/CD concepts — automatically turning source/configuration into finished builds.

• Firebase — backend infrastructure for several of your applications.

• Firebase Authentication — registration, login, logout, password reset and email verification.

• Firebase Auth persistence — maintaining signed-in sessions.

• Cloud Firestore — storing user and application data.

• Firestore security rules — restricting users to authorised data.

• Firestore document/collection architecture — organising campaigns, budgets and settings.

• Firestore deleteField() — removing individual map fields without rewriting unnecessary data.

• Firestore read/write optimisation — reducing database operations and costs.

• Firebase Cloud Functions — secure server-side processing.

• Firebase Blaze — required infrastructure for your Cloud Functions/payment applications.

• Google Cloud budget alerts — cost monitoring.

• Firebase Auto Stop Services — protection against unexpected cloud costs.

• Stripe — payment processing.

• Stripe Checkout — hosted secure payment checkout.

• Stripe Connect — directing payments to connected fundraising accounts.

• Stripe application fees — implementing your GiftMe platform fee.

• Stripe webhooks — receiving payment events server-side.

• Stripe webhook secrets — verifying genuine Stripe events.

• Stripe secret API keys — server-side Stripe authentication.

• Progressive Web Apps (PWA) — installable website applications.

• Web App Manifest — PWA/application metadata.

• Service Workers — offline support, caching and your Android Builder's TWA detection.

• Cache Storage — PWA offline resources.

• PWA scope/start URLs — controlling application navigation.

• Unique PWA manifest IDs — preventing different installed apps conflicting.

• Bubblewrap — packaging web applications as Android apps.

• Trusted Web Activities (TWA) — presenting verified web content through Android/Chrome.

• Digital Asset Links — Google's Android ↔ website trust relationship for TWAs.

• assetlinks.json — Android website/app association.

• WebView — your Android Builder's fallback when a site doesn't have a service worker.

• Automatic TWA/WebView detection — your builder's decision system.

• Android application/package IDs — permanent identities such as com.example.app.

• Android version codes — identifying successive Android releases.

• Android version names — human-readable app versions.

• Android APKs — installable Android packages.

• Android App Bundles (AAB) — Google Play publishing packages.

• Android keystores — signing Android applications.

• Signing aliases — identifying signing keys inside a keystore.

• Keystore passwords/key passwords — protected signing credentials.

• Android app signing — maintaining update identity between releases.

• JDK/Java — required Android/Bubblewrap build tooling.

• Command Prompt — manually running Android/Bubblewrap tooling.

• npm/Node.js tooling — used by Bubblewrap and associated build tools.

• Google Play Console concepts — publishing and updating Android applications.

• Google Play package identity — matching Play Store releases to an existing application.

• Google Play listing URLs — including their id=package.name structure.

• Deep/launch URLs — passing information when an app opens a website.

• URL query parameters — including your vs_app launch value.

• Deterministic key generation — generating the same protection key from the same package ID.

• Client-side access guards — your custom Ventsharm App Launch Guard.

• App ↔ website launch-token handshake — matching the app's vs_app value against the website guard.

• Graceful access fallback — displaying the Google Play install/update screen when the guard doesn't match.

• Feature/update compatibility — preserving an established package→key algorithm so existing guards remain compatible.

• WebView/TWA fallback architecture — allowing one builder to support different types of websites.

• Responsive/mobile-first web design.

• CSS media queries.

• CSS animations and transitions.

• Glassmorphism UI.

• Dynamic loading overlays.

• Image loading/fade handling.

• SVG <use> elements — including fixing Chrome rendering issues.

• Mutation/dynamic-content handling — important for Blogger infinite scrolling and dynamically loaded images.

• Browser caching — including diagnosing old versions of websites/apps appearing cached.

• Offline web applications.

• Image conversion in the browser — JPG, PNG and WEBP.

• PDF generation/conversion concepts — including dimension-controlled book covers.

• Pixels, inches and centimetre conversion for image sizing.

• Stripe/Firebase frontend ↔ backend separation — keeping sensitive operations off the browser.

• Authentication vs authorisation — distinguishing being logged in from being allowed to access particular data.

• Client-side vs server-side security — particularly important with Firebase, Stripe and your app guard.

• API keys/secrets/tokens — understanding which credentials can be public and which must remain private.

• Webhooks vs ordinary API requests.

• Event-driven backend processing.

• Caching vs database synchronisation.

• Windows driver

•  installation/troubleshooting.

• Windows services/startup configuration.

• Intel graphics drivers.

• NVIDIA driver/services configuration.

• Windows ISO in-place upgrades.

• 32-bit/x86 Windows compatibility.

• Hardware/driver compatibility preservation.