Showing posts with label Mobile apps. Show all posts
Showing posts with label Mobile apps. Show all posts

Tuesday, June 21, 2016

Expert Panel Explores the New Reality for Cloud Security and Trusted Mobile Apps Delivery

Transcript of a discussion on the heightened role of security in the age of global cloud and mobile delivery of apps and data.

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Citrix.

Dana Gardner: Hi, this is Dana Gardner, Principal Analyst at Interarbor Solutions, and you're listening to BriefingsDirect.

Gardner
Our next innovation thought leadership panel discussion focuses on the heightened role of security in the age of global cloud and mobile delivery of apps and data. As enterprises and small to medium-sized businesses (SMBs) alike weigh the balance of apps and convenience with security -- a new dynamic is emerging.

Security concerns increasingly dwarf other architecture considerations. Yet advances in thin clients, desktop virtualization (VDI), cloud management services, and mobile delivery networks are allowing both increased security and edge applications performance gains.

To learn more about the new reality for end-to-end security for apps and data, please join me in welcoming our panel: Stan Black, Chief Security Officer at Citrix; Chad Wilson, Director of Information Security at Children's National Health System in Washington, DC; Whit Baker, IT Director at The Watershed in Delray Beach, Florida; Craig Patterson, CEO of Patterson and Associates in San Antonio, Texas, and Dan Kaminsky, Chief Scientist at White Ops in San Francisco.
Learn more about the Citrix Security Portfolio 
of Workspace-as-a-Service, Application Delivery, 
Virtualization, Mobility, Network Delivery,
 and File-Sharing Solutions
Gardner: Stan, a first major use case of VDI was the secure, stateless client. All the data and apps remain on the server, locked down, controlled. But now that data is increasingly mobile, and we're all mobile. So, how can we take security on the road, so to speak? How do we move past the safe state of VDI to full mobile, but not lose our security posture?

Black: Probably the largest challenge we all have is maintaining consistent connectivity. We're now able to keep data locally or make it highly extensible, whether it’s delivered through the cloud or a virtualized application. So, it’s a mix and a blend. But from a security lens, each one of those of service capabilities has a certain nuance that we need to be cognizant of while we're trying to protect data at rest, in use, and in motion.

Gardner: I've heard you speak about bring your own device (BYOD), and for you, BYOD devices have ended up being more secure than company-provided devices. Why do you think that is?

Caring for assets

Black: Well, if you own the car, you tend to take care of it. When you have a BYOD asset, you tend to take care of it, because ultimately, you're going to own that, whether it’s purchased for you with a retainer or what have you.

Black
Often, corporate-issued assets are like a car rental. You might not bring it back the same way you took it. So it has really changed quite a bit. But the containerization gives us the ability to provide as much, if not more, control in that BYOD asset.

Gardner: This also I think points out the importance of behaviors and end-user culture and thinking about security, acting in certain ways. Let's go to you, Craig. How do we get that benefit of behavior and culture as we think more about mobility and security?

Patterson: When we look at mobile, we've had people who would have a mobile device out in the field. They're accustomed to being able to take an email, and that email may have, in our situation, private information -- Social Security numbers, certain client IDs -- on it, things that we really don't want out in the public space. The culture has been, take a picture of the screen and text it to someone else. Now, it’s in another space, and that private information is out there.

You go from working in a home environment, where you text everything back and forth, to having secure information that needs to be containerized, shrink-wrapped, and not go outside a certain control parameter for security. Now, you're having a culture fight [over] utilization. People are accustomed to using their devices in one way and now, they have to learn a different way of using devices with a secure environment and wrapping. That’s what we're running into.

Gardner: We've also heard at the recent Citrix Synergy 2016 in Las Vegas that IT should be able to increasingly say "Yes," that it's an important part of getting to better business productivity.

Dan, how do we get people to behave well in secure terms, but not say "No"? Is there a carrot approach to this?

Kaminsky: Absolutely. At the end of the day, our users are going to go ahead and do stuff they need to get their jobs done. I always laugh when people say, "I can’t believe that person opened a PDF from the Internet." They work in HR. Their job is to open resumes. If they don’t open resumes, they're going to lose their job and be replaced by someone else.

Kaminsky
The thing I see a lot is that these software-as-a-service (SaaS) providers are being pressed into service to provide the things that people need. It’s kind of like a rogue IT or an outsourced IT, with or without permission.

The unusual realization that I had is that all these random partners we're getting have random policies and are storing data. We hear a lot of stuff about the Internet of Things (IoT), but I don't know any toasters that have my Social Security number. I know lots of these DocuSign, HelloSign systems that are storing really sensitive documents.

Maybe the solution, if we want people to implement our security technologies, or at least our security policies, is to pay them. Tell them, "If you actually have attracted our users, follow these policies, and we'll give you this amount of money per day, per user, automatically through our authentication layer." It sounds ridiculous, but you have to look at the status quo. The status quo is on fire, and maybe we can pay people to put out their fires.

Quid pro quo

Gardner: Or perhaps there are other quid pro quos that don't involve money? Chad, you work at a large hospital organization and you mentioned that you're 100 percent digital. How did you encourage people with the carrot to adhere to the right policies in a challenging environment like a hospital?

Wilson: We threw out the carrot-and-stick philosophy and just built a new highway. If you're driving on a two-lane highway, and it's always congested, and you want somebody to get there faster, then build a new highway that can handle the capacity and the security. Build the right on- and off-ramps to it and then cut over.

Wilson
We've had an electronic medical record (EMR) implementation for a while. We just finished up rolling out to all of our ambulatory spaces for electronic medical record. It's all delivered through virtualization on that highway that we built. So, they have access to it wherever they need it.

Gardner: It almost sounds like you're looking at the beginning bowler’s approach, where you put rails up on the gutters, so you can't go too far afield, whether you wish to or not. Whit Baker, tell us a little bit about The Watershed and how you view security behavior. Is it rails on the gutters, carrots or sticks, how does it go?

Baker: I would say rails on the gutters for us. We've completely converted everything to a VDI environment. Whether they're connecting with a laptop, with broadband, or their own home computer or mobile device, that session is completely bifurcated from their own operating system.

So, we're not really worried. Your desktop machine can be completely loaded with malware and whatnot, but when you open that session, you're inside of our system. That's basically how we handle the security. It almost doesn't require the users to be conscious of security.

Baker
At the same time, we're still afraid of attachments and things like that. So, we do educational type things. When we see some phishing emails come in, I'll send out scam alerts and things like that to our employees, and they're starting to become self-aware. They are starting to ask, "Should I even open this?" -- those sort of things.

So, it's a little bit of containerization, giving them some rails that they can bounce off of, and education.

