![]() Using this framework, programmers can easily code the application as a device responsive. JavaScript frameworks are a type of tool that makes working with JavaScript easier and smoother. Nowadays, JavaScript is used as a server-side programming language as well. JavaScript was initially used for the client-side. It supports functional programming, object-oriented and prototype based programming. Some of the popular frameworks are NativeScript, Apache Cordova, Xamarin, etc. The main reason behind to use cross-platform or hybrid framework is easier to maintain a single code base. To overcome this complexity, mobile frameworks supports this feature. However, to develop an application that support both operating systems, we need to code in two different languages using two different frameworks. Android provides a native framework based on Java language and iOS provides a native framework based on Objective-C/Shift language. There are many frameworks available to develop a mobile application. To keep this example easy to understand we’re going to work with a fresh project.Generally, developing a mobile application is a complex and challenging task. Creating a New NativeScript Project with Dependencies You don’t need both, but it doesn’t hurt. To build for the iOS platform, Xcode must be installed and configured. To build for the Android platform, the Android SDK must be installed and configured. It can be installed as per the instructions on the NativeScript website. While you can probably use NativeScript 2.0 or higher, the particular version I’m using is 2.4. This is because the CLI along with all dependencies are obtained via the Node Package Manager (NPM). NativeScript, like many cross platform frameworks, requires Node.js to operate. There are a few prerequisites that must be met in order to make this tutorial a success. I did a generic JavaScript implementation of time-based one-time passwords in a previous post on this blog. I definitely want to give those two sources credit for sharing the algorithm on generating these passwords. ![]() Much of the code for generating passwords from secret keys was inspired by the following two sources: At the bottom of the list screen there is a counter that will reset every 30 seconds. It has two screens, one for listing time-based one-time passwords that change every 30 seconds and one screen for adding new passwords with a secret key. However, Google Authenticator leaves a lot to be desired and while we won’t cover anything too crazy, it opens the door to your imagination.īefore getting too far ahead of ourselves, it is probably a good idea to see what we’re going to be building.Ībove is an animated screenshot of what the application will do. A popular application that accomplishes this management is Google Authenticator. In case you’re unfamiliar, two-factor authentication (2FA) is an extra layer of security for web applications, requiring you to enter a numeric password that changes every 30 seconds in addition to your standard password. Let’s take time-based one-time password management to the next level and create a native mobile application with NativeScript and Angular. This inspired me to convert the application to something native and NativeScript seemed like a solid solution. Being a hybrid mobile application, there were some performance limitations that came with the Ionic 2 application. That particular application was built with Ionic Framework and I even wrote a tutorial explaining how to make a similar 2FA manager with Ionic 2. Not too long ago I released a time-based one-time password manager called OTP Safe to Google Play and iTunes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |