What is Reddit's opinion of
Mixpanel?
From 3.5 billion Reddit comments
81 reviews of this app found across Reddit:
Heres the adoption report from Mixpanel. They have the X at about 9% of iPhones and the two 8s combined at 12%. This time last year the two new 7s were combined for just over 25% of new iPhones. So the adoption of new iPhones has actually decreased. https://mixpanel.com/trends/#report/iphone_8_X
> As measured by the App Store on September 19, 2015.
Must be all those people downloading Peace. But seriously, someone who just upgraded iOS is more likely to visit the App Store. This puts it at 29% on September 19.
> He had 20 targets inside the 10 yard line in the red zone, and Diggs had 7. That’s scheme over talent, and Diggs can’t necessarily help that.
It's not just scheme over talent, because most schemes are based on their player's talents. The reason Adams gets so many RZ targets is largely because he's one of the best, if not the best, RZ WRs in the game. Diggs is not. Pretty simple to see - Diggs had 5 TDs on 16 RZ targets (and 3 on 7 in the 10). Adams had 14 TDs on 28 RZ targets (and 13 on 20 in the 10). Hypothetically if you gave Diggs the same amount of targets he would've had 8.75 RZ TDs and 8.6 inside the 10. Adams is simply much better inside the RZ, therefore he gets more targets.
> Adams ran more routes per game than Diggs did too.
Adams ran 5 less routes per game (464 routes/14 games to Diggs 611/16 games).
The running game thing is somewhat debunked at this point. Still, I'd consider their situations basically a wash.
Seems like a pretty decent gap to me, although I see where you're coming from. Definitely a viable opinion.
dont really appreciate the opt out links not being in the post itself
EDIT: https://mixpanel.com/optout/
I think it goes by IP
EDIT: From the new policy http://optout.networkadvertising.org/ http://optout.aboutads.info/
This gets posted a lot but it's worth pointing out that the Discord staff has repeatedly stated that they do not sell data. From DiscordDan:
>The gist is, perhaps unsurprisingly, that we collect information because it’s literally impossible to operate an internet service without collecting information. We are not in the business of selling data - we intend to sell customizables like stickers and skins directly to our users. We understand the whole “if you’re not paying, then you are the product” sentiment and that is not what’s going on here. We are a small startup that is working like crazy and just haven’t gotten around to implementing our store yet (e.g. this is one of the reasons we still call Discord an ‘Alpha’ version). So one example of how we use data is when you sign in to Discord we store your IP address so if you get banned from a server we prevent a user from creating a new account from the same IP to simply circumvent the ban and harass people. However we do intend to change this to use a hash of your IP so we don’t need to keep it around. Another thing we do is log what actions people take in Discord (like, join a server or invite a friend) so we can understand what features people are using and how we can make Discord more awesome. We mostly use https://mixpanel.com to do this but also have some data sent to google analytics.
I legitimately wonder if this is what forces a complete 180 on including it in iOS.
It definitely looks like a shallower adoption rate over 10 days after launch versus its predecessor.
Hey u/blef__ , love this! I really enjoyed the two articles in your newsletter that went out today that dug deeper into MDS. Adding here:
The Unspoken Gerrymandering of the Modern Data Stack
The Changing Face of the Data Stack
And a personal favorite – because it opens the door into diversity and inclusion:
According to mixpanel, 2 week in iOS11 is at 36%. So yeah, if there are at least 300 million iOS devices out there (which is a pretty safe bet IIRC), more than 100m are on 11.
Though note that iOS11 adoption is much slower than iOS10, which was at 34% a week in (10 was officially released on September 13).
As per mixpanel!, since the release of 8.1.3 - the adoption is growing at about twice as fast Vs early Jan'15.
At this rate, it should eventually catchup with iOS 7 adoption.
8.1.3 reduced the free space threshold and now many can update again without resorting to inconvenient work arounds (deleting stuff/iTunes).
Have you read their [privacy policy](https://mixpanel.com/legal/privacy-policy/? You are, basically, giving them away all your personal information (including email, passwords, credit card info, etc..). You should read the fine print...
https://mixpanel.com/trends/#report/android_os_adoption
Looks like the adoption rates are slightly improving. Maybe because more people are buying Android phones every year, so the overall percentage of new OS becomes higher? I still don't see a difference in carrier update frequencies.
Our official privacy policy is almost done. Sorry that it's taking so long, but you can rest assured that your privacy is utmost important to us as well as our transparency as a company. Hopefully this isn't TLDR
The privacy policy on our H&C site was written for our previous product, which was an iPad game called Fates Forever. We are currently writing a new one specifically for Discord. The gist is, perhaps unsurprisingly, that we collect information because it’s literally impossible to operate an internet service without collecting information. We are not in the business of selling data - we intend to sell customizables like stickers and skins directly to our users. We understand the whole “if you’re not paying, then you are the product” sentiment and that is not what’s going on here. We are a small startup that is working like crazy and just haven’t gotten around to implementing our store yet (e.g. this is one of the reasons we still call Discord an ‘Alpha’ version). So one example of how we use data is when you sign in to Discord we store your IP address so if you get banned from a server we prevent a user from creating a new account from the same IP to simply circumvent the ban and harass people. However we do intend to change this to use a hash of your IP so we don’t need to keep it around. Another thing we do is log what actions people take in Discord (like, join a server or invite a friend) so we can understand what features people are using and how we can make Discord more awesome. We mostly use https://mixpanel.com to do this but also have some data sent to google analytics.
Yes, but Mixpanel do.
>Anonymous statistics of usage
>
>Paste collects anonymous and aggregated statistics of application usage utilizing Mixpanel in compliance with Mixpanel privacy policy.
Yup.
~900 Million iOS devices, 55% on iOS 11
~500,000 r/Apple subscribers, and a thread about iOS 11 being shit at 8k upvotes
Looking at data on a quarter on basis is really quite idiotic. You want to look at several quarters in a row in order to really gauge performance.
Edit: Almost year over year data https://mixpanel.com/trends/#report/android_vs_ios/from_date:-346,to_date:-1
Dips and valleys... but mostly holding their ground.
Here's mixpanel's data: https://mixpanel.com/trends/#report/iphone_models/from_date:-1395,report_unit:month,to_date:0
I count 34% on 4.7" screens, vs 47% above. Though the mixpanel data excludes the iphone 6, which was 10% above. So....it's not a large difference?
Incidentally, pedometer++ is great with the apple watch. It has a "intelligently combine phone and watch steps" option.
Exactly. Achilles heel of Android is that the userbase is littered across OS versions.
For comparison, here’s iOS
As previously said. Nothing is stopping any developer or any app or extension from adding code at any point to spy on you. It's a risk you take with any software, the benefit here is that chrome extensions are open for all to read, so you'd be an idiot to try it.
Regarding the account I'd, have a read of the documentation: https://mixpanel.com/help/reference/javascript-full-api-reference
You'll see that once that library has been initialised, to send data you need to use mixpanel.library_name.track(...); Send anything
The existing players with tons of funding have pretty good buy-in with startups already. Here are a couple of them, I'm certainly missing at least a dozen form the list:
https://baremetrics.com/#pricing
https://mixpanel.com/pricing/
https://www.kissmetrics.com/pricing
They all have a plan that is affordable by a startup with some minimal revenue or funding.
You need a better differentiator than 'startups'. If your only differentiator is 'startups', I'd close up shop right now and find something else to work on.
Over 95% of iOS devices are running iOS7 or iOS8. Unless you have a really good reason to support iOS6 then I wouldn't bother.
https://mixpanel.com/trends/#report/ios_8/from_date:-29,report_unit:day,to_date:-1
No problem, some good questions.
In my company the high level KPIs are set at board level for the senior leadership teams and linked in with bonuses.
Heads of /Directors of product have generally defined North Star metrics for us. More here https://mixpanel.com/blog/north-star-metric/
Commercials = 💰
> The privacy policy on our H&C site was written for our previous product, which was an iPad game called Fates Forever. We are currently writing a new one specifically for Discord. The gist is, perhaps unsurprisingly, that we collect information because it’s literally impossible to operate an internet service without collecting information. We are not in the business of selling data - we intend to sell customizables like stickers and skins directly to our users. We understand the whole “if you’re not paying, then you are the product” sentiment and that is not what’s going on here. We are a small startup that is working like crazy and just haven’t gotten around to implementing our store yet (e.g. this is one of the reasons we still call Discord an ‘Alpha’ version). So one example of how we use data is when you sign in to Discord we store your IP address so if you get banned from a server we prevent a user from creating a new account from the same IP to simply circumvent the ban and harass people. However we do intend to change this to use a hash of your IP so we don’t need to keep it around. Another thing we do is log what actions people take in Discord (like, join a server or invite a friend) so we can understand what features people are using and how we can make Discord more awesome. We mostly use https://mixpanel.com to do this but also have some data sent to google analytics.
We won't be providing self-hosting any time soon. If you're worried about privacy
The gist is, perhaps unsurprisingly, that we collect information because it’s literally impossible to operate an internet service without collecting information. We are not in the business of selling data - we intend to sell customizables like stickers and skins directly to our users. We understand the whole “if you’re not paying, then you are the product” sentiment and that is not what’s going on here. We are a small startup that is working like crazy and just haven’t gotten around to implementing our store yet (e.g. this is one of the reasons we still call Discord an ‘Alpha’ version). So one example of how we use data is when you sign in to Discord we store your IP address so if you get banned from a server we prevent a user from creating a new account from the same IP to simply circumvent the ban and harass people. However we do intend to change this to use a hash of your IP so we don’t need to keep it around. Another thing we do is log what actions people take in Discord (like, join a server or invite a friend) so we can understand what features people are using and how we can make Discord more awesome. We mostly use https://mixpanel.com to do this but also have some data sent to google analytics.
Discord is 100% encrypted client to server. That means that every audio packet and every text message is sent through a secure connection between you and our server. No one can man in the middle it. We do not store or even inspect audio packets, but simply pass them around between people in the same channel. We DO store text messages on our server to allow for chat history so people can read messages they missed while offline.
> I feel like I'm kind of cheating by not considering K & L the latest two letter releases for December of this year, but I feel like since it Lollipop was released so recently it's acceptable to consider the latest two releases as J & K.
Lollipop source code was released on the 3rd of November, OTAs started on the 12th of November.
In contrast, iOS 8 was released on September 17th. iOS 7 / iOS 8 Betas had 95%+ install base at the release of iOS 8. By October 17th, iOS 8 had 48% install base. Today iOS 8 has 62%.
I know this is like Apple and Oranges to some extent, and they aren't completely comparable for many reasons. But there is still some value in comparing the two from a developer standpoint as well as from the users perspective.
Current numbers (in percentage):
5s: 31.52 5: 26.88 4s: 18.88 4: 11.31 5c: 10.86 6: 6.06 6+: 1.32 Older: 0.57
Looking at MixPanel's website, the images give me the impression they're making tools to sell to people who don't have credit cards.
Anyway, all the code in bitmapist is in the __init__.py file. Is everyone ok with this style? I thought it was just for package level setup but I do see some projects using it for all their code when the module in question is fairly small.
That extension appears to inject a hidden div containing mixpanel tracking code to every page one opens. I would be a little cautious about this extension, especially since the author does not mention adding this.
This isn't the article I was thinking of, but they link to other similar analysis (and discuss the various results) and then do their own; it appears to be from 2016.
Hello! CTO of Phantom here. Thanks for flagging your concerns. Just wanted to add to what u/brandon-phantom said.
As mentioned, the payload you shared is a standard Posthog payload, I believe Metamask uses Mixpanel (behind Segment), a similar product.
We use the data to create engagement metrics to see how the app is doing, but never to identify you. We actually don't want your IP address and will be turning that setting off in the next release :) Unfortunately it is on by default in Posthog.
Just wanted to explicitly mention that we are not tracking anything that would allow us to know your Solana address, but yes we do give you an anonymous user ID so that we can know how many users we have.
Takes 3 seconds on google to find dozens of articles to contradict the OP
To think an amazing run game doesn’t greatly help the passing game. You need to watch football.
All the Ycombinator people use mixpanel
It doesn’t give you the depth that GA gives you. It’s meant for you to setup your own important user actions and track those.
For example choosing the top 5 website actions you want your users to take, then tracking those actions, then doing A\B tests on those actions and optimizing them.
I would be curious to hear more about your GA privacy concerns. Tbh I assume all free analytics tools mine your data, so not sure you will find a robust alternative that doesn’t do that.
Super curious about your reasons for leaving GA
There was actually a pretty interesting article I read that running immediately before the pass isn't any likelier to make the pass more effective. In fact, there's reason to believe that running doesn't even help set up play action.
Meanwhile, over in the part of the industry where the manufacturer saves money on support costs when as many people as possible are on the latest rev...
https://mixpanel.com/trends/#report/ios_11/from_date:-16,report_unit:week,to_date:0
Not bad for what, a couple of weeks now?
Ironically, I read that out of curiosity - I wasn't suspicious about Discord itself - but now I am, lol.
Someone asked:
> "Will you use/sell my information? Thanks for the response."
and the response, in my view, is meant to deceive. It's long and full of tangents and doesn't once say "No.":
> The privacy policy on our H&C site was written for our previous product, which was an iPad game called Fates Forever. We are currently writing a new one specifically for Discord. The gist is, perhaps unsurprisingly, that we collect information because it’s literally impossible to operate an internet service without collecting information. We are not in the business of selling data - we intend to sell customizables like stickers and skins directly to our users. We understand the whole “if you’re not paying, then you are the product” sentiment and that is not what’s going on here. We are a small startup that is working like crazy and just haven’t gotten around to implementing our store yet (e.g. this is one of the reasons we still call Discord an ‘Alpha’ version). So one example of how we use data is when you sign in to Discord we store your IP address so if you get banned from a server we prevent a user from creating a new account from the same IP to simply circumvent the ban and harass people. However we do intend to change this to use a hash of your IP so we don’t need to keep it around. Another thing we do is log what actions people take in Discord (like, join a server or invite a friend) so we can understand what features people are using and how we can make Discord more awesome. We mostly use https://mixpanel.com to do this but also have some data sent to google analytics.
Hey there! Jen from Mixpanel here. I think this doc about how retention is calculated might be helpful to you, too. You can also check out our community forum, which has a ton of great resources.
If you feel like you need more, don't hesitate to hit up support at mixpanel dot com and chat with someone here who will be happy to get as detailed as you need!
Very nice website design. These are just thoughts from a quick pass, so don't take them too seriously; I hope they help:
One thing I like to see as soon as possible is sample code, possibly annotated. Something like this is what I'm referring to. Selecting my language of choice and seeing something like that is always the first thing I'm looking for when delving into the docs to decide if this tool is a good fit for my project.
Another thing you might consider is to show some nice sample graphs; something that makes me say "ooh, I wonder what my game's graph would look like".
Last critique I can think of is that the three sections "MULTI-PLATFORM CLIENT", "LIMITLESS PROJECTS", "STABILITY" seem almost like filler to me. These are things I would expect from any stat tracker (multi-platform may indeed be worth noting though, since I'd like to see if you have a library for my language/platform of choice).
Now then, my question for you is: why would I use this instead of Mixpanel or others?
> Would you agree though that it's generally easier to deploy to Android?
I've never done this so I can't comment. I would say the approval process is probably more lenient on Android (if it even exists), but beyond that I don't think there's much of a difference.
> But TestFlight requires the client to be running iOS 8 which makes it useless to test compatability with older devices.
This is true but iOS has far, <u>far</u> better adoption rates than Android so unless your app is as large as Facebook this isn't an issue. iOS 8 is an old OS now anyways.
> I can build it on any OS whereas I need a Mac (or a virtualized OSX) to build for iOS.
True.
> I can host my app for sale wherever I want to as many people as I want and they can copy the file and give it to their friends to install.
You could just create promo codes on iOS. Or you could give them the file and they could build it themselves with Xcode. Either way.
It's best not to speculate on what your users might do and follow instead what you can find out about what users are doing, as in the stats Mixpanel released on iOS 9 adoption.
My personal strategy is to start all new projects on the absolute latest version of iOS available so that I don't start off with any cruft from old, shorter-lifetime versions. For any already existing projects, I update to the most recent of the last version (8.4 in this case). That seems to maintain the best balance between feature availability versus losing the users who stop seeing app updates because they won't follow OS versions.
All devices that have 9 installed... You'll probably be safe to do this in a few months if you find using some of the 9 APIs save you a lot of development time. Like UIStackView.
Here you can see adoption, https://mixpanel.com/trends/#report/ios_9/from_date:-3,report_unit:hour,to_date:0
Yeah, I feel the same pain.There're many reasons behind this. Listing some from top of my head. Hope I am not overwhelming.
tl;dr: Android is open, sort of free, highly customizable but not the best place to do business.
#1 Revenue
It's very well known that iOS users are more likely to pay for apps than Android users. Because of that, the revenue generated in iOS apps is almost 3 times Android apps (it used to be 4 times - 80/20 in 2011).
#2 Ease to build apps
Android is very very fragmented. So for example, if I build an app, I will have to test it to at least 10 devices to make sure that it works as it is supposed to. The reason why things might not work is, different OEM have their custom shit in it, which sometimes break some functionalities, resulting in a crashing app (Unfortunately, XYZ stopped).
But in case of iOS, it's very simple job. Test it in some handful no of devices and you can safely assume that it's gonna work everywhere, because Apple is the one who's making and distributing devices + OS.
Moreover, the OS update adoption in iOS also pretty impressive as compare to Android. Which is also one annoying thing for developers and startups.
#3 Piracy
Unfortunately, it's very easy to get paid stuff for free in Android. Which sucks for paid apps. That's why developers are moving towards in-app purchases and subscription based models instead of paid apps model.
--
^(Please note, above are only my views and observations. It's not advisable to consider them as facts without further research.)
there are some useful breakdowns etc here:
https://mixpanel.com/trends/#report/iphone_models
https://mixpanel.com/trends/#report/ipad_models -- just beware performance of that first retina ipad (3,1-3,3)
Yep. They don't have identical offerings but are definitely competitors. Here's a short description from Mixpanel.
Remember that field goal percentages don't include fumbled snaps, offensive penalties, etc.
They also don't include that kickers tend to do worse, not better, following practice kicks: https://www.sharpfootballanalysis.com/analysis/icing-the-kicker-does-it-really-work/amp/
They also doesn't factor in NFL kickers may tend to do worse at the end of closer games: https://mixpanel.com/blog/nfl-data-icing-the-kicker/
Do I think the win probability model likely underestimates the chances of success for a kicker within 82% lifetime percentage from 40-49 yards? Yeah. But let's not forget only moments earlier he missed a kick with the game on the line. A successful kick was far from a foregone conclusion.
And on the Chiefs side, you can certainly argue that win probability underestimates Mahomes odds of winning the game if the DPI isn't called and Herbert's odds when it was.
I completely respect anyone who says they think the win probability on these two data points could flip who is number one and who is number two based on the model. I don't think anyone can argue that these plays weren't among the most impactful plays of the entire season. And for me that's the most important point, especially when you consider the officiating on them was questionable at best.
https://mixpanel.com/blog/nfl-draft-data/ I believe this would be the article I saw a while ago, running hardly opens up the pass if at all. I believe one reason why would be that defenses match offensive formations; if you are in 10 personnel, you don’t need 7 or 8 guys to stop the run
https://mixpanel.com/blog/nfl-draft-data/
As the other reply said FO have written stuff too but I think this was what I was trying to recall. Its a pretty simplistic analysis in that it only considers sequential plays and not whole game trends but it's still interesting.
PA is a funny one I find, sometimes you see fakeouts from the same look where they have the run or pass play designated but my understanding was that the strength of PA is that it causes hesitation and defenses tend to hesitate even if the team isn't running a lot, it's rare to see a team in a position to run PA and not have at least some balance - how often do you see good teams run PA when they're 2 scores down.
You obviously need balance but I'm not sure if that's done to set up the pass or exploit whatever the defence is showing you. If you're starting to see nickel or prevent then yeah either you're way behind or the balance is completely shot.
I get what you mean with PA and there are some cool instances where you see something used one way early in a season for it to be switched later, going from run to PA or vice versa but it's still rather specific. Here is the article I was referring to, it's quite basic to be honest in that it only considers sequential plays over game long trends:
We generally go for the last 2 major versions, although it depends a lot on the target audience.
One app I work on supports as far back as iOS 9 which is a pain in the ass. It's on my todo list to get the stats from Firebase and see how many users are actually on those versions.
I tend to use the Mixpanel stats to guide decisions. It's a bit more granular than the official Apple ones, and if you pull the JSON data, you can see it broken down by minor version. https://mixpanel.com/trends/#report/ios_14/from_date:-172,report_unit:day,to_date:-69
it is dated tbh, he has these core beliefs like using the run to set up the pass and play action pass. It's been proven that while the run game is important you don't have to establish the run to pass and use the play action effectively
"In short, good plays tend to follow other good plays; bad plays tend to follow bad plays. The run sets up the pass no better than the pass sets up the pass."
Henry only sees 8 men in the box 29% of the time, which places them 12th in the league. You know why? Because Tanny will burn them if they do, and they know it.
Here's an article explaining that there's no statistical difference in the impact of having an average run game and a great run game when it comes to the passing game. https://mixpanel.com/blog/nfl-draft-data/#:%7E:text=The%20run%20sets%20up%20the,pass%20sets%20up%20the%20pass
Here's a pretty exhaustive look at it, but the upshot is that there's no evidence to suggest that a good running game leads to a good passing game.
You can learn more on 1 of the popular tracking analytics company: mixpanel https://mixpanel.com/topics/mobile-user-tracking/ or this article https://www.cookiepro.com/blog/website-tracking/
If you really care about what I think, feel free to look through my reddit comment history.
Just for some context: I'm NOT complaining that the app doesn't work for me. I'm complaining that covid spreads the most in poor communities. Middle class people who have jobs they can do remotely have not been hit nearly as hard as densely urban poor communities that work service jobs. So if we want to stop this virus, that's the areas we need to really help to not spread.
And while I'm currently looking into getting a new phone, even though apple SHOULDN'T make 6-year-old tech obsolete, the point is that a public health policy needs to reach as many people as possible.
I was looking for data on this and finally found it:
https://mixpanel.com/trends/#report/ios_14
As of right now, 6.7% of iphone users still run ios 12. And I would guess that not updating your phone or your IOS is strongly correlated with being in the highest COVID risk group (poor, old, or both). And THAT is where I see the problem.
Again, if you go back long enough you'll see me argue elsewhere that being "poor" actually guarantees you to be middle class in NY thanks to all the tax benefits and such. I'm not complaining about what I have. I'm complaining about what isn't effective.
Look at Mixpanel's pitch deck they mention two problems https://mixpanel.com/blog/open-sourcing-our-pitch-deck-that-helped-us-get-our-865m-valuation/
https://mixpanel.com/trends/#report/ios_13
The mixpanel stats are generally pretty good, as they are an aggregate of all devices using the mixpanel tracking sdk.
We're sitting at 74.90% on iOS13 right now, 21.23% on iOS12, and 3.78% on older.
Tech stack doesnt mean its a web application you idiot. It means the set of tools/technologies used to build an application https://mixpanel.com/topics/what-is-a-technology-stack/#:~:text=Definition,and%20run%20one%20single%20application.
MixPanel's numbers say 88% of devices worldwide are on iOS 13, which is only slightly less than the number of devices on Android 6 (the minimum for Google's framework).
https://mixpanel.com/trends/#report/ios_13/from_date:-3,report_unit:day,to_date:0 https://mixpanel.com/trends/#report/android_os_adoption/from_date:-9,to_date:0
Given in the past Apple have convinced people to upgrade for a new emoji, asking them to go to 13.5 to use the contact tracing app really isn't that big of a deal.
iOS 13 is being used by 80% of iPhones according to MixPanel and 88% according to David Smith.
Seems like a reasonable target for a new app that won't even ship for months unless you really need older device support.
https://www.google.com/amp/s/www.fieldgulls.com/platform/amp/2018/1/3/16808842/seahawks-establish-the-run-myth-nfl-analytics https://www.footballoutsiders.com/info/FO-basics https://mixpanel.com/blog/2017/04/28/nfl-draft-data
I hope you like charts becUse you're not only wrong, but you're very wrong. Running is important because of the ability to manage the clock, not to set up your passing game.
Mixpanel is a good tool too - https://mixpanel.com. They have a free plan which is nice to start getting some good data about what your early users are doing on your web app.
The vast majority of an iphone are sold within its launch year though....you can see this from mixpanel stats. And the regular/plus split occurs early in the cycle. So the xs max appears to be the better selling of the xs/xs max set.
Here’s mixpanel’s data: https://mixpanel.com/trends/#report/iphone_models/from_date:-1395,report_unit:month,to_date:0
- What do you think of this; a vehicles-miles-traveled-tax? This is an incentive mechanism to affect public behavior when using our transport network.
- Also get this, the vehicle pays it, not us. The car needs to own some money to do that no? Bingo.
- Vehicles also needs to be connected all the time. 5G bebeh.
- No need for tolls, road tax, heck, no need for private car ownership anymore, might even solve traffic jams.
Both rushing efficiency and rushing volume have very little to no effect on play action efficiency (source), so why would either have any effect on overall passing efficiency?
These queries say they don't. I'm sure there's other evidence that says the same.
You're peddling old conventional wisdom that should be dead by now. Let it die.
You can see at the playstore reviews too.
Here are some links (german tho) but you can also find that on their github IIRC.
- https://www.androidpit.de/datenschutz-messenger-wire-tracking-code-sendet-daten-in-die-usa
- https://www.kuketz-blog.de/messenger-wire-beinhaltet-mixpanel-app-tracking/
- The tracking service is: https://mixpanel.com/
Which had some negative stuff going on in the past already.
The problem is, you could opt out of the data transmission, but the Wire app sends data before you even get to the settings to disable it. It sends data when the app is started. This is also not allowed since we have the "General Data Protection Regulation (GDPR)" in the EU. Even if they remove this, the trust is lost + a tracking servicce of a shady company is not a good feeling.
Thanks for your honest feedback. I appreciate it.
The module was written to solve a real need. While we, as developers might be better off learning the elasticsearch DSL for our needs, we can't quite ask clients to do the same. Our segmentation was inspired by mixpanel. While I have no idea how they implement it, I had to solve the problem for querying elasticsearch for arbitrary Where conditions. And I did that using PEG.js. While you might be right that there aren't too many applications for it, I am sharing it with the hope that someone will find it useful.
If the elastic-muto DSL seems complicated, that might just be my failure to convey it in a simple and easy to understand manner. Let me give it another shot. The conditions are quite similar to SQL conditions in the sense that you can combine them with and/or. Conditions are quite simple. They have the field, operator and a value. Operators are also similar to SQL conditions like ==, !=, <= etc. Hope that helped.
I'm not going to relate my friends' stories out of respect for their privacy, but here are some links to people's stories that are already public:
https://www.fastcompany.com/3036174/strong-female-lead/what-its-really-like-for-women-in-tech
https://mixpanel.com/i-am-tech/#video/70xdKbs0OhA
I think it's possible to reasonably disagree on the extent of how different women's experiences in tech are from men's and how important that difference is, but it seems hard to deny that it exists.
No, not at this point. Considering iOS 9 doesn't drop support for older hardware (and by most reports makes older hardware faster) I didn't see much of a reason to stick to iOS 8.
Going iOS 9 only let me cut some cruft and focus on building awesome features, vs supporting users who will likely upgrade by the end of the winter anyway (we're already at 75% adoption, where as iOS 8 was only at 50% by this time last year)
Give iOS 9 a shot, it's a lot more stable than 8 ever was (heck even the betas for 9 were more stable than 8)
What sort of metrics are you looking to collect? If you just want to record high-level events (like every time a player uses a power up or something), you might be able to get away with Mixpanel or Google Analytics
> And there were plenty of exploits for iOS, and there will be in the future
Most of these affect pre-iOS 9. And, after 1 month, iOS 9 has 65% adoption, while iOS 8 has 28% adoption: > https://mixpanel.com/trends/#report/ios_9/from_date:-29,report_unit:day,to_date:0
.
> While iOS only has one app source it still lets in malware
This was quickly identified, and now devs are made to verify Xcode before running.
> On Android devices you can install apps from any source, hence it is a easier target for criminals to dupe foolish users.
> Because there is one entity required to patch a bug in iOS while there are a few thousand(many non existant a few months after the handset release) in order to patch all android devices, hence there are plenty of android devices vulnerable. That has nothing to do with the security architecture.
These issues do not change the fact that Android is vulnerable. This is a central argument. Apple made the correct choice in their design (you can consider it their "security architecture"), which has led to far less fragmentation and faster updating. Google made poor choices, which has led to massive fragmentation. The end result is that the average Android user has a very vulnerable OS, while the average Apple user has as secure OS.
Actually, I knew I would have caught this. Looks like they VERY RECENTLY updated their page to add the nofollow --
link to an archive in June 2015: https://web.archive.org/web/20150618171637/https://mixpanel.com/free/
Extremely unlikely. Even on Mixpanel charts it barely registers. And Mixpanel already had a bias towards modern devices in comparison to Google's stats.
Edit: on my own applications' stats, 6.0 is not even showing either. It's probably part of "Others", which is 0.24%.
I actually thought about this as a startup in the past. I think a lot of products out there do their thing very well. But I always thought that one app that was connected could do things much better.
As a small example, why don't we let users fill out bug reports that go straight into the bug tracking and get assigned to developers?
Obviously, we don't want them filling out a long-ass form, but it could be done discreetly.
When an error occurs, a light version of Intercom would take their information (location, browser, account details). A light version of MixPanel could get be used to see how they came to this problem (they were on Dashboard, then clicked add user, etc). A simple error message would be shown with a textbox to ask the user what happened.
All this could be logged into bug tracker once done. The system could even assign specific areas of the app to a developer or a team of developers. Thats serious accountability. I'm sure developers would ensure their section was top-notch - especially if they didn't want to be getting a ton of bug fixes.
I'm not sure what does it mean that "you are doing a project" - do you need to describe how to do this or do you actually need to to this?
Anyway, what you want to do is to create a funnel chart. Here's some description: https://mixpanel.com/funnels/
If you mean tracking what their clicks, sessions, etc is... there are quite a few options.
The two I'd recommend is mixpanel and appdynamics.
For crashes, crashlytics is the way to go.
Angular and technologies like it is mostly for one page applications. It brings a lot of headaches in big projects. I recently saw very useful video cast on this from Uber. See this video when you have time: https://mixpanel.com/education/data-driven-optimization
For anyone wanting to know what iphone models that are used the most, this is a good resource. I use this to determine what iphone model to do the most development for/testing on and to see trends of usage.
Depends on when you are trying to track an event. Is it on the server or the client side. If it's in the browser it's probably better to take a look at their JavaScript integration. Then it's nothing more than importing their library and then doing a:
mixpanel.track("Opened Main Landing Page");
Can't be done using GA but I've heard you can do it with Mixpanel; they call it People Analytics.
Sorry if that sounded harsh. Your current design just doesn't give your brand/company a professional feel. Here are some points of critique:
Upon visiting your website, I didn't really understand what you could offer me. What value does your company offer? Why can't I get 'business data analysis' (which is very vague) elsewhere? Take a look at this link: https://mixpanel.com - they tell a story with a header and subheader. I understand what they're offering from this. They also supplement this with visual graphics.
Not sure what relevance the header image is to your company.
Next section -- red text again (needs changing - bright red = bad, danger, alert, risk). It's also quite dark. Your site needs lightening up!
Check grammar. Don't keep putting a space between your sentence and a question mark!
Next section 'Data visualisation for your business' doesn't really let the user know what you can offer them. It's just a pointless header.
Next section is the best one. You offer a bit of information and you have the 'who we are' area.
I'd start by using your current layout. Change the images. Make the dark sections white. Change the red to a green or blue (look at the flatuicolors link below for a beautiful shade). Add some subheaders beneath your big headers to explain a bit more about your product. Use icons where possible.
Good luck and let me know if you need any help!
We're also considering using Tableau or possibly becoming a Mixpanel partner to gain access to 200,000 data points a month. Is this a good platform to use as a short term solution?
Ok, I signed up for an account and tested that endpoint, this is the script that works for me:
import hashlib import json import requests import time
API_KEY = '1234' API_SECRET = '5678'
query_params = { 'api_key': API_KEY, 'from_date': '2014-04-01', 'to_date': '2014-04-30', 'event': 'High Fantasy', 'expire': str(int(time.time()) + 600), 'format': 'json', }
s = ''.join('='.join(i) for i in sorted(query_params.items())) s += API_SECRET query_params['sig'] = hashlib.md5(s).hexdigest()
ENDPOINT = 'https://mixpanel.com/api/2.0/segmentation/'
response = requests.get(ENDPOINT, params=query_params)
data = response.json()
print data
If you replace the key and secret with your real ones, then run it, it should work. Checking for differences between your script and this one should let you pinpoint where the issue is.