At the beginning of the year Andrea said that version 16.5 would include a new user interface rendering system. The time has come to reveal that this is the new “Ionic” theme for mobile applications.
It’s actually not just a new theme. It’s a new rendering system based on one of the most common frameworks for hybrid applications, Ionic.
This allows us to access features like:
- Native scrolling.
- Look and Feel that adapt automatically to the host operating system (iOS and Android).
- A User Experience very similar to that of native applications.
The decision to create this new rendering system was made so we could optimize applications as well as possible in order to improve the user experience. And if the interface that you have created has followed the standards, moving to the new theme shouldn’t take much more than a parameter change.
At this point I’ll leave you with the preview application, and as always I’m interested in hearing what you think of it. If you have Caravel installed on your device, you can test it by entering the identifier progamma.mwindi in the URL box.
NB: The preview application may contain inaccuracies. If you notice any unexpected behaviors, report them so they can be verified.
Anyone who follows trends in tech knows that one of the hottest right now is about IoT (Internet of Things) systems. An IoT system can detect data from a set of “smart” objects connected to the cloud. In certain cases they may also be controlled from the cloud.
But what are these smart objects? All domestic appliances will certainly become smart in upcoming years, and many of them already are, like smart watches, smart lamps, smart thermostatic valves, and so on.
One item that’s already available and easy to get your hands on is the AWS IoT Button, which lets you experiment with this new technology for a low price, and might even bring to mind some innovative ideas.
Once you have bought your AWS Button, you can configure it so that it connects to a WiFi network to send a message to the AWS cloud every time you press it. It recognizes three event types: single-click, double-click, and long-press.
The most complex part is creating a script within AWS that recognizes your Button and runs the code in the cloud. Fortunately, there’s a template that can send an email. I’ve modified it to make a call to a REST WebAPI implemented in an app developed with Instant Developer Cloud.
From here all you need to do is use the push characteristics of Instant Developer Cloud to get real-time updates on the events collected by your smart buttons. In the video below you can see how the experiment turned out.
Nice, right? All you need is to find the right idea, and Bob’s your uncle! Do you already have an idea on how to use it?
We’re into the hottest part of the summer and vacation is fast approaching. For many, vacation is a time for some well-earned rest and relaxation, but programming buffs often seize the chance to look into something new at their leisure.
To make things easier, we’ve put together a series of design patterns for Instant Developer Cloud. In addition to the mobile-design-patterns we presented two weeks ago, today we also have:
- doc-design-patterns: shows how to manage the application using an ORM (Object Relational Mapping) approach. Using documents and collections, there is a strict structure for accessing and modifying data, and it’s much simpler to manage complex operations on the back end and on the device. Also, we didn’t overlook the interaction between documents and Web APIs that is so popular today.
- datamap-design-patterns: this is one of the most interesting examples because it deals with displaying the application data. Between the infinite, virtual, nested, and recursive lists there was also time to make a digital wheel of fortune. You can click here to see a preview of the application.
- sync-design-patterns: an actual work bench for testing the synchronization system between a local app and the cloud. You can explore the secrets behind exchanging messages, document synchronization, and remote calls.
I don’t know if you noticed, but the five design patterns we’ve provided cover the full development cycle for an application:
- Database design and access to data.
- Back end development with an ORM approach.
- Front end development using visual element libraries.
- Pairing front and back ends using datamaps.
- Syncing the local app and the cloud.
To get the most from the examples, we recommend opening them in the IDE, launching the application preview, and testing the various functionalities. Then return to the IDE and in the various views that interest you, have a look at the code that implements them.
As always, I look forward to your feedback, and if any interesting examples come to mind, send me an email and we will happily add it.
Enjoy your vacation!
In recent months I’ve had the pleasure of helping create a number of mobile apps using Instant Developer Cloud. It has been an intense and satisfying period, and one of the best gifts was being able to understand how to improve the documentation system for the platform.
In fact, when people begin working with Instant Developer Cloud they immediately ask, “Where is the documentation? What can I look at to learn how to use it?”
There are already a number of options available:
- The introductory tutorials based on chatbots: these are helpful for understanding the fundamental concepts for the IDE and the framework.
- A few complete example applications that show functioning apps.
- Online documentation of the libraries with examples of code so you can learn detailed information about the various methods available.
What else do we need? What I’ve seen is that the complete example applications are too complicated to be analyzed quickly and adapted to one’s personal needs. That’s why I decided to create a new series of example projects that contain the most common design patterns.
We made the first one in June to show the basic structures of the user interface for responsive mobile apps. Starting today, you can open the mobile-design-patterns project that contains the most common cases in very simple form.
What will you find there? Here are a few examples:
- The basic elements of a page.
- Navigating among pages including sending bidirectional parameters.
- How to create pages based on tabs.
- A model of a responsive grid.
- Lots of different list types.
- The most common widgets and popups.
Scattered here and there in the code you can also find examples of using REST Web APIs, how to read a file from disk, how to download resources from the internet, and more.
To use a pattern, just open the example project, select the view that interests you, open it in HTML view with F4, and then copy the code to your project using the same procedure. If you’d rather see the application working directly in the browser, just click here.
I’d like to hear what you think of this kind of documentation. And if you like it, I have in mind five or six other groups of design patterns to publish over the next few weeks.
Let us know!