Reflecting on a Big Week at Mobile World Congress

Filed in Mobile World Congress, Roaming by on March 12, 2015 0 Comments

As I mentioned last week, Mobile World Congress is one of my favorite times of the year. It’s one incredibly nonstop, action-packed week, but one of the few weeks of the year when much of the mobile industry concentrates at one venue.

I just returned from this year’s show, and, as usual, the people, the energy and the innovation have left me more energized and optimistic than ever about what’s ahead for mobile. This year, a record-breaking 93,000-plus attendees from 200 countries came to the event, where keynote speakers included such notables as Facebook CEO Mark Zuckerberg and U.S. Federal Communications Commission Chairman Tom Wheeler, among a long, long list of other speakers.

Syniverse was fortunate to have more than 65 Syniverse colleagues in attendance, and we hosted almost 300 meetings with customers, industry colleagues, media representatives, analysts and many others.

MWC_2015_Pavilion1

MWC_2015_Pavilion2

The Syniverse pavilion.

The highlight of our attendance was the announcement of a new study that illustrates crucial areas of revenue opportunity and risk for operators. The results highlight what we think is an imperative for operators to maintain primary focus on core business areas like roaming and to take action to protect revenue in the face of today’s tough competition for subscribers.

The announcement resulted in a variety of media coverage, including an interview with bnetTV just outside our pavilion that offered me an opportunity to shed more light on the study. I invite you to access it here or through the image below to find out more about what our results uncovered.

And after you watch the video, be sure to share your thoughts and reflections on Mobile World Congress 2015 in the comments section below.

MWC_2015_Interview

Tags: , , , ,

avatar

About the Author ()

Mary Clark is a former Chief Corporate Relations Officer and Chief of Staff at Syniverse.

Leave a Reply

/*AddThis*/