Blog :

Programmatic Native Advertising

Programmatic Native Advertising

We’ve all had the experience of mobile pages loading almost instantly, littered with gaping holes in the text. After a few seconds, we see those holes filled by an advertisement that finally drops into place. A significant reason for this lag-time is the different file types used to create those mobile pages. Often times, when that ad finally appears, it may not quite “fit” the page.

By its very nature, mobile content has to be powerful. It needs to be nimble on delivery. To meet the needs of the mobile user experience (UX), Google created the open-source format, AMP (Accelerated Mobile Pages). Their end-purpose is to load mobile data quickly regardless of the mobile platform.

Users expect close to an immediate load, but studies show that “an alarming 77% of (mobile) publisher’s today, their web pages take more than 10 seconds to load…and the average is actually 19 seconds.” The same studies show that publisher’s “who can deliver this content in five seconds or less earn twice as much (search volume) as those at the average point.”
Paul Muret VP, Display, Video & Analytics, Google

Google announced the AMP format in December 2015; soon mobile screens were rapidly filled with new content. This covered the main content of the mobile pages. Unfortunately, the advertisements were still left dragging with a format that took longer to load, thus creating the gaping holes.

The solution was Google’s release this month of AMP for Ads. This format allows for advertising content to load at the same rate as the page content. Google also announced AMP for landing pages. This way, all mobile content is delivered seamlessly without the time gaps.

What about the mobile UX?

This technology translates to a cleaner transmission of page elements. But how do you tackle the issue of merging content, context, and UX? The answer is the Programmatic Native Advertisement in their DBM (DoubleClick Bid Manager). In short, Google has created an environment where advertisements are built from scratch to maximize each individual page load.

Before now, the artwork for a mobile ad was selected from amongst three or four established graphics previously built by a graphic artist. As an ad was called up, the best fitting graphic was chosen for that request/platform. Now, when an advertisement is requested to fill a unique audience/seller/publisher combination, the ad is crafted from scratch to fill that request. Each of the elements of those artworks is individually uploaded. The computer decides the best selection, configuration, and layout of those separate elements, relative to the audience. This programmatic approach allows for a fluid display of content across all campaigns and platforms.

Think of it this way – currently, a graphic artist may use a graphic design program to craft a polished graphic. That artwork may consist of 30 or 40 layers of visual elements. When they’re finished, a couple of polished elements are presented as options dependent upon the needs of the ad. Now imagine taking a collection of those graphic elements and tossing them all into a bowl. Programmatic Native Advertisement will select a specific cluster of those elements to create a new graphic, for each page load. The ad will be built to fill the screen, platform, size, device, all built in context to the user.

The beauty in this development is not so much the uniform data transfer rates, as it is the context in which the advertisements are experienced. The ad’s form and function will be subordinate to the mobile user experience (UX). This technology adds a unique flexibility to advertisements in the mobile universe. Gone are the days of guessing how to best craft your mobile message. If you have questions about addressing your audience, contact Colure’s development team.

What is the difference between a web app vs a mobile app?

What is the difference between a web app vs a mobile app?

In a day when there’s an app for almost every need or function, companies providing these digital problem solvers often ask “do I need to develop a mobile application just to provide a simple function?” The answer is no. An application that operates on your web browser may be the answer. Web apps have filled the void to provide those functions. Web apps provide the feel of a mobile app with the power, accessibility, and stability of web-browser.

From a technical viewpoint the web is a highly programmable environment that allows mass customization through the immediate deployment of a large and diverse range of applications, to millions of global users.” – Acunetix

One user defined the differences as:

a website is defined by its content, while a web application is defined by its interaction with the user. That is, a website can plausibly consist of a static content repository that’s dealt out to all visitors, while a web application depends on interaction and requires programmatic user input and data processing.” – kerrek-sb 

Defining you needs is the first step to deciding how to proceed. Many variables will affect your selection. Here are a few ideas to keep in mind as you progress:

  • Design with the user in mind. This decision may mean thinking beyond your personal opinions. An aesthetically pleasing won’t satisfy customers if it’s hard to use. Think simple. Sensory overload with images and options will only turn customers away. Try to keep the app’s main functions first, with more advanced settings tucked away. Ask yourself: if my app only did one thing, what would it be? Build off of the main focus, adding additions only where it enriches the customer’s user experience (UX).
  • Balance personal creativity with traditional functions. Colors have meaning and emotional responses. Choose a palette that represents your goals and functions. Experiment with different color schemas before the app is released. The color blue may give your app a calming feel and is the choice of many social media giants. A red color scheme may elicit strong emotions like passion or urgency but also serves as a warning color. Decide how you want your users to feel when they use your app.

It’s important to beta test your app. Try to seek a large group of beta testers to help define the strengths and weaknesses of your app. The benefits of a solid beta-test have been well established. It may be a cost, but an untested app will lose profits in the future. Your goal should be to have the best performing, most efficient app in your field. Otherwise, why would customers choose yours over a competitor?

Develop your app to fulfill the needs of your clients and to answer those questions you seek to conquer. Proceeding with the proper format for your app will facilitate greater function for everyone involved with the process.