We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 9 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(5)
Simon,查看 Localytics(我在那里工作)。我们的服务是实时的,我们的 SDK 是开源的,有免费和付费服务计划,而且我们刚刚发布了网络界面的重大更新。您可以在此处访问演示(无需注册):https://dashboard.localytics.com/demo
——布莱恩
Simon, check out Localytics (I work there). Our service is real-time, our SDKs are open source, there are both free and paid service plans, and we just released a huge update to our web interface. You can access the demo (no registration required) here: https://dashboard.localytics.com/demo
--Brian
AskingPoint.com(我在那里工作并且是创始人)。
我们不会也不会出售您的数据。我们是免费的,因为我们计划最终通过一项选择加入的服务赚钱,我们将向第三方收取收入,我们将与参与并帮助产生该服务的应用程序分享收入。
AskingPoint.com (I work there and am the founder).
We don't and won't sell your data. We are free because we plan on eventually making our money from an opt-in service that we will charge third parties for the revenue from which we will share with the Apps that participated and helped generate it.
还有HockeyApp。我只是根据 Flurry 和 HockeyApp 的网站宣传来比较它们,我的总结是 HockeyApp 更“以修复为中心”,而 Flurry 更“以销售为中心”: QA 将从 HockeyApp 出色的崩溃报告功能中获益更多,而产品管理将从 Flurry 疯狂的切片分析中获益更多。希望这有助于根据您想要实现的目标来指导您。
更新:我与 Crittercism 的家伙进行了快速交谈,并想添加我的发现。他们的产品似乎填补了以修复为中心的 HockeyApp 和以销售为中心的 Flurry 之间的空白。它使用相同的底层 PLCrashReporter 库来生成强大的崩溃报告,就像 HockeyApp 一样,而且它似乎比 HockeyApp 具有更多类似 Flurry 的分析功能。另外,定价...... Flurry 是免费的(尽管他们似乎通过 WWW 界面上的广告来赚钱)。 HockeyApp 的定价基于计划,从每月 10 美元的计划开始。 Crittercism 价格基于您应用程序的活跃用户数量,您必须与他们的销售人员合作才能找出实际数字。
同时更新有关支持:HockeyApp 的支持非常好;我从来没有等待超过 10 分钟才能得到对我的问题的答复,而且答复简洁而准确。混乱,大约 24 小时的周转时间和相当不个性化且毫无生气的反应,但基本上是准确的。 Crittercism 很快就回应了我的询问。他们有一个“立即聊天!”按钮让我接通了首席技术官,这对于解决我遇到的技术问题非常有用。
一些关键细节和阐述:
HockeyApp 自动在其网络上表示用户的崩溃报告
接口,并可以通过崩溃API对崩溃进行分组。乱舞则不然;
它只是向您显示一堆原始崩溃,您可以手动进行
一次将它们符号化为一条指令(使用
atos
——你不能使用
symbolicatecrash
因为 Flurry 没有给你一个合适的.崩溃报告)。请注意 HockeyApp 中的行号可以关闭
通过一两行。
Flurry 的崩溃报告显示您不包括其他正在运行的
进程,而 HockeyApp 则执行。事实上,似乎 乱舞
崩溃报告被截断至 255 个字符左右。与 HockeyApp 相比,它们很贫乏。
对于您在 HockeyApp 的 Web UI 中标记为已修复的崩溃,HockeyApp 可以
通知随后遇到此类崩溃的用户
该问题已在新版本中修复。
Flurry 拥有 HockeyApp 无法企及的非常深厚的分析能力:
跟踪使用统计数据、客户参与度、平均会话时长、
应用程序的地理分布、一段时间内的用户保留率。 Flurry
乱舞是免费的; HockeyApp(最多免费 10 个应用程序)。两个都
提供电子邮件支持,但只有 HockeyApp 提供讨论
团体。两者都可以记录任意消息(例如来自的 JSON 响应)
导致您的应用程序崩溃的服务器)但仅限 HockeyApp
表示该消息可以是任意长度。
唉,这些只是一些随机的花絮,吸引了我的开发本性,让我更喜欢 HockeyApp。我想知道如果我在我的应用程序中使用两者会发生什么!
如果您有 7 分钟的时间,HockeyApp 有我发现的视频演练非常有用。
There is also HockeyApp. I am comparing Flurry and HockeyApp based solely on grokking their website propaganda, and my summary is that HockeyApp is more "fix-centric", whereas Flurry is more "sales-centric:" Dev & QA would benefit more from HockeyApp's great crash reporting features, and Product Management would benefit more from Flurry's crazy slice-and-dice analytics. Hopefully that helps guide you based on what you are trying to accomplish.
Update: I had a quick chat with the Crittercism dudes and wanted to add my findings. Their offering seems to fill the gap between fix-centric HockeyApp, and sales-centric Flurry. It uses the same underlying PLCrashReporter library to produce robust crash reports like HockeyApp does, and it seems to have more Flurry-like analytics than HockeyApp. Also, pricing ... Flurry is free (though they seem to monetize through advertising on their WWW interface). HockeyApp has pricing based on plans, starting with a $10/month plan. Crittercism prices based on # of active users of your app and you have to work with their sales folks to eek out an actual number.
Also update regarding support: HockeyApp's support is excellent; I've never waited more than 10 minutes to get a response back to my questions and the responses are succinct and accurate. Flurry, about 24 hr turnaround and a fairly unpersonalized and lifeless response that was mostly accurate. Crittercism has been quite fast to respond to my inquires; they have a "Chat Now!" button that put me through to the CTO, which was great for the technical questions I had.
Some key specifics and elaborations:
HockeyApp automatically symbolicates users' crashreports on their web
interface, and can group crashes by crashing API. Flurry does not;
it just shows you a bunch of raw crashes and you get to manually
symbolicate them one instruction at a time (using
atos
-- you can'tuse
symbolicatecrash
because Flurry doesn't give you a proper.crash report). Be aware that line numbers in HockeyApp can be off
by one or two lines.
The crash reports that Flurry shows you do not include other running
processes, whereas HockeyApp's do. In fact, it appears that Flurry
crash reports are truncated to 255 characters or so. They are anemic compared to HockeyApp.
For crashes you mark as fixed in HockeyApp's web UI, HockeyApp can
inform a user who subsequently experiences such a crash that the
issue has been fixed in a new version.
Flurry has very deep analytics prowess that HockeyApp cannot touch:
tracking usage stats, customer engagement, average session length,
geographic distribution of your app, user retention over time.
Flurry is free; HockeyApp (free up to 10 apps). Both
provide email support, but only HockeyApp provides a discussion
group. Both can record arbitrary messages (like a JSON response from
the server that caused your app to crash) but only HockeyApp
indicates that this message can be any length.
Alas, these are just a few random tidbits that appealed to my developer-nature and cause me to prefer HockeyApp. I wonder what would happen if I used both in my app!
If you have 7 minutes, HockeyApp has a video walkthrough that I found quite useful.
Cobub Razor 是一个像 Flurry 一样的开源免费系统。并且它同时开放了SDK和Web端源代码。
演示:http://demo.cobub.com/razor/en
GitHub:http://www.github.com/cobub/razor
Cobub Razor is an open source free system like Flurry. And it opens both SDK and web side source codes.
Demo: http://demo.cobub.com/razor/en
GitHub: http://www.github.com/cobub/razor
Mixpanel,我听说过很多关于他们产品的好消息 https://mixpanel.com/
Mixpanel, I have heard a lot of good thing about their product https://mixpanel.com/