{"id":231,"date":"2013-01-01T13:00:25","date_gmt":"2013-01-01T13:00:25","guid":{"rendered":"http:\/\/localhost\/happiestminds\/blogs\/?p=231"},"modified":"2024-04-11T09:07:14","modified_gmt":"2024-04-11T09:07:14","slug":"are-we-repeating-history-with-mobile-enablement","status":"publish","type":"post","link":"https:\/\/www.happiestminds.com\/blogs\/are-we-repeating-history-with-mobile-enablement\/","title":{"rendered":"Are we repeating history with Mobile enablement?"},"content":{"rendered":"
<\/div>

I wonder whether we are repeating history when we talk about mobile enabling applications.\u00a0 When we look back 10 to 15 years, organisations have spent millions of dollars in converting two tier applications to multi tier and web enabled them.\u00a0 Many legacy applications have been web enabled since then.\u00a0 During this course of time we went through a journey of<\/p>\n

    \n
  1. Two tier applications to web enablement of each of these applications<\/li>\n
  2. This resulted in to mushrooms of portals across the enterprise as there were many applications which got web enabled!\u00a0 This created lot of overhead.\u00a0 This lacked consistency and created management nightmare<\/li>\n
  3. Industry started looking at portal consolidation effort.\u00a0 Again millions of dollars were spent on consolidation<\/li>\n
  4. Meanwhile there was a push to look beyond applications as business processes were cutting across applications.\u00a0\u00a0 This is where workflow, orchestration, BPM tools got introduced.\u00a0 This brought in process view and integrated applications<\/li>\n
  5. Money was spent on building portals which are process centric viz., order management,\u00a0fulfillment\u00a0 claims processing, employee onboarding, customer onboarding etc.<\/li>\n<\/ol>\n

    While this was going on, there were multiple types of browsers got introduced.\u00a0 This led to compatibility issues.\u00a0 To overcome this challenge, concepts such as Responsive Web Design evolved.\u00a0 HTML technology got matured.<\/p>\n

    Now organizations are looking at mobile enabling their applications, one by one.\u00a0 I\u00a0 wonder we are retracing the history by embarking on to this mobile enablement journey.\u00a0\u00a0 organizations have choices to make: Learn from the past and embark on a structured & robust mobile strategy\u00a0 or repeat the history and have a clutter of mobile applications within the enterprise.<\/p>\n

    In my view, we don’t have to repeat this web history.\u00a0 We can look at quantum leap in mobile space and jump to a matured state instead!<\/p>\n

    \n

    Before I jump in to solution, it will be good to look at challenges what organizations face with respect to options they have in mobility.\u00a0\u00a0 Diversity in technology along with budgetary constraints have been inhibiting organizations from adopting to full-fledged mobility strategy.<\/p>\n

    Let’s look at diversity of technology both at device level and at software level.<\/p>\n

    There are variety of devices from many vendors including Apple, Samsung, Google, Nokia, RIM with various form factors (i.e., 4 inch, 7 inch, 10 inch) and Operating systems such as Windows, Android, iOS and so on, In this case I would say “more options leading to confusion”, which is much higher than just the browser compatibility problems we dealt with\u00a0during the internet era.<\/p>\n

    Adding to these, mobility field is still evolving.<\/p>\n

    We shouldn’t forget one other important aspect when it comes to enterprise adoption i.e., information security.\u00a0 Organizations are seriously looking at the option of “BYOD” ( Bring your own device).\u00a0\u00a0 This means that in an enterprise any permutation – combination of the above choice scan exist.<\/p>\n

    Here I must say that significant attention being given to security aspects both from hardware and software perspective, by leading vendors such as Apple, Google, Microsoft.<\/p>\n

    Now, I would touch upon the other aspect I mentioned, i.e., budget.\u00a0 Organizations are taking very cautious approach in taking steps towards mobile enablement.\u00a0 They also want to see quick results with small experiments.\u00a0 They don’t want to have high investment while the field is still maturing.\u00a0\u00a0 Most of them are taking one or two applications at a time and see how it gets enabled on mobile.<\/p>\n

    All of these aspects forcing the organizations to trod the same path as we did with web enablement.<\/p>\n

    In my view, we have better options, while we have all the above challenges.\u00a0 In my view, first step is to look at the maturity of the organization \/ business unit for mobile adoption.\u00a0\u00a0 This would enable them to do a quick analysis and put a\u00a0road-map\u00a0for enterprise mobility.\u00a0\u00a0 This step would probably take couple of months effort with minimal spend.\u00a0 As a next step, having a strong enterprise backbone for mobile enablement is necessary.\u00a0\u00a0\u00a0 After this, one can experiment with few applications.\u00a0 This will be a scalable model.\u00a0 This will drastically reduce time to market and reduce total cost of ownership.<\/em><\/strong><\/p>\n<\/div>\n

    \r\n
    \r\n \r\n <\/i>\r\n <\/a>\r\n 0 <\/span>\r\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"

    I wonder whether we are repeating history when we talk about mobile enabling applications.\u00a0 When we look back 10 to 15 years, organisations have spent millions of dollars in converting two tier applications to multi tier and web enabled them.\u00a0 Many legacy applications have been web enabled since then.\u00a0 During this course of time we […]<\/p>\n","protected":false},"author":78,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[200],"tags":[202,217],"class_list":["post-231","post","type-post","status-publish","format-standard","hentry","category-mobile-computing","tag-mobile","tag-mobile-enablement"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/posts\/231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/users\/78"}],"replies":[{"embeddable":true,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/comments?post=231"}],"version-history":[{"count":1,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/posts\/231\/revisions"}],"predecessor-version":[{"id":12398,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/posts\/231\/revisions\/12398"}],"wp:attachment":[{"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/media?parent=231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/categories?post=231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.happiestminds.com\/blogs\/wp-json\/wp\/v2\/tags?post=231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}