Skip to main content

Mobile journey options


In the last few years, we have seen rise in the use of mobile devices. As more and more users are using mobile devices, there is an increasing demand for businesses to have presence in the mobile world. Mobile devices have created tremendous business opportunities. The term mobile is not limited to mobile phones anymore, but it includes any device which can be used to access the information on the move. This includes tablets, hand held game consoles, media devices, watches etc. This list is increasing every day. 

Options for mobile development

There are number of options for developing apps with mobile presence, but we will explore the following 3 most commonly used solutions.
  • Native apps: Native apps are downloaded and installed locally from platform specific marketplace.
  • Cross platform apps: Using cross platform framework, you can develop native or hybrid apps. Hybrid apps are browser based apps but the user experience is same as a native app.
  • Cross browser, mobile ready web application: These are web based applications which run under a browser on a mobile device.

Comments

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0