VLog: Situational App vs Situational Applications

What is a situational application?
From wikipedia: “a situational application is “good enough” software created for a narrow group of users with a unique set of needs. The application typically (but not always) has a short life span, and is often created within the group where it is used, sometimes by the users themselves.”
Though most packed tools offer some level of customization, they are designed to give each user a consistent experience. An undifferentiated experience. When you adopt a package, you change your operations to fit the package. If you do something differently in your business, you experience a gap—the packaged app gap.
“If you do something differently in your business, you experience a gap—the packaged app gap.”
Situational Applications are definitionally different. They rarely displace a big packaged tool but they bridge the packaged app gap. You do business your way. You build Situational Applications to support your way. A differentiated way. Hopefully a way that gives you competitive advantage and makes your operational lives easier. In the past, businesses used spreadsheets, MS Access, Lotus Notes, and Sharepoint to assemble Situational Applications and many of these still live on in the daily lives of business users.
The next generation, what management consultant, Ian Tomlin, calls the 4th Generation, is meant to use modern means to bridge the packaged app gap. But for years, the industry for situational applications platforms has languished in spite of analysts predictions that the space would generate $700 million by 2013. The need is there. People tell me this daily. So why no action? There MUST be a missing link.
“Mobile is the missing link, because you are sometimes at your desk but you are ALWAYS mobile.”
  1. Situational Apps are mobile.
  2. Situational Apps are social.
  3. Situational Apps are multi-device, multi-channel, multi-user.
So to move from Situational Applications to Situational Apps you must think mobile-first. Think you aren’t ready for Mobile? Even if you are not today, we guarantee that you will be tomorrow. So, why not future-proof your solutions and think mobile-first even if you start using your apps in a browser. Point.io’s service makes it easy to get started with Situational Apps that can grow with your business—apps that bridge the packaged app gap and let you get on with your business.

Vlog: Document-centric Apps for Workflows

Video Log Entry: Why document-centric apps are important and how the APIdoc Plugin for App Composer makes it easy to build Situational Apps that work for your business.

Our drag-and-drop component allows for simple integrations for file-based services, both behind-the-firewall and cloud-based. It empowers App Composers to snap together lightweight, cloud-hosted workflow apps intended to drive collaborative processes in a mobile world. It will give mobile developers a way to engage users in multi-step, multi-party processes that need to juggle documents across time, device, and location.

Today, we released the APIdoc Plugin for App Composer to beta developers. The APIdoc Plugin for App Composer is an drag-and-drop enabled Fact component that allows for simple integrations for file-based services, both behind-the-firewall and cloud-based. It empowers App Composers to snap together lightweight, cloud-hosted workflow apps intended to drive collaborative processes in a mobile world. It will give mobile developers a way to engage users in multi-step, multi-party processes that need to juggle documents across time, device, and location.