One framework for all your HTTP needs.

By replacing your app’s HTTP request calls with the ones from HttpSmartCache SDK’s, you go from 2 seconds to 0.002 seconds response time. Then, relax.

Remove loading messages from your app

Because nobody has time to loose: We take care of the performance users came to expect. And leave you free to focus on your core business.

Apps. The way they should be: Simply Fast.

Back end logic and API’s stay the same. Install HTTPSmartCache and give it a turbo engine.

Less friction between user and content

A long-lasting relationship depends on the quality of each encounter, which is also heavily influenced by how the app performs. An application that looks stunning but performs poorly can damage integrity. Users quickly notice software that is slow or likely to break (whether because of downtime, network failures, etc.), and this impairs both usage and brand perception. Users expect an app to be fast and responsive. If it’s not, it will get poor reviews, lower ratings and lower adoption numbers. Below are some advantages of using HTTPSmartCache:

Easy Integration with Existing Systems

Easy Integration with Existing Systems

Get Return Over Investment in no time. With minimal setup, any RESTful system can take advantage HTTPSmartCache. SSL and  batteries included.

Cross-platform support (mobile and back end)

Cross-platform support (mobile and back end)

  • Supported on all major mobile platforms
  • Native iOS, Android, Windows, OS X, Linux and more.
  • Back end programming remains the same
Smart  Loading

Smart Loading

Smart-loading mechanisms, first load visible content and then move on to content below the fold. This technique reduces the user’s waiting time and thus makes for a smoother experience.

Better Performance, Lower Operational Costs

Better Performance, Lower Operational Costs

Because the number of http requests are drastically reduced on the wire, the load in the back end decreases. This trend impacts the bill at the end of the month. With less computer instances and more money, it might be the right time for a vacation.

No learning curve for developers.

No learning curve for developers.

Because HTTPSmartCache works with your existing system, there’s nothing to learn. Simply install and use (see integration section at the end of the page).

Users want immediate access to exclusive data.

Users want immediate access to exclusive data.

The perception of performance is based on start-up time, page-loading behavior, smoothness of transitions and animations, errors, and waiting times. What have you done to reduce waiting time?

Performance Supports Brand Differentiation

Every product encounter affects the brand perception. Users are looking for the best tools to enhance their lives. To attract a significant user base in a landscape that is becoming more populated each day, a mobile app has to stand out. It should do something no other app does, or do it better than others do. These benefits reinforce the brand. Because performance is an essential element in the user experience, it directly helps to differentiate the brand. Taking this one step further: making a technically challenging feature perform smoothly will give the product a unique selling point, one that will be difficult to imitate.

How it works

Sometimes we need to go back to the drawing board. And that's what we did.

Instead of just optimising the transport layers, we found its equally or more important to optimise - how - we distribute information in the first place.

By sending the right data at the right time, the information a user needs is already there and there's no waiting to reach the network. Most data can be predictably pushed to devices upfront. It's the same concept that is applied in continuous loading on popular websites: for instance, when you scroll down a twitter page, more content is loaded on demand (upfront) and we don't even notice that it happened, the content is already there.

IMG_8407

The same thing can happen automatically for any GET http request in your app. It doesn't mean content has to be endless, it just means that loading messages shouldn't be getting in the way of your content and users. HTTPSmartCache optimally transfers data so it's always fresh to use by your app.

 

Integration

The integration is simple and seamless, because the optimisation layer is independent of how the data is generated or what its content is. That means, you have to change nothing in your existing API's or application data structure.

This is an example of how it fits in the stack:

HTTPSmartCache-3

Basically it's just necessary to "plug the cables". In the same sense that Google translate analyses thousands of documents to predict the best translation, so does HTTPSmartCache's server component analyses every request in order to predict what the next request will be (to inject response for a request in advance to the client). With this input, it makes the cache in your app more efficient than one could manually, and is automatically ready for future API changes.

As you may have realised, there are side-benefits too: by reducing the number of unnecessary http request/responses on the wire (data is only sent when changed), the load on the back end reduces, thus reducing infra-structure costs.

Then, in the mobile client  side, replace the http get request calls with the ones from the SDK. For example, in iOS it would look like this:

//From: 
NSURLSessionDataTask *dataTask = [mySession dataTaskWithURL:requestURL completionHandler:
                                      ^(NSData *data, NSURLResponse *response, NSError *error)
                                      {if (error) { //Implement error handling } else {
                                           //data received..
                                          }
                                      }];
[dataTask resume];

//To:
#import "NSURLSession+HTTPSmartCache"
NSURLSessionDataTask *dataTask = [mySession smart_dataTaskWithURL:requestURL completionHandler:
                                      ^(NSData *data, NSURLResponse *response, NSError *error)
                                      {if (error) { //Implement error handling } else {
                                           //data received..
                                          }
                                      }];
[dataTask resume];

To find out more, check the project's concept demonstration source in Github:

a59a44b1a383ad42e195fa34f0ad2756f46c77a2

Interested?

Whether you're interested in HTTPSmartCache, would like to get involved with this project, or discuss about a partnership, please leave a message:





Your Name (required)

Your Email (required)

Subject

Your Message