Rogerthat Platform
Contents
Rogerthat Platform: easy to use realtime interactive communication
- Message based automation
- Between your organization and your users (both organization members and external people)
- On the smartphone or desktop of your users
- Graphically rich full-screen messages
- One-click interactive responses
- Very simple to use
Rogerthat offers you

- An organization-to-person interactive messaging solution, which is much richer than email, SMS text messaging or instant messaging
- A new paradigm for interactive smartphone communication without having to build a smartphone app yourself. You should use the Rogerthat platform because it is much more flexible, less complex, and much lower time to market compared to traditional technologies such as building a native app or an HTML5 app.
- Instant deployment of your new message flows or look & feel. No need to wait for appstore approval or for users reluctant to app upgrades.
- A platform for non-technical users to define interactive message flows, to launch them or link them to a QR code, and to analyze the results.
- A platform for programmers to integrate interactive smartphone communication with your existing backend systems.
Rogerthat toolset
- Message Flow Designer to design entire communication flows using drag & drop
- Message Flow Runner and Reporter to launch message flows and aggregate or analyze the results
- QR Code Designer to design branded and visually pleasing QR codes, and link them to a message flow which is started when the QR code gets scanned
- Message Designer to design branded and visually pleasing interactive message
- Rich cross-language programming API to integrate with your systems
Which technical challenges does Rogerthat solve for you?
- Cross platform: iPhone, Android, web browser, BlackBerry (coming soon), Windows Phone (coming soon)
- Multi device: realtime synchronization of messages over all your devices or web browsers
- Reliable messaging using your unreliable smartphone network connection
- Cross platform push technology
- Minimal data transfer to maximize performance and minimize end user mobile data cost
- Attach rich alarm sounds to messages
- Ability to remotely update the status of a message, for example show what other users answered or seal the message
- Combine the flexibility of HTML for look & feel, with native interactive widgets for maximal usability
- Very fast time to market:
- Get smartphone presence in days
- Update business logic or look & feel in hours
- No need to upfront invest $100K to develop your app for multiple smartphone platforms
- No need to requalify your app each time there is a mobile operating system upgrade
- No need to wait days or weeks to get approved and publish your app in Apple Appstore
- No need to wait for users to upgrade your app.
- Very simple integration with your backend systems
- Very secure, very reliable, very performant
How does Rogerthat compare to other technologies?
| Rogerthat | SMS text messaging |
Instant messenger | Native mobile app |
Mobile web | ||
| User interface | HTML + native full screen |
HTML | Non graphical | Non graphical | HTML + native full screen |
HTML full screen |
| User interactivity | Full | Minimal (secret URL) |
Minimal (SMS codes) |
Minimal (unstructured) |
Full | Full |
| Push technology (incoming messages) |
Yes | Yes | Yes | Yes | Yes | No |
| Alarm messages | Yes | No | No | No | Yes | No |
| Always authenticated | Yes | Yes | Yes | Yes | Possible | No |
| Spam Protection | Opt-in model | Spam filters | Spam filters | Possible | - | - |
| Read and reply offline | Yes | Partially | Yes | No | Yes | No |
| Design and run message flows | Yes | No | Yes | No | No | No |
| Flexibility (How fast update business logic) |
Hours | - | Days | - | Weeks (appstores + user upgrades) |
Hours |
| QR code support | Yes | No | Yes | No | Possible | Yes |
| Support for private community | Yes | No | No | Yes | Yes | Yes |
| Support for private label | Yes | No | No | Yes | Yes | Yes |
| Multi-platform | Yes | Yes | Mobile phone only | Yes | Expensive | Yes |
| Multi-device synchronization | Yes | Yes | No | If both devices online | Complex | Complex |
| Delivery notification | Yes | No | No | Yes | Yes | No (push not supported) |
| Remotely updateable message status | Yes | No | No | No | Yes | Only synchronous |
Rogerthat Engineering Principles
- Multi-device: every device accessing the cloud has its own idiosyncrasies. Desktops and laptops are devices for consuming rich and interactive cloud user interfaces through a reliable network connection. Mobile phones are great always-on personal notification devices but terrible text input devices. Moreover their network connection is unreliable and often slow. Tablets are cool for consuming content, are reasonably useful as an input device, but users do not always carry them along, unlike their mobile phone. Finally, clouds need a rich but simple API to allow programmatical access to a service.
- Ubiquitous access: People use their laptop at work, check their smartphone during dinner, use a tablet in the couch. They want to pause any kind of cloud operation on one device, and resume on another device. The cloud must deal with this.
- Cross-platform: you access the cloud using a browser, a desktop application, a small-screen mobile device, a tablet, an API. Plenty of mobile operating systems and vendors are competing in the market, reminding us of the early days of the PC. At Mobicage we deploy codebase reduction techniques to minimize the amount of work to support multi-platform. We bridge both the language/OS barrier, the fundamental differences in network availability and performance, and the different security threat model.
- PAAS: we strongly believe in Platform-As-A-Service. Instead of building full-stack complex deployments, we use and advise using PAAS solutions such as Google App Engine, Amazon Web Services
- Reliability, Availability: Your data is safeguarded in the cloud. There are no assumptions on the clients you use to access the cloud. They can disappear at all times. They can break down, crash, be stolen or be hacked. Such an event must not cause you to lose data or to get into an inconsistent transaction state.
- Scalability: When a cloud service becomes popular, the number of users and the according server load grows exponentially. A good cloud architecture must cope with this. Stateless request handlers, smart caches and NoSQL techniques help to design scalable software services.
- Security: our solutions offer the highest degree of security. It is clear that browser-based SSL cannot be considered secure anymore. Devices accessing the cloud must use the SSL protocol in a non-conventional setup.


