Remove Development Remove Software Engineering Remove Technical Cofounder Remove User Testing
article thumbnail

Common technical hiccups in your product analytics that are easy to spot

Mixpanel

The good news is that many technical quirks tend to follow certain patterns that can be easily spotted—even by non-engineers. Here are four technical hiccups associated with corrupt event tracking data, how to spot them, and what to do about them. As they say—garbage in, garbage out. Event stuttering. Disjoint event duplicates.

article thumbnail

Why it’s never too early to add product analytics to your app

Mixpanel

So it’s tempting to think the additional add-on of measuring user events in your code (i.e., implementing product analytics) is something that can wait until your team is bigger, until you have more users, or until you have more money. You know where users clicked and didn’t click, when they clicked, and in what order.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How to be the go-to engineer for product analytics

Mixpanel

As data-driven product development continues to balloon in popularity, so does the need for accurate and sophisticated implementation of analytics tracking in software products. Keep the product folks technically up-to-date. One of those niches that’s become more valuable in recent years: product analytics.

article thumbnail

Always implement analytics as part of feature development. Here’s why.

Mixpanel

Here are eight reasons you should always implement your analytics in the same sprint as your feature development and not at a separate time after development is complete. When engineers implement features, they write code. Analytics should be tested alongside features. Implementation is better with less context-switching.

article thumbnail

Data thinking vs. product thinking

Mixpanel

Data has fundamentally changed how we design and develop products, but there’s a difference between simply reacting to data points and applying the level of analytic rigor needed to yield meaningful results. There’s an enormous amount of ambiguity when it comes to developing products. Here’s how. But you’d be wrong.

article thumbnail

How to add analytics event tracking in SwiftUI (the elegant way)

Mixpanel

Rather than a UITableViewController with accompanying storyboard and custom UITableViewCell subclasses, all we need now is a binding to a list of tasks and 10-ish lines of actual code: struct TaskListView: View {. Use custom event initializers to reduce footprint. Use custom view modifiers for more logical grouping. onDrag {. }.onDrop