Tech Talk Insights

When it comes to mobile application development, we have a lot of options. There are plenty of cross-platform solutions that allow you to write code once and deploy it everywhere. The most well-known options include: Flutter (a Google product) React Native (a Facebook product) Ionic (built using Angular framework) NativeScript (built using Angular framework) Xamarin (a Microsoft product) Cordova (HTML/CSS/JavaScript) There are a lot of factors to consider when deciding which platform to use for mobile app development. Here we compare Flutter and React Native in terms of performance, ease of development, support, and more. Flutter vs. React Native - A Brief Introduction Flutter and React Native are two of the most popular frameworks for building mobile apps. They both allow you to build native applications for Android, iOS, and other platforms with a single code base. The main difference between these two frameworks is that React Native uses JavaScript and Flutter uses Dart.  ...

Flutter is a new cross-platform app development framework from Google that allows apps to be created for both Android (KitKat or later) and iOS (iOS 5 or later). It's all  open source  and still being developed by engineers at Google and you can follow two engineer's profile at  Chinmay Garde  &  Devon Carew . The main focus of Flutter is to provide low-latency input and high frame rates (60fps) for high performance on Android & iOS. Flutter Architecture Flutter is built with C, C++, Dart, Skia (a 2D rendering engine), Mojo IPC, and Blink’s text rendering system. To have better understanding of the main components, please check the below architecture diagram:- High-Level Overview of Flutter Architecture Flutter has three main components:- A heavily optimized, mobile-first 2D rendering engine (with excellent support for text) A functional-reactive framework A set of Material Design widgets, libraries, tools, and a plugin for Atom H...

As you all know last month at Google I/O we got glimpse of the L Developer Preview . It provides us an advance look at the upcoming release for the Android platform, which offers new features for users and app developers. Android is getting a major overhaul with its next version, which is currently being referred to as Android L. The new version will tout more than 5,000 new APIs, multiple new features, a new runtime engine, and a major user interface makeover. The Android SDK has been released and, for the first time, you will be able to preview the new version on a Nexus 5 or 7 device. I thought let's give a try to L Developer Preview, so I downloaded the SDK & setup my development environment. After that I installed the L Preview System Image on Nexus 5. To flash the image onto your device please follow these  instructions . You can have a look at Nexus 5 with L Developer Preview as follows:- Now it's time to get our hands on L Developer Preview APIs ...

Sometimes we have requirements to check whether device is phone or tablet & even for tablet whether device is 7" or 10". Following method will help us if the device is tablet or phone. If device is tablet method will return true, otherwise it'll return false. public boolean isTablet(Context context) { boolean isTablet = (context.getResources().getConfiguration().screenLayout & Configuration.SCREENLAYOUT_SIZE_MASK) >= Configuration.SCREENLAYOUT_SIZE_LARGE; return isTablet; } If above method return true, which means the device is Tablet. Now we have to detect whether device is 10" tablet or not. If device is 10" following method will return true, otherwise it'll return false. public boolean isXLTablet(Context context) { boolean isXLTablet = (context.getResources().getConfiguration().screenLayout & Configuration.SCREENLAYOUT_SIZE_MASK) >= Configuration.SCREENLAYOUT_SIZE_XLARGE; return isXLTablet; }

The below method will return whether current file is audio file or not:- public static boolean isMusic(File file) { Uri uri = Uri.fromFile(file); String type = MimeTypeMap.getSingleton().getMimeTypeFromExtension( MimeTypeMap.getFileExtensionFromUrl(uri.toString())); if (type == null) return false; else return (type.toLowerCase().startsWith("audio/")); } The below method will return whether current file is video file or not:- public static boolean isVideo(File file) { Uri uri = Uri.fromFile(file); String type = MimeTypeMap.getSingleton().getMimeTypeFromExtension( MimeTypeMap.getFileExtensionFromUrl(uri.toString())); if (type == null) return false; else return (type.toLowerCase().startsWith("video/")); } The below method will return whether current file is image file or not:- public static boolean isImage(File file) { Uri uri = Uri.fromFile(file); String type = MimeTypeMap.getSingleton().getMimeTypeFromExtensi...

ART (Android RunTime) is the next version of Dalvik. Dalvik is the runtime, bytecode, and VM used by the Android system for running Android applications. ART has two main features compared to Dalvik: Ahead-of-Time (AOT) compilation, which improves speed (particularly start-up time) and reduces memory footprint (no JIT). Improved Garbage Collection (GC). An ahead-of-time (AOT) compiler is a compiler that implements ahead-of-time compilation. This refers to the act of compiling an intermediate language, such as Java bytecode, into a system-dependent binary. Hence your apps are compiled to native code once, and stored on your device to run effectively as native. This differs from the traditional VM model, which interprets bytecode. Interpreters are slow, so VM developers added a technology called Just-in-Time (JIT) compilation, which compiles (and hopefully optimizes) your code to native code on-the-fly. Dalvik is a JIT'ing VM. The downside to JIT is that the JIT compiler ...

Sometime we have requirements to implement call & sms support with in our android app. Now how to check whether device has support for call & sms feature. To verify, we can check the device phone type, which indicates the type of radio used to transmit voice calls. In addtion to this we can also check that the device has a telephony radio with data communication support or not. The method is as follows:- public static boolean supportCallAndSMS(Context context) { boolean isSupported = false; TelephonyManager telephonyManager = (TelephonyManager) context .getSystemService(Context.TELEPHONY_SERVICE); boolean isPhone = !(telephonyManager.getPhoneType() == TelephonyManager.PHONE_TYPE_NONE); boolean featureTelephony = context.getPackageManager().hasSystemFeature( PackageManager.FEATURE_TELEPHONY); if(isPhone && featureTelephony) { isSupported = true; } return isSupported; }