Gardner: Stan, thinking about other ways that we can encourage good security posture in the mobility era, authentication certainly comes to mind, multi-factor authentication (MFA). How does that play into this keeping people safe?

Behavior elements

Black: It’s a mix of how we're going to deliver the services, but it's also a mix of the behavior elements and the fact that now technology has progressed so much that you can provide a user an entire experience that they actually enjoy. It gives them what they need, inside of a secure session, inside of a secure socket layer, with the inability to go outside of those bowling lanes, if they're not authorized to do so.

Additionally, authentication technologies have come a long way from hard tokens that we used to wear. I've seen people with four, five, or six of them, all in one necklace. I think I might have been one of them.
Authentication technologies have come a long way from hard tokens that we used to wear.

Multi-factor authentication and the user interface  are all pieces of information that aren't tied to the person's privacy or that individual, like their Social Security Number, but it’s their user experience enabling them to connect seamlessly. Often, when you have a help-desk environment, as an example, you put a time-out on their system. They go from one phone call to another phone call and then they have to log back in.

The interfaces that we have now and the MFA, the simple authentication, the simplified side on all of those, enable a person, depending upon what their role is, to connect into the environment they need to do their job quickly and easily.

Gardner: You mentioned user experience, and maybe that’s the quid pro quo. You get more user experience benefits if you take more precautions with how you behave using your devices.

Dan, any thoughts on where we go with authentication and being able to say, Yes, and encourage people to do the right thing?
Learn more about the Citrix Security Portfolio 
of Workspace-as-a-Service, Application Delivery, 
Virtualization, Mobility, Network Delivery,
 and File-Sharing Solutions
Kaminsky: I cannot emphasize how important usability is in getting security wins. We've had some major ones. We moved people from Telnet to SSH. Telnet was unencrypted and was a disaster. SSH is encrypted. It is actually the thing people use now, because if you jump through a few hoops, you stopped having to type in a password.

You know what VPNs meant? VPNs meant you didn't have to drive into the office on a Sunday. You could be at home and fix the problem, and hours became minutes or seconds. Everything that we do that really works involves making things more useable and enabling people. Security is giving you permission to do this thing that used to be dangerous.
Security is giving you permission to do this thing that used to be dangerous.

I actually have a lot of hope in the mobility space, because a lot of these mobile environments and operating systems are really quite secure. You hand someone an iPad, and in a year, that iPad is still going to work. There are other systems where you hand someone a device and that device is not doing so well a year from now.

So there are a lot more controls and stability from some of these mobile things that people actually like to use more, and they turn out to also be significantly more secure.

Gardner: Craig, as we're also thinking about ways of keeping people on the straight and narrow path, we're getting more intelligent networks. We're starting to get more data and analytics from those devices and we're able to see what goes on in that network in high detail.

Tell us about the ways in which we can segment and then make zones for certain purposes that may come and go based on policies. Basically, how are intelligent networks helping us provide that usability and security?

Access to data

Patterson: The example that comes to my mind is that in many of the industries, we have partners who come on site for a short period of time. They need access to data. They might be doing inspections for us and they'll be going into a private area, but we don't want them to take certain photos, documents and other information off site after a period of time.

Patterson
Containerizing data and having zones allows a person to have access while they're on premises, within a certain "electronic wire fence," if you will, or electronic guardrails. Once they go outside of that area, that data is no longer accessible or they've been logged off the system and they no longer have access to those documents.

We had kind of an old-fashioned example where people think they are more secure, because they don't know what they're losing. We had people with file cabinets that were locked and they had the key around their neck. They said, "Why should we go to an electronic documents system where I can see when you viewed it, when you downloaded it, where you moved that document to?" That kind of scared some people.

Then, I walked in with half their file cabinet and I said, "You didn’t even know these were gone, but you felt secure the whole time. Wouldn’t you rather know that it was gone and have been able to institute some security protocols behind it?"

A lot of it goes to usability. We want to make things usable and we have to have access to it, but at the same time, those guardrails include not only where we can access it and at what time, but for how long and for what purposes.
Once they go outside of that area, that data is no longer accessible or they've been logged off the system and they no longer have access to those documents.

We have mobile devices for which we need to be able to turn the camera functions off in certain parts of our facility. For mobile device management, that's helpful. For BYOD, that becomes a different challenge, and that's when we have to handle giving them a device that we can control, as opposed to BYOD.

Gardner: Stan, another major trend these days is the borderless enterprise. We have supply chains, alliances, ecosystems that provide solutions, an API-first mentality, and that requires us to be able to move outside and allow others to cross over. How does the network-intelligence factor play into making that possible so that we can say, Yes, and get a strong user experience regardless of which company we're actually dealing with?

Black: I agree with the borderless concept. The interesting part of it, though, is with networks knowing where they're connecting to physically. The mobile device has over 20 sensors in it. When you take all of that information and bring it together with whatever APIs are enabled in the applications, you start to have a very interesting set of capabilities that we never had before.

A simple example is, if you're a database administrator and you're administering something inside the European Union (EU), there are very stringent privacy laws that make it so you're not allowed to do that.

We don’t have to make it that we have to train the person or make it more difficult for them; we simply disable the capability through geofencing. When one application is talking securely through a socket, all the way to the back end, from a mobile device, all the way into the data center, you have pretty darn good control. You can also separate duties; system administration being one function, whereas database administration is another very different thing. One set doesn't see the private data; one set has very clear access to it.

Getting visibility

Gardner: Chad, you mentioned how visibility is super important for you and your organization. Tell me a bit about moving beyond the user implications. What about the operators? How do you get that visibility and keep it, and how important is that to maintaining your security posture?

Wilson: If you can't see it, you can’t protect it. No matter how much visibility we get into the back end, if the end user doesn't adopt the application or the virtualization that we've put in place or the highway that we've built, then we're not going to see the end-to-end session. They're going to continue to do workarounds.

So, usability is very important to end-user adoption and adopting the new technologies and the new platforms. Systems have to be easy for them to access and to use. From the back-end, the visibility piece, we look at adopting technology strategically to achieve interoperability, not just point products here and there to bolt them on.
So, instead of thinking about things from a device-to-device-to-device perspective, we're thinking about one holistic service-delivery platform, and that's the new highway that provides that visibility.

A strategic innovation and a strategic procurement around technology and partnership, like we have with Citrix, allows us to have a consistent delivery of the application and the end user experience, no matter what device they go to, and where they access from in the world. On the back side, that helps us, because we can have that end-to-end visibility of where our data is heading, the authentication right upfront, as well as all the pieces and parts of the network that go into play to deliver that experience.

So, instead of thinking about things from a device-to-device-to-device perspective, we're thinking about one holistic service-delivery platform, and that's the new highway that provides that visibility.

Gardner: Whit, we've heard a lot about the mentality that you should always assume someone unwanted is in your network. Monitoring and response is one way of limiting that. How does your organization acknowledge that bad things can happen, but that you can limit that, and how important is monitoring and response for you in reducing damage?

Baker: In our case, we have several layers of user experience. Through policy, we only allow certain users to do certain things. We're a healthcare system, but we have various medical personnel; doctors, nurses and therapists, versus people in our corporate billing area and our call center.  All of those different roles are basically looking only at the data that they need to be accessing, and through policy, it’s fairly easy to do.

Gardner: Stan, on the same subject, monitoring and response, assuming that people are in, what is Citrix seeing in the field, and how are you giving that response time as low a latency as possible?

Standard protocol

Black: The standard incident-response protocol is identify, contain, control, and communicate. We're able to shrink what we need to identify. We're able to connect from end-to-end, so we're able to communicate effectively, and we've changed how much data we gather regarding transmissions and communications.

If you think about it, we've shrunk our tech surface, we've shrunk our vulnerable areas, methods, or vectors by which people can enter in. At the same time, we've gained incredibly high visibility and fidelity into what is supposed to be going over a wire or wireless, and what is not.

We're now able to shrink the identify, contain, control, and communicate spectrum to a much shorter area and focus our efforts with really smart threat intelligence and incident response people versus everyone in the IT organization and everyone in security. Everyone is looking at the needle in the haystack; now we just have a smaller stack of needles.

Patterson: I had a thought on that, because as we looked at a cloud-first strategy, one of the issues that we looked at was, "We have a voice-over-IP system in the cloud, we have Azure, we have Citrix, we have our NetScaler. What about our firewalls now, and how do we actually monitor intrusion?"
Citrix and Microsoft are helping us with that in our environments, but those are still open questions for us. We're not entirely satisfied with the answers yet.

We have file attachments and emails coming through in ways that aren’t on our on-premises firewall and not with all our malware detection. So, those are questions that I think all of us are trying to answer, because now we're creating known unknowns and really unknown unknowns. When it happens, we're going to say, "We didn’t know that that part could happen."

That’s where part of the industry is, too. Citrix and Microsoft are helping us with that in our environments, but those are still open questions for us. We're not entirely satisfied with the answers yet.

Gardner: Dan, one of the other ways that we want to be able to say, Yes, to our users and increase their experiences as workers is to recognize the heterogeneity -- any cloud, any device, multiple browser types, multiple device types. How do you see the ability to say, Yes, to vast heterogeneity, perhaps at a scale we've never seen before, but at the same time, preserve that security and keep those users happy?

Kaminsky: The reason we have different departments and multiple teams is because different groups have different requirements. They have different needs that are satisfied in ways that we don't necessarily understand. It’s not the heterogeneity that bothers us; it’s the fact that a lot of systems have different risks. We can merge the risks, or simultaneously address them with consistent technologies, like containerization and virtualization, like the sort of centralization solutions out there.

People are sometimes afraid of putting all their eggs in one basket. I'll take one really well-built basket over 50,000 totally broken ones. What I see is, create environments in which users can use whatever makes their job work best, and go ahead and realize that it's not actually the fact that the risks are that distinct, that they are that unique. The risk patterns of the underlying software are less diverse than the software itself.

Gardner: Stan, most organizations that we speak to say they have at least six, perhaps more, clouds. They're using all sorts of new devices. Citrix has recently come out with Raspberry Pi at less than a $100 to be a viable Windows 10 endpoint. How do we move forward and keep the options open for any cloud and any device?

Multitude of clouds

Black: When you look at the cloud, there is a multitude of public clouds. Many companies have internal clouds. We've seen all of this hyperconvergence, but what has blurred over time are the controls between whether it’s a cloud, whether it’s the enterprise, and whether it’s mobile.

Again, some of what you've seen has been how certain technologies can fulfill controls between the enterprise and the cloud, because cloud is nimble, it’s fast, and it's great.

At the same time, if you don't control it, don’t manage it, or don't know what you have in the cloud, which many companies struggle with, your risk starts to sprawl and you don't even know it's happened.

So it's not adding difficult controls, what I would call classic gates, but transparency, visibility, and thresholds. You're allowed to do this between here and here. An end user doesn't know those things are happening.
Also, weaving analytics into every connection, knowing what that wire is supposed to look like, what that packet is supposed to look like gives you a heck of a lot more control than we've had for decades.

Also, weaving analytics into every connection, knowing what that wire is supposed to look like, what that packet is supposed to look like gives you a heck of a lot more control than we've had for decades.

Gardner: Chad, for you and your organization, how would you like to get security visibility in terms of an analytic dashboard, visualization, and alerts? What would you like to see happen in terms of that analytics benefit?

Wilson: It starts with population health and the concept behind it. Population health takes in all the healthcare data, puts it into a data warehouse, and leverages analytics to be able to show trends with, say, kids presenting with asthma or patients presenting with asthma across their lifespan and other triggers. That goes to quality of care.

The same concept should be applied to security. When we bring that data together, all the various logs, all of the various threat vectors and what we are seeing, not just signatures, but we're able to identify trends, and how folks are doing it, how the bad guys are doing it. Are the bad guys single-vectored or have they learned the concept of combined arms, like our militaries have? Are they able to put things together to have better impact? And where do we need to put things together to have better protection?

We need to change the paradigm, so when they show their hand once, it doesn't work anymore. The only way that we can do that is by being able to detect that one time when they show their hand. It's getting them to do one thing to show how they are going to attack us. To do that, we have to pull together all the logs, all of the data, and provide analytics and get down to behavior; what is good behavior, what is bad behavior.

That's not a signature that you're detecting for malware; that is a behavior pattern. Today I can do one thing, and tomorrow I can do it differently. That's what we need to be able to get to.

Getting information

Patterson: I like the illustration that was just used. What we're hoping for with the cloud strategy is that, when there's an attack on one part of the cloud, even if it's someone else that’s in Citrix or another cloud provider, then that is shared, whereas before we have had all these silos that need to be independently secured.

Now, the windows that are open in these clouds that we're sharing are going to be ways that we can protect each one from the other. So, when one person attacks Citrix a certain way, Azure a certain way, or AWS a certain way, we can collectively close those windows.
I want to know where the windows are open and where the heat loss went or where there was air intrusion.

What I like to see in terms of analytics is, and I'll use kind of a mechanical engineering approach, I want to know where the windows are open and where the heat loss went or where there was air intrusion. I would like to see, whether it went to an endpoint that wasn't secured or that I didn't know about. I'd like to know more about what I don't know in my analytics. That’s really what I want analytics for, because the things that I know I know well, but I want my analytics to tell me what I don't know yet.

Gardner: I'm afraid we will have to leave it there. You've been listening to a BriefingsDirect discussion focused on the heightened role of security in the age of global cloud and mobile delivery of apps and data.

We've heard how security concerns increasingly dwarf other architecture considerations, particularly when we take into consideration behavior and the ability to provide a strong and beneficial user experience.

We've learned how the advances in thin clients, desktop virtualization, cloud management services, and mobile-delivery networks are allowing for both increased security and edge apps performance gains.
Learn more about the Citrix Security Portfolio 
of Workspace-as-a-Service, Application Delivery, 
Virtualization, Mobility, Network Delivery,
 and File-Sharing Solutions
So please join me now in thanking our guests, Stan Black, Chief Security Officer at Citrix; Chad Wilson, Director of Information Security at the Children's National Health System in Washington, D.C.; Whit Baker, IT Director at The Watershed in Delray Beach, Florida; Craig Patterson, CEO of Patterson and Associates in San Antonio, Texas, and Dan Kaminsky, Chief Scientist at White Ops in San Francisco. Thanks to you all.

And a big thank you, too, to our audience for joining the Citrix-sponsored business innovation thought leadership discussion. I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator. Thanks again for listening, and do come back next time.

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Citrix.

Transcript of a sponsored discussion on the heightened role of security in the age of global cloud and mobile delivery of apps and data. Copyright Interarbor Solutions, LLC, 2005-2016. All rights reserved.

You may also be interested in:

Wednesday, August 05, 2015

How Localytics Uses Big Data to Improve Mobile App Development and Marketing

Transcript of a BriefingsDirect discussion on how big data helps an analytics company improve data-driven marketing on a variety of platforms.

Listen to the podcast. Find it on iTunes. Get the mobile app for iOS or Android. Download the transcript. Sponsor: HP.

Dana Gardner: Hello, and welcome to the next edition of the HP Discover Podcast Series. I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator for this ongoing discussion on IT innovation and how it’s making an impact on people’s lives.

Gardner
Our next big data case study interview highlights how Localytics uses data and associated analytics to help providers of mobile applications improve their applications -- and also allow them to better understand the uses for their apps and dynamic customer demands.
Become a member of myVertica today
Register now
Gain access to the free HP Vertica Community Edition
To learn more about how big data helps mobile application developers better their products and services, please join me in welcoming our guest, Andrew Rollins, Founder and Chief Software Architect at Localytics, based in Boston. Welcome, Andrew.

Andrew Rollins: Thank you for having me.

Gardner: Tell us about your organization. You founded it to do what?

Rollins: We founded in 2008, two other guys and I. We set out initially to make mobile apps. If you remember back in 2008, this is when the iPhone App Store launched. So there was a lot of excitement around mobile apps at that time.

Rollins
We initially started looking at different concepts for apps, but then, over a period of a couple months, discovered that there really weren't a whole lot of services out there for mobile apps. It was basically a very bare ecosystem, kind of like the Wild, Wild West. [Register for the upcoming HP Big Data Conference in Boston on Aug. 10-13.]

We ended up focusing on whether there was a services play in this industry and we settled on analytics, which we then called Localytics. The analogy we like to use is, at the time it was a little bit of a gold rush, and we want to sell the pickaxes. So that’s what we did.

Gardner: That makes a great deal of sense, and it has certainly turned into a gold rush. For those folks who do the mining, creating applications, what is it that they need to know?

Analytics and marketing

Rollins: That’s a good question. Here's a little back story on what we do. We do analytics, but we also do marketing. We're a full-service solution, where you can measure how your application is performing out in the wild. You can see what your users are doing. You can do anything from funnel analysis to engagement analysis, things like that.

From there, we also transition into the marketing side of things, where you can manage your push notifications, your in/out messaging.

For people who are making mobile apps, often they want to look at key metrics and then how to drive those metrics. That means a lot of A/B testing, funnel analysis, and engagement analysis.

It means not only analyzing these things, but making meaningful interactions, reaching out to customers via push notifications, getting them back in the app when they are not using the app, identifying points of drop-off, and messaging them at the right time to get them back in.

An example would be an e-commerce app. You've abandoned the shopping cart. Let’s get you back in the application via some sort of messaging. Doing all of that, measuring the return on investment (ROI) on that, measuring your acquisition channels, measuring what your users are doing, and creating that feedback loop is what we advocate mobile app developers do.

Gardner: You're able to do data-driven marketing in a way that may not have been very accessible before, because everything that’s done with the app is digital and measurable. There are logs, servers -- and so somewhere there's going to be a trail. It’s not so much marketing as it is science. We've always thought of marketing as perhaps an art and less of a science. How do you see this changing the very nature of marketing?

Everything ultimately that you are doing really does need to be data-driven. It's very hard to work off just intuition alone.
Rollins: Everything ultimately that you are doing really does need to be data-driven. It's very hard to work off of just intuition alone. So that's the art and science. You come out with your initial hypothesis, and that’s a little bit more on the craft or art side, where you're using your intuition to guide you on where to start.

From there, you have to use the data to iterate. I'm going to try this, this, and this, and then see which works out. That would be like a typical multivariate kind of testing.

Determine what works out of all these concepts that you're trying, and then you iterate on that. That's where measuring anything you do, any kind of interaction you have with your user, and then using that as feedback to then inform the next interaction is what you have to be doing.

Gardner: And this is also a bit revolutionary when it comes to software development. It wasn't that long ago that the waterfall approach to development might leave years between iterations. Now, we're thinking about constantly updating, iterating, getting a feedback loop, and condensing the latency of that feedback loop so that we really can react as close to real-time as possible.

What is it about mobile apps that's allowed for a whole different approach to this notion of connectedness and feedback loops to an app audience?

Mobile apps are different

Rollins: This brings up a good point. A lot of people ask why we have a mobile app analytics company. Why did we do that? Why is typical web analytics not good enough? It kind of speaks to something that you're talking about. Mobile apps are a little bit different than the regular web, in the sense that you do have a cycle that you can push apps out on.

You release to, let’s say, the iPhone App Store. It might take a couple of weeks before your app goes out there. So you have to be really careful about what you're publishing, because your turnaround time is not that of the web. [Register for the upcoming HP Big Data Conference in Boston on Aug. 10-13.]

However, there are certain interactions you can have, like on the messaging side, where you have an ability to instantly go back and forth. Mobile apps are a different kind of market. It requires a little different understanding than the traditional approach.

... We consume the data in a real-time pipeline. We're not doing background batch processing that you might see in something like Hadoop. We're doing a lot of real-time pipeline stuff, such that you can see results within a minute or two of it being uploaded from a device. That's largely where HP Vertica comes in, and why we ended up using Vertica, because of its real-time nature. It’s about the scale.
Become a member of myVertica today
Register now
Gain access to the free HP Vertica Community Edition
Gardner: If I understand correctly, you have access to the data from all these devices, you are crunching that, and you're offering reports and services back to your customers. Do they look to you as also a platform provider or just a data-service provider? How do the actual hosting and support services for these marketing capabilities come about?

Rollins: We tend to cater more toward the high end. A lot of our customers are large app publishers that have an ongoing application, let’s say a shopping application or news application.

In that sense, when we bring people on board, oftentimes they tend to be larger companies that aren’t necessarily technically savvy yet about mobile, because it's still new for some people. We do offer a lot of onboarding services to make sure they integrate their application correctly, measure it correctly, and are looking at the right metrics for their industry, as compared to other apps in that industry.

Then, we keep that relationship open as they go along and as they see data. We iterate on that with them. Because of the newness of the industry it does require education.

Gardner: And where is HP Vertica running for you? Do you run it on your own data center? Are you using cloud? Is there a hybrid? Do you have some other model?

Running in the cloud

Rollins: We run it in the cloud. We are running on Amazon Web Services (AWS). We've thought a lot about whether we should run it in a separate data center, so that we can dictate the hardware, but presently we are running it in AWS.

Gardner: Let’s talk about what you can do when you do this correctly. Because you have a capacity to handle scale, you've developed speed, and you understand the requirements in the market, what are your customers getting from the ability to do all this?

Rollins: It really depends on the customer. Something like an e-commerce app is going to look heavily at things like where users are dropping off and what's preventing them from making that purchase.

Another application, like news, which I mentioned, will look at something different, usually something more along the lines of engagement. How long are they reading an article for? That matters to them, so that they can give those numbers to advertisers.

So the answer to that largely depends on who you are and what your app is. Something like an e-commerce app is going to look heavily at things like where users are dropping off and what's preventing them from making that purchase.
Something like an e-commerce app is going to look heavily at things like where users are dropping off and what's preventing them from making that purchase.

Gardner: I suppose another benefit of developing these insights, as specific and germane as they might be to each client, is the ability to draw different types of data in. Clearly, there's the data from the App Store and from the app itself, but if we could join that data with some other external datasets, we might be able to determine something more about why they drop-off or why they are spending more, or time doing certain things.

So is there an opportunity, and do you have any examples of where you've been able to go after more datasets and then be able to scale to that?

Rollins: This is something that's come up a lot recently. In the past year, we have our own products that we're launching in this space, but the idea of integrating different data types is really big right now.

You have all these different silos -- mobile, web, and even your internal server infrastructure. If you're a retail company that has a mobile app, you might even have physical stores. So you're trying to get all this data in some collective view of your customer.

You want to know that Sally came to your store and purchased a particular kind of item. Then, you want to be able to know that in your mobile app. Maybe you have a loyalty card that you can tie across the media and then use that to engage with her meaningfully about stuff that might interest her in the mobile app as well.

"We noticed that you bought this a month ago. Maybe you need another one. Here is a coupon for it."

Other datasets

That's a big thing, and we're looking at a lot of different ways of doing that by bringing in other datasets that might not be from just a mobile app itself.

We're not even focused on mobile apps any more. We're really just an app analytics company, and that means the web and desktop. We ship in Windows, for example. We deal with a lot of Microsoft applications. Tying together all of that stuff is kind of the future. [Register for the upcoming HP Big Data Conference in Boston on Aug. 10-13.]

Gardner: For those organizations that are embarking on more of a data-driven business model, that are looking for analytics and platforms and requirements, is there anything that you could offer in hindsight having traveled this path and worked with HP Vertica. What should they keep in mind when they're looking to move into a capability, maybe it's on-prem, maybe it's cloud. What advice could you offer them?

At scale, you have to know what each technology is good at, and how you bring together multiple technologies to accomplish what you want.
Rollins: The journey that we went through was with various platforms. At the end of day, be aware of what the vendor of the big-data platform is pitching, versus the reality of it.

A lot of times, prototyping is very easy, but actually going to large scale is fairly difficult. At scale, you have to know what each technology is good at, and how you bring together multiple technologies to accomplish what you want.

That means a lot of prototyping, a lot of stress testing and benchmarking. You really don’t know until you try it with a lot of these things. There are a lot of promises, but the reality might be different.

Gardner: Any thoughts about Vertica’s track record, given your length of experience?

Rollins: They're really good. I'm both impressed with the speed of it as compared to other things we have looked at, as well as the features that they release. Vertica 7 has a bunch of great stuff in it. Vertica 6, when it came out, had a bunch of great stuff in it. I'm pretty happy with it.
Become a member of myVertica today
Register now
Gain access to the free HP Vertica Community Edition
Gardner: I'm afraid we will have to leave it there. We've been learning about how Localytics uses big data to improve data-driven marketing for a variety of mobile application creators and distributors.

I'd like to thank our guest, Andrew Rollins, Founder and Chief Software Architect at Localytics, based in Boston. Thank you, Andrew.

Rollins: Thank you very much for having me.

Gardner: And thanks to you, our audience, for joining as well. I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host for this ongoing series of HP-sponsored discussions. Thanks again for joining, and do come back next time.

Listen to the podcast. Find it on iTunes. Get the mobile app for iOS or Android. Download the transcript. Sponsor: HP.

Transcript of a BriefingsDirect discussion on how big data helps an analytics company improve data-driven marketing on a variety of platforms. Copyright Interarbor Solutions, LLC, 2005-2015. All rights reserved.

You may also be interested in:

Wednesday, July 08, 2015

HP BSM and IT Data Access Spur New Business Benefits at Swiss Insurer and Turkish Mobile Carrier

Transcript of a BriefingsDirect discussion on how two organizations have been improving their application’s performance via total performance monitoring and metrics.

Listen to the podcast. Find it on iTunes. Get the mobile app for iOS or Android. Download the transcript. Sponsor: HP.

Dana Gardner: Hello, and welcome to the next edition of the HP Discover Podcast Series. I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator for this ongoing discussion on IT innovation and how it’s making an impact on people's lives.

Gardner

Our next innovation case study panel discussion explores how improved business service management and data access improvements at a Swiss insurance company and a Turkish mobile phone carrier help to spur new business benefits and IT performance issues resolution.

By more deeply examining how applications are performing via total performance monitoring and metrics these enterprises slashed mean time to resolution and later significantly reduced the number of IT incidents.
Track your app's user experience with Fundex
Download the infographic
Fix poor performing mobile apps
To learn more about how to build high confidence that IT disruptions can be managed, and even headed off in advance, please join me in welcoming our panelists, Thomas Baumann, IT Performance Architect at Swiss Mobiliar in Bern. Welcome, Thomas.

Baumann

Thomas Baumann: Hello, Dana.

Gardner: Nice to have you with us. We're also here with Merve Duran, Management System Specialist at Avea in Istanbul. Welcome.

Merve Duran: Hello, Dana.

Gardner: Thomas, tell us about Swiss Mobiliar and what you’re doing to increase the performance of your applications.

Largest insurance company

Baumann: Swiss Mobiliar is Switzerland’s largest personal insurance company. It’s also the oldest insurance company, founded in 1826, and every third Swiss household is insured at Mobiliar. We are number one in household contents insurance.

My role at Swiss Mobiliar is Minister of Performance. I'm responsible for optimizing all the applications, infrastructure, etc.

Gardner: Tell us about the challenges that you’ve had in terms of keeping all of your applications performing well. How many end users do you support with those applications?

Baumann: There are about 4,500 internal users, but we also deliver applications directly to our customers. So that makes a group of users that’s at about 2.5 million people.

Gardner: What requirements have you been trying to meet in terms of better performance and how do you go about achieving that?

Baumann: About three years ago, we had a very reactive service model. We were only listening to customers or users complaining about bad response times, unresolved tickets, and things like that. Additionally, our event console was at the end of its life. So we were thinking about a more comprehensive solution.

We chose HP’s Real User Monitoring (RUM) and HP’s Operations Management i (OMi) to help us decrease our mean time to repair and to obtain a better understanding of end-user performance and how our applications are used by our customers.

Gardner: Thomas, how important is the acquisition of data and the use of that data? Have you changed either your attitude or culture when it comes to being data-driven, as a path to this better performance?

Baumann: Yes. Initially we had very little data, and data that was generated by syntactical measurements. Now, we measure real end-user traffic at all times, at all locations, and from all users, for the top applications that we have. We don’t use it for all applications.

Gardner: Do you have any sense of performance metrics and improvements? How do you measure your success?

Performance index

Baumann: Regarding end-user response times, we created a performance index, comparable to New York Stock Exchange's Dow Jones Index. Calculating the average response times of the most important functions of an application, and the mean time of all these response times, gives us this performance score value.

We started in 2012, and there was a performance score value of 100, just to have a base level where we can measure the improvement. Now, with an important sales application, we're at 220, an increase of a factor of 2.2 in performance.

Gardner: Have you been able to translate that through some sort of a feedback loop or the ability to predict where problems either are or are beginning, so that you can head off problems altogether? Has that been something you’ve been able to achieve?
Track your app's user experience with Fundex
Download the infographic
Fix poor performing mobile apps
Baumann: Yes. OMi helped us to achieve this, because now we're able to detect very small incidents before they start to impact our service. In many cases we can avoid a major incident or a large problem that would lead to an availability problem in our company just by analyzing those very small defects or incidents that are detected by our machines.

Gardner: Before your customers and users detect them?

Baumann: Exactly. Sometimes you tell the customers that they have to do this and this, and they're very surprised because they didn't know there was a problem before I mentioned it.

Gardner: Let’s now go to Merve at Avea. Tell us a little bit about your company, how large it is, and what you’re doing to improve your application’s performance?

Duran: Avea, is the sole GSM 1-800 mobile operator of Turkey and was founded in 2004. It’s the youngest operator in Turkey, and we perform as management at Avea’s IT domain.
Mobile users are much less tolerant to application errors, slow response times and poor usability.

Gardner: What did you put in place and what were you trying to improve upon as you’ve gone to a higher level of performance? How did you want to measure that? How did you want to improve?

Duran: As an example, we have more than 20 mobile applications in Avea for iOS and Android-based mobile devices. We know that these applications get many hits in a day and we know that the response times of these hits play a significant role in the overall user experience.

Duran
Also we know that mobile users are much less tolerant to application errors, slow response times and poor usability. That’s why we needed to manage our mobile application performance. So we are using HP Real and Synthetic User Mobile Monitoring solutions at Avea.

Gardner: Have you been able to measure and determine how that performance has improved? What you’ve been able to use to determine the success of your activities?

Duran: Before this solution, we had almost no end-user data on hand, so root cause analysis was too hard for us and it took long times when a problem occurred. Also we didn't know how many problems were occurring. With this solution, we can do the root cause analysis and we know how many issues are occurred. Before this solution, we only found out if the customers complained. So the mobile RUM and BPM solution are quite important to us.

Metrics of success

Gardner: Looking to the future, Thomas, where do you see things going next? What’s the next plane of improvement when it comes to applications? Where do you see yourselves going next at your organization?

Baumann: For now, we use RUM to analyze response times. What we start to do now is analyze the behavior of the user: How are they using our applications? We can improve the workflow of whole business process by analyzing how the applications are used, who is using them, from which location, etc.

Gardner: And do you see the data that you’re gathering and using, being used in other aspects of IT? Does this have an adjacency benefit in some way, or is this something that you're just using specifically for application performance?
We can improve the workflow of whole business process by analyzing how the applications are used, who is using them, from which location.

Baumann: For now, we use it specifically for application performance, but we see large opportunities to mix these data with other data to get more insight and have a greater overview of how applications are used.

Maybe we can compare it to an airplane. We were flying as a visual-only flight and now we've migrated to instrumental flight. We also have those black boxes so we can analyze how all those measurements developed over the last period, what happened exactly before the crash, or in general how the systems are used and how we can improve it.

Gardner: That's a very good analogy. It's one thing to just get to your destination. Now, you can make that much more scientific and understood. Therefore, you can devise your future based on a plan rather than a reaction. That's important.

I just want to go in one more direction before we end, and that would be the type of applications that you're using. Do you see more of a feedback loop to your developers? You're doing most of your activity in operations, but as we know that the better you design an application, the better it will then perform.

DevOps is an important trend these days. Do you see yourselves as application performance professionals starting to have more impact on the development process of feedback of information to developers, maybe the next generation of an application, or may be for entirely new applications. Any thoughts, Merve?

Quite helpful

Duran: For BPM mobile solution, yes, this is quite helpful for us, because we can use this solution when we develop a new release of an application. So it will be good to test it before new application releases.

Gardner: Thomas, any thoughts about bringing your information and intelligence back into testing or even development itself?

Baumann: For development, it's more difficult. We still develop a couple of applications, but most of them we purchase. So there isn't much direct influence on development. But for testing there are a lot of possibilities.

Gardner: We've been learning about how two organizations have been improving their application’s performance via total performance monitoring and metrics. We've been talking with a Swiss insurance company and a Turkish mobile phone carrier.
Track your app's user experience with Fundex
Download the infographic
Fix poor performing mobile apps
I'd like to thank our guests, Thomas Baumann, IT Performance Architect at Swiss Mobiliar in Bern, and Merve Duran, Management System Specialist at Avea in Istanbul.

I'd also like to thank our audience as well for joining us for this special new style of IT discussion. We've explored solid evidence from early enterprise adopters about how big data changes everything for IT, for businesses and governments, as well as for you and me.

I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host for this ongoing series of HP-sponsored discussions. Thanks again for listening, and come back next time.

Listen to the podcast. Find it on iTunes. Get the mobile app for iOS or Android. Download the transcript. Sponsor: HP.

Transcript of a BriefingsDirect discussion on how two organizations have been improving their application’s performance via total performance monitoring and metrics. Copyright Interarbor Solutions, LLC, 2005-2015. All rights reserved.

You may also be interested in:

Thursday, March 05, 2015

Kony Visualizer Puts Mobile Apps Features Control in Hands of Those Closest to the Business Processes

A BriefingsDirect interview on creating dynamic and engaging user interfaces for mobile apps with drag-and-drop ease.

Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: Kony, Inc.

Dana Gardner: Hello, and welcome to a special BriefingsDirect interview, coming to you from the Kony World 2015 Conference in Orlando.

Gardner
I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host throughout this series of penetrating discussions on the latest in enterprise mobility. We're here to explore advancements in mobile applications design and deployment technologies across the full spectrum of edge devices and operating environments.

For our next innovation interview, we welcome Ed Gross, Kony Vice President of Product Management. Ed is focused on the Kony Visualizer Product, including requirements prototyping, development oversight, release planning, and lifecycle management.

Welcome to BriefingsDirect, Ed.

Ed Gross: Thanks, Dana. Glad to be here. It's an exciting event that we're having here at Kony World. We're in the process of educating our customers on our latest releases in our product portfolio. One that I'm most excited about is the 2.0 release of our Visualizer product, which brings a number of next-generation capabilities with it.

Visualizer is a tool by which you can create engaging and dynamic user experiences on all platforms for mobility, including tablet and desktop as well. What it does is present an opportunity for designers to take back control of the development process of both designing applications and creating rich next-generation user experiences.

Gross
If you look at how applications are designed typically, it's a very rigid process of creating wireframes and mockups and then throwing those materials over the wall to developers. Designers today, prior to the Visualizer, didn't really have a suite of tools that they could  use to create these applications directly using the technology.

Right now, designers create sort of mockups and proxies of that design to hand over to a developer to implement. We thought it would be great if designers had a tool by which they can directly create that user experience in the native and Web channels using the underlying Kony framework.

With Visualizer you can go in with this what-you-see-is-what-you-get (WYSIWYG) environment. It’s actually called WYSIWYM (what you see is what you mobilize). It’s a term that we coined because it’s a unique approach and something we believe to be a new paradigm in designing applications.

What I can do as a designer is just drag and drop widgets onto my forms. I can create dynamic interactions that really showcase the native capabilities that we have with Visualizer. I can then take that design and publish the actual app to the Kony cloud. Then,  using an app on my phone or tablet, I can then download that design directly, look at all the native interactions, review them, and get a feel for the actual application without having to write any code.

This is a true native experience, not some sort of web-based proxy, mockup, or set of wireframes. I'm actually creating the app product itself within Visualizer with this WYSIWYG canvas.

Native capabilities

We provide access to all the native capabilities. For example, I can use a cover flow widget, a page widget, a calendar, or a camera. I get access to all those rich native capabilities, using what we call actions, without having to go down and write code for all these different platforms.

Fundamentally, what this also represents is a collaboration opportunity with business and IT. If I'm a designer working under the marketing arm of an organization or I'm a designer or a developer in the IT organization, by using what we call app preview, I can take this design, publish it to the Kony cloud, and bring it into the shell application that you could download from any of the app stores.

Then, I can review and  write notes on this design. I can send those notes back to the cloud. Ultimately, the Visualizer user can see those comments that I've left across the entire application. They can act upon them and iterate through that design process by republishing that app back to the cloud so that the business user or the developer, the designer, whoever is actually reviewing this application, can annotate on it.

The fundamental principle here is that you are not just creating a set of assets to hand over to a developer. You’re actually creating the app itself. What’s really fundamental is that we're essentially giving all of the power and all of the control back to the designer, so that the designer can finalize this application and then simply hand it over to the developer using Kony Studio.

The developer can take it from there without having to rewrite any of the front end of the application. The developer doesn't need to be concerned with creating all of the user experience components by writing code or creating views. They focus on what they do best, which is hooking that application into back-end services and systems, such as SAP, Siebel, or any enterprise service bus connectors.
What we saw before Visualizer was that most development projects had very large numbers of defects associated with the user experience.

If you want to integrate with a Web service like an XML, SOAP, or JSON service, you do all that in the studio. You don’t worry about writing all the front-end code. You make it production ready, you wire it, and you do the fundamental business logic of the application and the integration with other products.

Because what the designer has given you is already complete, and so it cuts down all those cycles. It also cuts down on defects. What we saw before Visualizer was that most development projects had very large numbers of defects associated with the user experience.

What I mean when I say is that if today you take an application that was developed using other technology and you break down all the defects according to what category they belong in, such as, integration defects or user experience defects, or performance defects, we find that 70 percent to 80 percent of the defects categorically are associated with poor implementation of the user experience.

In that typical waterfall process that I mentioned earlier, there are a lot of gaps We hand those assets over to a developer, and the developer has to make a lot of assumptions in that process. They have to fill in a lot of the holes that the designer may have left, because the designer is not going to make sure that they design and spec out every single tiny component of that application.

What winds up happening is that a developer somewhere in that lifecycle will make assumptions and implement something in a way that doesn't satisfy the requirements of the business. So you have to go through that whole process of designing and developing over and over again.

Rapid iteration

With Visualizer, you have the capability to quickly iterate. You publish that app design, you get feedback from the business, as I had mentioned earlier, and even during the development process, reiterate through that design process. That integration between Visualizer and our studio project is completely bidirectional.

At any point in that development process, you can transfer that application design back in Visualizer, make any adjustments, and then reimport it back into Studio. So your product suite is very well-integrated. At Kony, it’s something that we believe is a true differentiator.

Our core focus is mobility. So we ensure that the developer and designer experience is world class by tightly integrating the entire design and development process and making sure that those two processes are as close as possible to what we call the metal, the underlying channel, and that they can occur in parallel streams. You no longer have to go through sort of a tradition paper-based design process to move forward with implementing your app design.

Gardner: What is specifically new or some of the highlights in Visualizer 2.0 as well as Framework 6.0?

Gross: Historically at Kony, we have supported a broad swath of devices. From 2008, look at all Symbian devices, BlackBerry devices, all the way up through iOS, Android, Mobile Web, and even Desktop Web, Windows, etc. What we did is look at our layout model where we had previously recognized that we're going to push forward to the next generation of application design.
It's focusing on those devices, those smartphones, that can provide that next-generation level of experience that we’ve become used to.

By doing so we introduce the different paradigm to layout your application using what we call flex layout that’s supported on the next generation of what we call Hero devices. It's focusing on those devices, those smartphones, that can provide that next-generation level of experience that we’ve become used to.

If you look at Android, iOS, and Windows devices, that’s our core focus as well as Web and Mobile Web. We really up-leveled the entire experience so you can design very engaging experiences using flex layout. We've also introduced a number of capabilities around animation, so that you can get those advanced animation and dynamic interactions that you become used to in consumer grade applications with Kony.

We've also introduced a suite of APIs around this as well. The developer can create very dynamic experiences, or the designer in Visualizer can create these wonderful experiences using what we call Action Editor to access all of those animation components and a bunch of native components, such as the ability to advanced device level actions like invoke a camera or map widget or send an SMS or an e-mail, all without having to write code.

Gardner: A recurring theme here and in the industry at large is the need for speed, closing the gap between the demand for mobile apps and what the IT organization and the developer core can produce. Is there anything about Visualizer and Framework that helps the DevOps process along. Perhaps it's being able to target a cloud or platform-as-a-service (PaaS) type of affair, where you can get that into production rapidly. How does what you brought to the market now help in terms of speed?

Reducing time

Gross: There are number of things. The first principle here is that we're significantly and seriously reducing the time it takes to get from design to development through this process. We're seeing a 15x or higher improvement in the time it takes to develop the front-end of an application, which is significant, and we believe in that very much. That's probably the most important thing.

There are tools underneath the hood that support that, including the app preview that I’d mentioned that lets you get on the device native without having to go through any of the development cycles. So it’s a drastic improvement.

There's also, a huge reduction in the amount of errors in the process. It also increases your capability to iterate. That is really core. You can create multiple designs and use those designs to socialize your idea, your business process, or what impact that will have on your users upfront.
The first principle here is that we're significantly and seriously reducing the time it takes to get from design to development through this process.

So I don't have to go through an entire waterfall process to discover that my user experience may not be right and may not be an effective use of my information architecture, for example. I'm able to do all that up front. And all this is supported with the underlying cloud infrastructure at Kony. When I publish my app preview, or if I publish this to a developer, it’s all supported within our cloud infrastructure.

To get down to brass tacks, I as a designer can publish my project to the Kony cloud and share it with a developer, what we call our functional previews of that application. That app preview that I’d mentioned is all supported with the underlying cloud platform.

Then, when you look at Studio, our Studio product is highly integrated with our MobileFabric solution, and we’re working in our next release to increase that integration even more. You can invoke our mobile cloud services from our development environment. We're going to be working to merge that entire Studio environment with our Visualizer design components, drastically improving the design and design or develop an integration experience.

Gardner: And to tie this into some of the other news and announcements here at Kony World, this is targeted at many of your partners and independent software vendors (ISVs), new ones that were brought in and the burgeoning cloud of supporters. Is this also what you expected, for ISVs to use to create those ready-to-deploy apps like Kony Sales, or are these for custom apps, or all of the above?

Custom app support

Gross: All of the above. Visualizer, if you look at the lowest level, is really built to support custom app design and development. That’s the traditional core of the Kony technology, the Kony platform stack. We're introducing a new product, Kony Modeler, this month, and that product is actually built on the foundation of Visualizer and our underlying developer framework.

When you design a Visualizer, you're essentially designing either custom applications or our model-driven business applications such as Kony Sales. The configuration of those applications inside of Modeler as a business analyst or business user does is also built on the Visualizer stack. So everything you do is highly visual, and this speaks to the user-centered development methodology that we see now.

User experience-driven applications are the future, and we recognize that at Kony. We put the user experience first, not the data model, not writing other kinds of models. We really focus on driving user expectations, increased performance for B2E applications, increased productivity, and it all relates back to user experience.

Gardner: Before we close out, I just wanted to hammer down a little bit on that ISV community and why they would look to Kony. It seems to me that they're focused on the logic and understanding their industries and businesses.
We put the user experience first, not the data model, not writing other kinds of models. We really focus on driving user expectations.

They don't want to have to rewrite code. They don’t want to be in the platform business. What is it that reduces the risk for an ISV who considers the Kony approach? Perhaps it’s in terms of the number of end-point devices, the ability to write once, run everywhere, the quality and speed issues you brought up. Give me a bit more insight as to why an ISV should think about Kony when going to mobile markets?

Gross: Well there are a number of things that I'll recap. The first one is that you’re greatly reducing the time it takes to get from design to the end product, which is key. Number two, you're able to reduce man-hours in the development process of the front-end experience.

I'd also like to reiterate that, because of our fundamental underlying JavaScript platform, you're able to write once for all these different channels. A fourth point that I'd like to bring up on top of these is our service-level agreement (SLA), which is unique in the industry.

At Kony, we have a unique SLA that says that within 30 days of a new operating system release, we will provide support within the Kony platform. Nobody else does that. We guarantee that support across our ISV channels and our direct customers, so that they don’t have to worry about revving up to the next version of the given channel. We really take care of that. We mask our customers from that, so that they can focus on innovation.

Gardner: Well great. I'm afraid we will have to leave it there. We have been learning about how advancements in mobile applications, design and deployment technologies are bringing new productivity benefits across the growing spectrum of edge devices and operating environments, and we’ve seen how quality, speed, and value are rapidly increasing, thanks to the Kony mobility platform and the new tools like Visualizer 2.0.

So a big thank you to our guest. We’ve been joined by Ed Gross, Kony Vice President of Product Management. Thank you, Ed.

Gross: Thank you, Dana.

Gardner: And a big thank you too to our audience for joining this special series coming to you directly from the recent Kony World 2015 Conference in Orlando.

I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host throughout this series of Kony-sponsored BriefingsDirect enterprise mobility discussions. Thanks again for listening, and do come back next time.

Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: Kony, Inc.

A BriefingsDirect interview on creating dynamic and engaging user interfaces for mobile apps with drag-and-drop ease. Copyright Interarbor Solutions, LLC, 2005-2015. All rights reserved.

You may also be interested in: