Apple App Analytics VS git-sizer

• Seamless Integration
  Apple App Analytics integrates directly with the App Store Connect, providing a seamless and straightforward user experience for developers to access data without needing additional third-party services.
• User Privacy
  The platform respects Apple's strong stance on user privacy, ensuring that developers receive valuable insights without compromising on user confidentiality.
• Rich Data Insights
  Developers can access comprehensive metrics including downloads, sales, app usage, retention rates, and user demographics to make informed decisions about app performance.
• Cohort Analysis
  Allows developers to track the behavior of specific groups of users over time, providing valuable insights on how cohorts engage with the app.
• Event Correlation
  Developers can view a timeline of events, such as app version updates or marketing campaigns, and correlate these with changes in metrics to better understand their impact.

Possible disadvantages

• Limited Cross-Platform Support
  Apple App Analytics is designed specifically for iOS applications, which may limit its use for developers looking to analyze cross-platform apps that include Android or web components.
• Delayed Data Updates
  Some users report that there's a delay in data availability, which can hinder real-time analysis and the ability to quickly respond to trends or issues.
• Lack of Custom Event Tracking
  The platform does not support custom event tracking, restricting developers from tracking specific in-app user interactions that are not predefined by Apple.
• Limited Integration with Third-Party Tools
  Compared to third-party analytics services, it has limited integration capabilities with other tools and services that developers might already be using in their analytics stack.
• Interface Complexity
  The interface may be complex for new users, with a learning curve required to fully utilize all features and extract insights effectively.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Apple App Analytics yet.

• Don't delete your replikas (yet)

  You know they do have app analytics right? Source: over 3 years ago

• Does WatchOS support Google ads tracking? So I can measure app installs via google ads campaigns.

  You can create unique links for the Google ad campaign and track it on Apple’s side. See https://developer.apple.com/app-store-connect/analytics/. Source: almost 5 years ago

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago