The Fast Track blog: How Can a Non-Programmer Learn to Build Business Applications?

Last month’s Wired magazine featured a cover story entitled, “The End of Code.” Its thesis is that machine learning and neural networks will eventually obviate the need for programmers to write code. While it is an interesting thought, we are far from that situation actually happening anytime soon. Rather than seeing the end of coding, I think we are just at the beginning of a new era where coding and business-led app building is becoming more plentiful and exploding. This is the era of the citizen developer who has to carry the water for the rest of the world.

The issue isn’t whether any of us will or won’t code, but how we can do a better job with the coding tools and low-code platforms that we have at our disposal. My Fast Track blog post today talks more about these issues.

Quickbase blog: How citizen developers can manage their own apps better

In the Quickbase blog The Fast Track, many others have written extensively about the rise of the citizen developer movement, whereby everyone can become a developer because of the widespread availability of rapid app development tools. IT professionals have been trained how to manage their app portfolios, and there is no secret to doing this. In this post, I suggest some ways to start thinking about how you can manage and build more capable apps on your own. Building the app is just the beginning of a lengthy process. More on this idea here.

Quickbase blog: How citizen developers can do better with managing their own apps

We have written extensively about the rise of the citizen developer movement, whereby everyone can become a developer because of the widespread availability of rapid app dev tools.

IT professionals have been trained how to manage their app portfolios, and there is no secret to doing this. Here are some ways to start thinking about how you can manage and build more capable apps.

First off, do you need to build a separate app or can you deliver the same functionality with something entirely running entirely on a Web server? While building apps can be cool, it might be easier to set up a URL that your users can access and run the app from their web browsers. Web-based apps can require more skill to understand how to setup the best user experience and appropriate user controls, however. And web-based apps also demand a different skill set than building apps too.

Do you have reliable pool of beta testers? You want to start recruiting people that will give you the best feedback and can identity bugs and other issues before the app gets deployed and used widely. Ideally, they will be users who are forthcoming with their experiences but don’t bury you with numerous and irrelevant email comments. That is often a fine line to walk, however.

How often do you need to update your app? The hard part about app construction isn’t the initial app build, but what happens when your ultimate users get ahold of it and realize 17 new features that they now want as a result of seeing your app. So plan up front for how these updates will happen, how often you intend to do them, who will take responsibility for them and how the updates will ultimately end up in your users hands. Also think about what happens when you have to expire an app or remove it entirely from your portfolio.

Can you build the app with its own security built-in?  The answer should be yes: your users should be able to authenticate themselves and obtain the appropriate access rights to the app without having to rely on external Active Directory permissions or other security apparatus. Also, you should build in a mechanism to protect your data generated or used by the app too.

Do you need separate web, desktop, tablet and mobile versions for your app? If so, choose the appropriate tool that can create apps in those operating systems and form factors. Or focus on one or two versions and stick with them. Learn about responsive Web design to make your webpages more effective and useful to users who are running smaller tablet and phone screen sizes. Also, be sure to test the app with the collection of OS versions that your users are running to make sure it operates as expected. And when Google and Apple come out with new OS versions, make sure you stay on top of these updates and find out if your app still works properly.

As you can see, building an app is just the beginning. But the more you cover these issues up front, the better your app experience will be for everyone.

Quickbase blog: How Much Code Do You Need to Collaborate These Days?

Today we have a seeming ubiquity of the coding generation: rapid application development can be found everywhere, and it has infected every corporate department. But what is lost in this rush to coding everywhere is that you really don’t need to be a programmer anymore. Not because everyone seems to want to become one. But because the best kinds of collaboration happen when you don’t have to write any code whatsoever.

You can read my post about this topic in the Quickbase The Fast Track blog here.

The Evolution of today’s enterprise applications

Enterprises are changing the way they deliver their services, build their enterprise IT architectures and select and deploy their computing systems. These changes are needed, not just to stay current with technology, but also to enable businesses to innovate and grow and surpass their competitors.

In the old days, corporate IT departments built networks and data centers that supported computing monocultures of servers, desktops and routers, all of which was owned, specified, and maintained by the company. Those days are over, and now how you deploy your technologies is critical, what one writer calls “the post-cloud future.” Now we have companies who deliver their IT infrastructure completely from the cloud and don’t own much of anything. IT has moved to being more of a renter than a real estate baron. The raised-floor data center has given way to just a pipe connecting a corporation to the Internet. At the same time, the typical endpoint computing device has gone from a desktop or laptop computer to a tablet or smartphone, often purchased by the end user, who expects his or her IT department to support this choice. The actual device itself has become almost irrelevant, whatever its operating system and form factor.

At the same time, the typical enterprise application has evolved from something that was tested and assembled by an IT department to something that can readily be downloaded and installed at will. This frees IT departments from having to invest time in their “nanny state” approach in tracking which users are running what applications on which endpoints. Instead, they can use these staffers to improve their apps and benefit their business directly. The days when users had to wait on their IT departments to finish a requirements analysis study or go through a lengthy approvals process are firmly in the past. Today, users want their apps here and now. Forget about months: minutes count!

There are big implications for today’s IT departments. To make this new era of on-demand IT work, businesses have to change the way they deliver IT services. They need to make use of some if not all of the following elements:

  • Applications now have Web-front ends, and can be accessed anywhere with a smartphone and a browser. This also means acknowledging that the workday is now 24×7, and users will work with whatever device and whenever and wherever they feel the most productive.
  • Applications have intuitive interfaces: no manuals or training should be necessary. Users don’t want to wait on their IT department for their apps to be activated, on-boarded, installed, or supported.
  • Network latency matters a lot. Users need the fastest possible response times and are going to be running their apps across the globe. IT has to design their Internet access accordingly.
  • Security is built into each app, rather than by defining and protecting a network perimeter.
  • IT staffs will have to evolve away from installing servers and towards managing integrations, provisioning services and negotiating vendor relationships. They will have to examine business processes from a wider lens and understand how their collection of apps will play in this new arena.

 

Welcome to the world of API-first vendors

The latest development to happen with the cloud is what is called API-first or API-based SaaS companies. What this means in layman’s terms is a service that set up to just connect something with something else using well-documented interfaces. It is hard enough to understand what a cloud-based vendor is selling, but generally there is some physical comparison: a disk drive (Dropbox), an email server (Gmail), a word processor (Office 365) or whatnot. But an API-first vendor is almost like selling a package of air. To give you a better idea, here are some examples of these API-first companies:

  • Contentful, which offers an API-based content management system
  • Chartmogul, which has an API for web-based charts
  • Stripe.com’s Atlas has an API-based Internet payments system
  • 18F, a division of the US Government’s General Services Administration, has developed a series of digital services and APIs so that others can access various federally-based data sources
  • Tray.io, who is building various connectors to different web services using a drag-and-drop drawing canvas
  • Bitwage, which offers banking APIs so companies can pay their employees in Bitcoin. (They have been a “traditional” SaaS vendor, adding this API layer to their existing offerings.)

This last example brings up an important point. The truest API-first companies are those that started out with putting together a great API, without regard for an eventual or legacy product or SaaS offering.

These API-first companies are another degree removed from any physical reality, but it is a cool idea nonetheless. Patricio Robles at the Programmable Web was the first that I found to write about this a few years ago here.  But they have begun to become more common, and add to what you could call meta-API vendors, such as Mashery and Apigee, both of whom offer API management functions and analytics for API-first companies and developers. And there are API marketplaces that have sprung up over the years, including ones from Microsoft Azure, Infochimps and others. These latter places will sell access to particular data feeds that you can incorporate into your own apps.

API-first companies all share several common elements:

  • They have no user interface. The idea is for their customers to build their own UI and differentiate based on this value-add.
  • You interact with their product or service via something web-based.
  • The best API-first companies take the effort to show developers how to become productive within minutes of first use. More on that in a moment.
  • Their inherent value is based on their API set. Once you understand this, it is easier to see what they are offering.
  • On the other hand, there is less to visually demonstrate about the product, so it can be difficult to explain to potential customers. And the sales cycle is longer, since a company has to convince both the resident nerd and management staff about the worthiness of the product.
  • Pricing is typically usage-based, such as the number of requests to their APIs.

Back in the day (say five years ago), when you built some whizzy consumer tech company, you built the whizzy thing first and worried about the APIs later when you had gobs of data that other folks wanted to get access to. Witness Foursquare, which was a darling for a brief moment of time, but now they want to leverage all their data via their API to track commuting routes or popular nightspots or other things in their vast database. But what is happening more and more, as Robles says, is “APIs are designed, implemented and documented before the application that will consume them even exists.”

I first came across one of these with Twilio, which plans to go public this year. That is an incredible statement in and of itself, since imagine explaining what an API-first strategy to your average VC: it could easily be a plot point on “Silicon Valley” (the TV show). Twilio now runs major infrastructure for Coca Cola, Uber and EMC, among others. Their idea is to put an API in front of the switched phone network, so your programs could have access to making calls.

About that part about being productive out of the gate. This is a key aspect of this class of products. As I said, the idea is that you want your APIs to connect something to something else. The more integrations of various services you supply, the easier it will be for developers to build these bridges between their program and an existing SaaS product. This is what Contentful did: they have a variety of integrations with existing content management products, such as WordPress and Joomla, so you can import your existing blog posts and images and make use of them within minutes of signing up for their platform. This means an API-first company has to invest time in a solid knowledge base, lots of programming samples, and installation guides to make sure their potential developer customers can figure out how to use their APIs.

Chartmogul had a post here about how few apps will be built completely from scratch in the future. Companies will be able to launch faster, add new functionality easier, evaluate their costs more predictably, and scale more reliability.

Want to join in? There is now an entire website, naturally, to help you get started. Welcome to this brave new world!

Box turns the API world inside-out

You might not have seen the news last week from Box, the online storage service. There are two items. First is about Box’s new developer edition, announced at its annual conference. What is significant is that this is the first time, to my knowledge, that a software developer has made it easier to embed its app inside other apps. Let’s see what they did and why it is important.

Many software vendors have spent time developing application programming interfaces or APIs that make it easier for third parties to have access to their apps or data that they collect. These days it is hard to find a vendor that doesn’t offer an API, and Box has done a terrific job with its own APIs to be sure. They have created a developer community of tens of thousands of people who write programs using them.

These programs make it easy to fax a document from within Box via an Internet faxing service, add digital signatures inside a document, make small changes to a document, and so forth. The idea is to manipulate a document that is inside the Box cloud storage system, so that their cloud can become more valuable than the dozens or hundreds of other cloud-based storage providers that are available. Without access to its APIs, a third party has to first move the document out of Box, make these changes, and then move it back to its repository. That takes time and uses computer resources.

But the developer edition turns this notion on its head, or should I say goes inside the Box. What they are trying to do now is allow apps to use a set of Box features, but doing so inside your own app. Instead of accessing APIs so you can manipulate particular documents, you can make use of Box’s security routines, or storage routines, or other basic functionality, so that you don’t need to invent this functionality from scratch for your own particular app. What are some of the features that are offered? According to the announcement, these include: “full text search, content encryption, advanced permissions, secure collaboration, and compliance.” That is a lot of stuff that an independent software developer doesn’t have mess with, which means that new apps could be written more quickly.

On top of the developer edition, Box also announced its own Javascript libraries that anyone can use to get started on coding some of these features, called T3. They had posted a few snippets of code on this website showing you how you can construct a Todo list. While JS frameworks are numerous, this one might be interesting, particularly in light of the developer announcement.

Certainly, online storage is undergoing its own evolutionary moment. Google is now charging a penny a GB per month for near-line storage, promising to retrieve your files in seconds. Of course, they and other cloud providers are (so far) just a repository, and that is the line in the cloud that Box is trying to draw with these announcements.

If it all works out, we’ll see Box become the center of a new universe of apps that can take collaboration to the next level, because the folks at Box have already built a collaboration environment that they use for their own customers. It is gutsy, because a Box-like competitor could make use of these features and out-Box Box (which is one reason that Box will control who has access to its tools for now).

It could backfire: developers are a funny bunch, and many of them like reusing someone else’s code but maybe not to the level that Box requires. It certainly is a different model, and one that will take some getting used to. But the proof is in the pudding, and we’ll see in the coming months if anyone’s code turns out to be noteworthy.

The cashless customer is now king

I wanted to bring in my winter coat to the cleaners (maybe optimistically a week or so too soon) and in cleaning out the various pockets I came across some cash and a receipt dated last December. I thought about how long it has been since I have actually used cash.

What a difference from my dad’s world. My dad dealt with millions of dollars every day as a comptroller and always carried a wad of cash worthy of a mafia don. I still have his money clip somewhere. I put the few bills on my desk as a reminder and then thought about how the world has changed. Paying in cash is certainly becoming less common.

Most of my customers still pay me with paper or electronic checks, a few go through Paypal and every once in a while I get asked to accept credit cards. Now there are so many options for accepting Internet payments and two good ones that you might not know about. One is Simplify.com, which is part of MasterCard and has done a lot of work in developing their payment gateway. The other is Stripe.com. Both charge a bit less than 3% per transaction but have no other recurring fees. That is a lot less compared to just a few years ago, when you had to pay monthly processing and other annoying fees to have a merchant account. Stripe even accepts non-dollar currencies, including Bitcoins, and converts them into dollars for you.

aaa2Both Stripe and Simplify offer a variety of APIs, tools, code samples, and connectors to various payment-related apps. I like the way Simplify arranges its code samples, as you can see in this screenshot.

Stripe has more third-party plug-ins than Simplify, including more than a dozen just for WordPress. Both offer documentation on webhooks, which are URLs that can interact with short pieces of code for particular event notifications, although I think Stripe has better documentation. Both also support OAuth for consolidated signons to other SaaS apps without having to store your credentials. Finally, both can operate in either a testing or sandbox mode so you can try various things out, and then go live with actually processing real transactions.

We have come a long way with online payments to be sure. Both services allow you to build in payment processing to your website in ways that were unthinkable just a few years ago. I think my dad would be just as amazed as I am.

ITWorld: What is the value of a data dashboard?

When it comes to convincing your boss of the value of a data dashboard, nothing works better than when you can save some dollars as a result of a trend that you visualized. This is what one of the data-driven marketing staff did for the Texas Rangers baseball team; their dashboard saved about $45,000 in annual costs.

 

The Rangers are big fans of data dashboards, and they should be: dashboards can spot trends, communicate a particular position to management, or call out trouble spots while you can still doing something about it. I heard from Sarah Stone, who is the marketing and advertising manager for the team and also a Big Data junkie.

 

Stone gave a talk at the annual Tableau Software user conference held earlier this month near their Seattle headquarters; I also met with her separately to get more information about her situation. She told me that she was new to the team’s front office (as they call the folks who don’t actually get into uniforms) and was looking to support one of her colleagues who were involved in a discussion with one of their long-time contractors. Their contract was up for renewal and thanks to Stone’s help they were able to produce a visualization that was used to shave off $45k from the contract. This was a great example of how data science could be used to benefit other marketing and sales efforts.

 

Tableau Software is big into dashboards and I came across many of them during their conference. One issue is that they can easily overpower management, who may be used to squinting at a series of spreadsheet figures. “The first time you show your boss a visualization can almost be a magical moment, it can really reveal things in your data that weren’t very obvious before,” said a data analyst at a Defense Department contractor I met at the conference. At another session, Vaidy Krishnan, an analyst from General Electric’s Measurement and Control group said, “Dashboards are just a starting point for a discussion. You can’t get everything right out of the gate but using them helps you ask critical questions.”

 

Stone is the person who has to decide on television and other media advertising buys for the baseball team and has to spend wisely: she needs to know which games are selling slowly, or what kind of ticket buyers are likely to come to which games. To do this, she uses Tableau Software’s tools and connects to several public and private data sources to produce her visualizations.

 

For example, she wanted to see whether the Dallas market was saturated with professional sports teams and used census data to compare the raw number of seats for each metropolitan market. Not surprisingly, St. Louis (as shown below) showed lots of rabid sports fans (something that I can attest to, after living there for several years) while Dallas still had room to grow.

 

Another analysis looked at how they could save money on their corporate cell phone bills. She was able to find several staffers who were frequently on scouting trips out of the country, and try to adjust their plan to handle more international minute usage. “We also saw a spike in the bills during August but then figured out that was when the whole team was in Toronto for a series of games, so it made sense.”

 

Her work on tracking ticket sales is an example of how a typical Big Data analysis session goes. Often, you don’t know what questions to ask or how to go about collecting the data that you’ll need for your analysis. At the conference, Neil deGrasse Tyson, the director of the Hayden Planetarium in New York, gave one of the keynotes where said the “really difficult thing was formulating questions that we are currently too stupid to ask now, let alone understand the answers to.” He gave as an example if someone from the 1700s were to try to figure out when the next asteroid would hit the Earth. No one from that era would have even asked such a question.

 

Stone admits that she often will run several queries and create several different data dashboards before she figures out what she is trying to accomplish. This is very typical behavior in the Big Data world. She is in the process of putting together an interactive seating chart of their stadium, showing characteristics of which seats were purchased by season ticket holders, what concession sales happened on particular games, and whether promotions or team performance helps to fill seats.

 

Not surprisingly, all those bobble-head doll giveaways do drive ticket sales. “And a post-season win translates into three seasons of subsequent increased sales,” she told me. Some of the data is downloaded from StubHub, the secondary ticketing retailer that Major League Baseball helped start. She is also working with the local Southern Methodist University business school students as interns to help integrate regression models based on R.

 

“Our sales department knows what they are doing when it comes to selling tickets, but when it comes to looking more globally at this process and how it coincidences with other variables such as team performance or the weather, they need help.”  For example, her analysis can predict attendance so the team can better staff the stadium for more crowded games.

 

Before she started, the marketing department had to make frequent requests for reports from the box office, and these reports didn’t reflect real time sales either. “Producing real-time, holistic visualizations is the holy grail. We’ve always been able to obtain real time data, but it hasn’t been all that accessible and only a few people could gather that information,” she told me. “Our seat inventory is very perishable, and if I can design a discount program or arrange for an ad media buy for the next day’s game, it can have a big impact. Having a stale report doesn’t really help if you are trying to move thousands of tickets. We need to know how sales are trending because once the game is over, we can’t sell those tickets anymore.”

Ironically, when she started with the Rangers last year, Stone knew virtually nothing about baseball—she jokes that she didn’t even know the difference between an out and a hit then. (Now her game knowledge has improved to the point where she accurately scores each game she watches.) She came to the Rangers from another competitive landscape: professional politics, where she used data analytics to help focus media buys and to track what the other candidates were doing. “Really, politics and baseball are very similar,” she told me. “Both marketing groups have no control over the quality of the product you are promoting and you still have to get people to either come out to vote or to go to the game. Data is still data.”

Everyone is in the software business

Everyone is in the software business You may not know it, but you are in the software business, no matter what your actual business may appear to be. It doesn’t matter what you produce, whether you are a “bricks and mortar” retailer or a “guys in trucks” distributor, software is where you are going to end up.

virgin-america-logo-1Why is everyone in the software business? Simply because software is become the lifeblood of so many decisions on what a business makes, how it is sold, and how customers are kept happy. All the interesting business operations are happening inside your company’s software. Software is where you can find out if your customers are going elsewhere, if your profits are coming from some new markets, and if your employees are helping or hurting your overall reputation.

As an example, the airline Virgin America has billions of dollars invested in planes and the people that fly them, but their brand lives and thrives based on their mobile and web experience. That experience is all because of the airline’s booking software, and understanding what is happening with that software will make the difference between success and failure for the airline.

Take as another example a national food service distributor. Their business is getting food into trucks, and then getting those trucks to restaurants and other institutional caterers and retail kitchens. The company has had an ecommerce business for the past decade, and a pretty significant one at that. But lately their customers have been shifting their emphasis from calling their sales representatives with the weekly orders and wanting to do more online. The distributor needed to scale up their online business, and also be more data-driven. Rather than letting their truck drivers or regional offices make decisions about distribution, they wanted a single view of their business, and use the changes in their orders and other data to fine-tune their deliveries. This food distributor is now firmly into the software business.

What is driving everyone to software? Several things.

  • The cloud. The days where you had to build your own servers and data centers are over. Post Holdings is probably the largest cloud-only company, and their revenues are in the billions.
  • Everyone wants an online storefront. Just like the food distributor, even the most basic industries are finding out there is value is selling their stuff online.
  • Big Data is getting more familiar. You can now find Hadoop clusters in many traditional Fortune 500 companies. The IT staffers at the giant retailer Sears eventually spun off a side business in helping others get started with Big Data.
  •  Customer experience is king. One way that businesses can differentiate themselves is by paying attention to their customers. This isn’t anything new: Nordstrom’s department stores have been doing this for decades. What is new is a range of software tools to help figure this stuff out.

I will have more to say about this topic, right now I am working on a white paper for a client that will dive into this deeper. Check back here in the fall when I can post a link to it.