Add mixpanel events for submit app flow

[mdmohsin7]

Summary by CodeRabbit

• New Features

  • Enhanced analytics tracking for app submission processes, differentiating between public and private submissions.
  • Added tracking for user interactions on the "Submit App" and "App Submission Help" pages.

• Bug Fixes

  • Improved logic for tracking app submissions based on privacy settings.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve enhancements to the analytics tracking within the app submission process. The AddAppPage and AppsPage classes have been updated to include new import statements for MixpanelManager and to track specific user interactions, such as opening the app submission help page and the submit app page. Additionally, two new methods have been added to the MixpanelManager class to log events for private and public app submissions, allowing for more detailed analytics based on user privacy choices.

Changes

File Path	Change Summary
app/lib/pages/apps/add_app.dart	Added import for MixpanelManager. Integrated tracking for opening the app submission help page and enhanced tracking logic in onConfirm for app submissions based on privacy level.
app/lib/pages/apps/page.dart	Added import for MixpanelManager. Integrated tracking for opening the "Submit App" page.
app/lib/utils/analytics/mixpanel.dart	Added methods: privateAppSubmitted(Map<String, dynamic> properties) and publicAppSubmitted(Map<String, dynamic> properties) for tracking app submission events.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AppsPage
    participant MixpanelManager

    User->>AppsPage: Tap on "Submit App"
    AppsPage->>MixpanelManager: pageOpened('Submit App')
    
    User->>AddAppPage: Open App Submission Help
    AddAppPage->>MixpanelManager: pageOpened('App Submission Help')
    
    User->>AddAppPage: Confirm Submission
    AddAppPage->>MixpanelManager: privateAppSubmitted(appDetails) or publicAppSubmitted(appDetails)

Loading

🐰 "In the land where apps do play,
We track their steps both night and day.
With Mixpanel's help, we see them thrive,
Private or public, they come alive!
Hopping through submissions, oh what a sight,
Analytics dancing, everything feels right!" 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.