Marketingtool-pro Phone App

Open-source Expo / React Native app for AI-powered marketing workflows on mobile.

Overview

Marketingtool-pro Phone App is the mobile client for the Marketingtool-pro platform. It combines Appwrite for core authentication and account data with Firebase for AI flows, observability, and hosting-related services.

Highlights

• Expo / React Native mobile application
• Hybrid backend architecture using Appwrite and Firebase
• Phone-number sign-in flow bridged into an Appwrite session
• AI-powered tool execution for marketing workflows
• Firebase App Check, Crashlytics, messaging, and analytics support
• GitHub Actions-based deployment automation

Architecture at a glance

Mobile app

• Entry points: App.tsx and src/navigation/AppNavigator.tsx
• Startup is staged so the splash screen remains visible while fonts, auth bootstrap, and Firebase App Check initialize
• Messaging, analytics, and crash reporting are deferred until after first layout to reduce cold-start regressions

Auth and data

• Appwrite is the primary backend for account and database operations
• Firebase Auth is used for phone OTP verification
• After Firebase verification, the app calls the Appwrite phone-session function to create the session used by the rest of the app

AI execution

• The app loads its tool catalog from src/data/tools.js
• src/services/aiService.ts prefers the Appwrite tool-executor function
• The client can fall back to web APIs hosted at app.marketingtool.pro
• The functions/ package contains Firebase Functions v2 + Genkit flows used by backend AI features

Backend packages

• functions/ — Firebase Functions v2 + Genkit + Firestore
• appwrite-functions/phone-session — Appwrite function for converting a verified Firebase Phone Auth UID into an Appwrite session

Repository structure

• src/ — app screens, navigation, services, state, and UI code
• functions/ — Firebase Functions and Genkit flows
• appwrite-functions/ — Appwrite backend functions
• assets/ — static app assets
• scripts/ — repository maintenance and deployment helpers
• docs/ — supporting documentation

Getting started

Prerequisites

• Node.js and npm
• Expo-compatible iOS, Android, or web environment
• Required Appwrite and Firebase configuration values

Install dependencies

npm ci

Run the app

npm start

Platform-specific commands:

npm run ios
npm run android
npm run web

Validate the project

npm run doctor
npx tsc --noEmit

Firebase Functions package

Install and build the functions package separately:

cd functions && npm ci
cd functions && npm run build
cd functions && npm run lint

Local serving commands:

cd functions && npm run serve
cd functions && npm run shell

Deployment

Production deployment is automated through GitHub Actions.

• Tagging a release as vX.Y.Z triggers the production deployment workflow
• Android builds are produced with EAS and submitted to Google Play
• Apple builds are produced with EAS and processed for App Store submission
• Web hosting deploys on merge to Master

Do not trigger EAS build or submission flows without explicit approval.

Local release verification flow (run only when shipping is approved):

git pull --rebase
git status

# Verify App Store Connect/IAP configuration
# Uses fastlane/Fastfile lane: ios test_iap_config
# Values from App Store Connect → Users and Access → Integrations
export ASC_KEY_ID=YOUR_KEY_ID
export ASC_ISSUER_ID=YOUR_ISSUER_ID
export ASC_KEY_PATH=~/secrets/AuthKey_YOUR_KEY_ID.p8
chmod 700 ~/secrets && chmod 600 "$ASC_KEY_PATH"
npm run iap:verify

# Build + auto-submit (both stores)
npm run ship:verified

# iOS-only (still verifies IAP configuration first)
npm run ship:verified:ios

Contributing

Contributions are welcome.

1. Fork the repository
2. Create a branch for your change
3. Make and test your updates
4. Open a pull request with a clear description

Please also review:

• Contributing Guidelines
• Code of Conduct
• Security Policy

Security

If you discover a security issue, please do not open a public issue. Follow the private reporting guidance in SECURITY.md.

License

This project is licensed under the MIT License.

Third-party dependencies

This project uses third-party open-source software, including:

• React Native (MIT)
• Expo SDK (MIT)
• Zustand (MIT)
• React Navigation (MIT)
• Appwrite SDK (BSD-3-Clause)
• Lottie React Native (Apache-2.0)

Full license details available at marketingtool.pro.

App screens

View the app screens →

Every screen of the phone app, as designed.

Project page

View the project page →

Tool UI blueprint

View the tool UI blueprint →

All three are served from this same GitHub Pages site, so they stay with the code rather than living in a download folder on one machine.

They are self-contained HTML exports. That format renders correctly here but NOT in the GitHub wiki, which only renders markup files (.md, .textile) — a bundled artifact posted there shows as escaped text or downloads instead of displaying. That is why these live on the site and the wiki links to them.

Further reading

• ARCHITECTURE.md — how the system actually fits together: the request path for a tool run on each platform, how Windmill authenticates, what runs on each VPS, and the environment traps worth knowing before you debug anything.
• MOBILE_TOOLS_POLICY.md — the rules the phone app must follow: same backend, models and execution logic as web; display may be shortened, nothing else.

---

Maintained by Marketingtool-pro