What Blipp Actually Was
Blipp was an AR creation platform launched in 2014 by athena (later acquired by SAP). It let you build augmented reality experiences through a visual editor rather than writing code from scratch. You pointed your phone at a marker — a printed image, a logo, anything — and a 3D model, video, or interactive overlay would appear on screen. That was the whole premise: drag-and-drop AR for people who didn't have a Unity background. The platform generated an SDK you could embed into iOS or Android apps, or you could publish experiences directly through their cloud. For brands doing marketing activations, trade show demos, or product packaging, it was one of the faster ways to ship an AR experience before something like Spark AR or Lens Studio became dominant.
The Ultimate Guide To Blipp Revolutionizing The World Of Augmented Reality
I spent about two years building campaigns with Blipp for various clients. Here is what it actually felt like to work with it day to day, not what the homepage promised. You started by creating a Blipp account and adding a new Blippchar — that was their name for an individual AR scene. You uploaded a target image as the tracking marker, then layered assets on top. 3D models in .dae or .obj format, textures, video files, sometimes simple interactive buttons that triggered animations or opened URLs. The editor had a timeline, so you could keyframe animations: a model spinning into place, fading in, moving to a position. Transitions were basic but functional. You set the behavior when the marker was detected, lost, or re-detected. Then you published and got a shortcode you dropped into your app or used in a hosted web experience.
The thing nobody mentions upfront is how much your target image matters. Blipp used image recognition to lock onto the marker. A low-contrast photograph of a white wall on beige carpet will fail every time. A high-contrast, detailed logo printed on matte paper works fine. I learned this the hard way at a client launch in 2017 where we had printed the marker on glossy brochure stock and the AR would only trigger under direct fluorescent light at exactly the right angle. We switched to a matte card with higher contrast and it worked immediately.
Get the Full Details
Building Your First Experience
Log into the Blipp dashboard and create a new Blippchar. Upload your target image — I usually kept it under 2MB and at least 1000 pixels on the longest side for reliable tracking. Place it in the preview window so the editor knows what you are tracking. Next, add an asset. For 3D models, you needed to export from Blender or Maya with materials baked into the texture if you wanted them to show up correctly. Blipp did not run real PBR shaders. If you needed realistic lighting, you baked it into the texture itself. This was a limitation that tripped up a lot of people coming from game engines. Video assets worked better. You could drop in an MP4 and set it to loop, autoplay, or trigger on tap. I used this often for product demos where a 3D model was overkill but you wanted to show something moving. File size mattered here too. A 50MB video on a marker experience would tank load times on 4G. I kept videos under 15MB and used H.264 encoding at 720p as a rule of thumb.
For interactivity, Blipp had a limited action system. You could set up tap events that played animations, changed visibility, or navigated to a URL. It was not a full scripting environment. If you needed complex logic, you built the AR shell in Blipp and handled the heavy lifting in your own app code, passing data back and forth.
Integration Options
There were two main paths. The first was using Blipp as a standalone hosted experience. You embedded their viewer in a mobile web page or shared the link directly. This was fast to set up but gave you less control over the user journey. The second option was integrating the Blipp SDK into your own native iOS or Android app. This meant more development work but also meant you could handle authentication, analytics, and deeper customization. For a retail client I worked with, we went the SDK route. The host app had a loyalty login, and we passed the user ID into the Blipp session so we could tie AR interactions back to individual accounts. That required reading the Blipp SDK documentation, which was adequate but not thorough. The API reference had gaps, especially around the event callbacks. I spent a few hours reverse-engineering the callback behavior by logging to console until I understood the sequence.
Performance And Platform Limits
Blipp worked on iOS 9 and above and Android 4.4 and above, which covered most devices at the time but left out a segment of older Android hardware. Tracking performance varied significantly between devices. An iPhone 6s would lock onto a marker reliably. A mid-range Samsung from the same era could take several seconds to recognize the same image, if it recognized it at all. Scene complexity was the real bottleneck. Each 3D model added draw calls. Each texture added memory pressure. I had one project where the experience worked fine on iPhone but crashed consistently on certain Android devices because the texture memory exceeded what the GPU could handle. The fix was reducing texture resolution from 2048x2048 to 1024x1024 and simplifying the model polygon count from around 40,000 triangles to roughly 12,000. It still looked acceptable on a phone screen at arm's length.
What It Got Wrong
Blipp never supported plane detection or surface understanding. You could not place a virtual object on a table or floor. It was purely marker-based. If your use case required that kind of spatial AR, Blipp was the wrong tool and you should have been looking at ARKit, ARCore, or Vuforia instead. This was a fundamental architectural limitation, not something you could work around. The analytics were basic. You got impression counts and tap-through rates, but there was no deep session tracking or heat mapping. For a quick campaign check, it was enough. For measuring actual engagement quality, you needed to layer in your own tracking. Perhaps the most important thing to know is that Blipp as a standalone platform has been sunsetted. SAP athena discontinued it. Existing experiences may still work through archived SDK versions, but you will not get new feature updates or support. If you are starting a project today, you should be evaluating Niantic Lightship, Spark AR, Lens Studio, or 8th Wall depending on your needs. The concepts I described here still apply, but the tooling has moved on.
A Quick Reference For Migration
If you have existing Blipp projects you need to maintain or port, start by auditing your target images. Modern AR platforms handle tracking differently, so you may need to recreate or replace your markers. Export your 3D models to the format your new platform requires — glTF is the current standard and was not well-supported in Blipp. Rebuild your animations in the new editor; Blipp's timeline was unique enough that there is no direct import path. The biggest time sink will be the integration layer if you were using the SDK. Blipp's event system does not map cleanly onto ARCore or ARKit. Plan for a week of rewrite work even for a simple campaign experience. Budget accordingly.
Final Notes
Blipp was not the future of AR. It was a bridge technology that made marker-based AR accessible to a broader group of marketers and agencies who did not have dedicated developer resources. It worked well within its constraints. Outside those constraints, it fell apart quickly. The marker dependency, the lack of spatial awareness, the performance ceiling on complex scenes — these were hard limits that no amount of UI polish could overcome. If you are looking at legacy Blipp content, it is worth understanding what was there and why it behaved the way it did. That knowledge transfers directly to evaluating whatever comes next. The workflow patterns are similar even if the underlying technology has changed completely.
