Posts tagged Doing

New Facebook Tools Let Developers See What Users Are Doing In Their Apps

Facebook has a new plan for helping application developers monitor the success—or failure—of their applications. And that’s true whether they’re developing apps specifically to work with Facebook or not.

On Tuesday, the company introduced two new functions in App Insights, a tool that lets developers monitor traffic and Facebook interactions for apps. The new capabilities give app developers more detailed information about user behavior and app performance.

App Insights requires the Facebook software development kit (SDK), but works for general mobile apps as well as desktop apps that are integrated with Facebook.

Developers can now categorize groups of people by using “label cohorts” that group individuals into specific categories based on actions they’ve taken in a particular app. This information enables simple A/B testing, in which developers introduce a change for a subset of users to see how they react.

For instance, mobile game developers can provide one group of people with a digital gift and then track that cohort to see if it leads them to eventually spend more in the game.

Facebook offers four preset cohort types. These include “action-based,” for groups of people who done something specific, like clicking a button or making a purchase, and “time-based,” for users who all downloaded an app at the same time. Developers can create their own unique cohort types as well.

The second update provides specific, time-based data on how frequently people use an application and what kind of action they take after downloading it. This data is available up to 14 weeks after the person installs the app, and can be found in Facebook’s new App Event retention charts.

These charts monitor different “events,” like installing the application or making an in-app purchase. Developers can use this data to find out how fast users get to a specific level in the game, or how soon after downloading an application a user makes a purchase. 

To start using the new tools, developers should install the Facebook SDK.

Photo courtesy of Facebook

View full post on ReadWrite

Bad Link-Building You Should Be Doing

In a lot of cases, links from methods that many would consider bad are not just part of a natural profile but can actually drive traffic and PageRank.

View full post on Search Engine Watch – Latest

4 Things Your Competitors Are Doing This Q4 to Crush You on Google

Q4 is the ultimate game. There is no halftime show, but all the big teams are playing, and everyone is coming to the game.

View full post on Search Engine Watch – Latest

Live @ SMX East: What SEOs Should Be Doing With Mobile

For years, debates raged about what constituted “best practices” when it came to mobile SEO. Early on, the discussion focused on whether it was important to have a separate site optimized for mobile devices. That proved to be a major challenge, as it required detecting and optimizing…

Please visit Search Engine Land for the full article.

View full post on Search Engine Land: News & Info About SEO, PPC, SEM, Search Engines & Search Marketing

21 Things Every Web Developer Should Be Doing by @stoneyd

  If only Ferris knew what was ahead. That quote comes from much simpler, and slower times. With the web and all it’s related technologies, we have seen life change faster than ever. If life was fast during Ferris’ day, it’s at lightning speed now. But the faster life gets, the more we have to slow down to take stock of things. This is no less true in the ever-changing web. But let’s start at the beginning: web development. This is usually the starting point of a business’ web presence outside of social media. Sometimes, in haste to “get going” […]

The post 21 Things Every Web Developer Should Be Doing by @stoneyd appeared first on Search Engine Journal.

View full post on Search Engine Journal

11 Things You Should be Doing With Google Analytics by @YEC

Google Analytics offers e-commerce startups a great way to increase conversions and grow revenue by seeing where a site or mobile app could use improvements. It’s a great tool — if you’re not already using it, you should be. Although most entrepreneurs know the basics, there are a whole host of lesser-known Google Analytics tips that startups could be using to improve their business. Here are 11 of them: Create Custom Audience Segments Put your target audience analysis and personas to good use by creating customer audience segments in Google Analytics. You can apply these to overall traffic or individual […]

The post 11 Things You Should be Doing With Google Analytics by @YEC appeared first on Search Engine Journal.

View full post on Search Engine Journal

Takeaways from Sean Si’s “I’m Not Doing SEO”: A #SEOSummit Recap by @AkiLiboon

SEJ’s Philippine team was privileged to attend last Saturday’s SEO Summit and meet the speakers. Among them is Sean Si, a Filipino motivational and leadership speaker and the founder of SEO Hacker, a Philippine-based company that provides Internet Marketing and SEO services. “I’m Not Doing SEO” While the event is all about SEO, Sean talked about how the art of sales can pump up your business’ online marketing campaign. According to him, “Online marketing is bringing your brand from the throne to the hearts and minds of people.” In order to achieve that, you need to find the right arena […]

The post Takeaways from Sean Si’s “I’m Not Doing SEO”: A #SEOSummit Recap by @AkiLiboon appeared first on Search Engine Journal.

View full post on Search Engine Journal

Why I Left Doing Just SEO – Business 2 Community

Why I Left Doing Just SEO
Business 2 Community
Nobody what anybody tries to tell you, SEO is, by its very nature, a reactive industry. Traffic goes down, you react. Links disappear, you react. Google changes their algorithm, everybody reacts. It's not the only industry like this, but it was

View full post on SEO – Google News

Distributed Development: You’re Still Doing It Wrong

Distributed computing is the future of technology, but you’d never know it from how many tech organizations continue to operate. While our systems run across multiple servers and even data centers, our development teams too often sit within the same office. While there are real benefits to a co-located development team, the costs of competing for local talent may well outweigh them.

Ironically, open source has taught us how to effectively work in a distributed fashion, but far too few organizations have heeded its lessons. 

The Costs Of Homogeneity

Facebook is the world’s largest open source company, as I wrote recently. If any company groks open source, it’s Facebook. 

And yet Facebook has a very 20th century approach to development. When my company was acqui-hired by Facebook a few years back, Facebook had little interest in any engineer that wasn’t located within Silicon Valley. Move to the Valley or move on, was the mantra.

There are good reasons for this mindset. Studies have found that co-located engineering teams can be more productive, with less time needed to coordinate resources, make decisions, etc. Embedded in that decision, however, is a tradeoff, which Jeff Waugh uncovers in reference to why companies elect the co-located or distributed development approach:

Not only does distributed development yield a greater range of people, but it also provides access to talent at far lower cost. This is a big deal given the escalating cost of recruiting and hiring engineers. Seen the price of an engineer in Silicon Valley these days?

In an email conversation, former MySQL and ZenDesk executive Zack Urlocker pushed the advantages of distributed development. Not only is it “much easier to hire when you have distributed teams,” he told me, but it turns remote locations into real offices and “not just sales outposts,” which is good for both productivity and morale beyond the engineering team. 

But set aside the costs for a moment. Can distributed development actually work?

What Open Source Teaches Us

For those in the open source world, this is almost a silly question. Some of the world’s greatest software, from Linux to Hadoop, gets written by disparate engineers huddled over their laptops in far-flung locations. By its very nature, open-source development favors online collaboration on code, with all communication happening on mailing lists, chat channels and more. 

In the open source world, you can collaborate with your colleague sitting next to you, but any relevant communication needs to happen online, or the model falls apart. If anyone is privileged by sitting next to their peers in the office, the model breaks. 

GitHub can help. Increasingly, development happens on GitHub, brilliantly explained in non-geek speak by Lauren Orsini. GitHub works so well because it allows developers to work on their own time, forking and merging code asynchronously, either collaboratively or competitively. 

Your Mileage May Vary

Of course, the subtext here is that distributed development works better when the software architecture allows it, not to mention company culture. As Charles Wise posits, “Tightly integrated apps are much tougher” to pull off than systems that involve modular architectures. Given the increasing prevalence of open-source code emerging from tech titans like Facebook and Google, perhaps the default should be modular architectures that are a natural fit for distributed development?

Even with tightly integrated systems, companies have shown that it can work, and well. Marten Mickos, a veteran of MySQL, which had a very distributed workforce, and current CEO of open-source cloud company, Eucalyptus, emailed me some thoughts on how Eucalyptus works:

We have software developers in China, Bangladesh, India and all over the US. A third are located in Santa Barbara where we have an office. The rest work from their homes or collaborative workspaces.

Everything we do is online. We use Jira, Confluence, Github, wiki pages, email, IRC and so on.

Our developers have small private (and personal) clouds in order to be more productive.

We do regular online meetings for specific teams, specific features and specific releases. We follow an agile model, shipping major feature releases twice a year and maintenance releases every second month.

A lot of discussions happen on email. We have an alias for fun@ and one for life@ and discuss@ and On these lists, people can exchange information and debate various topics. And if they are busy, they can of course ignore those emails.

Because of our model and our commitment to openness, we have been able to recruit some of the absolutely best engineers in the field of distributed systems. The fact that they don’t have to move to wherever the HQ are is a huge plus from them.

This has been my experience as well, having worked at highly distributed teams at Canonical and Nodeable and more tightly coupled teams at Alfresco and MongoDB. Both work, though in different ways. 

What Works For You

Ultimately, though, whether distributed development can work for your company comes down to—surprise!—the particular nuances of your company, as Twitter’s open source guru, Chris Aniszczyk suggests:


All true. But my modest proposal is that many companies haven’t even tried to experimented with distributed development, and they should. As Urlocker insists, co-located development is “good but it’s limiting. Over time there is tremendous advantage to having multiple Dev teams in multiple cities.”

Better, more diverse talent at less cost. That sounds like a winning formula.

View full post on ReadWrite

Up Close @ SMX Advanced: What Advanced SEMs Should Be Doing About Mobile

Every year is the year of mobile, and 2014 hasn’t been a disappointment. Mobile screen time now exceeds TV in the United States. Fifty percent of paid-search clicks on Google will come from mobile devices in 2015, according to one forecast. So what do advanced SEMs need to know about mobile, and…

Please visit Search Engine Land for the full article.

View full post on Search Engine Land: News & Info About SEO, PPC, SEM, Search Engines & Search Marketing

Go to Top
Copyright © 1992-2014, DC2NET All rights reserved