Mobile Development Strategies Introduction

As a foundation to successfully implement a solid modern mobile strategy, we'll begin our dive into mobile strategy by first discussing today's various mobile development options:

1. Progressive Web Apps (PWAs) and Responsive Web
2. Cross Platform Development
3. Hybrid Development
4. Native Development
5. Wearables
6. Compare today's mobile apps with yesteryear's
7. 3rd Party development considerations

The discussions around each topic will be geared towards technical managers who may, or may not be familiar with the various mobile development options and/or deeper technical nuances regarding the strengths and weakness of each.  

However, while we will certainly be dealing with technical details, the posts here will not be specifically "how to" develop mobile, nor will the posts be specifically for developers and "how to" code.  That said, there will be plenty for developers and engineers here as well.

Instead, what we'll be more deeply diving into are areas to support technical and business leadership to understand the more technical details that each development paradigm offers an organization's overall mobile strategy to support the business.   

The following is an overview of the topics we'll be exploring:

Progressive Web Apps (PWAs):

First, we'll take a look into this hyper critical mobile option which is often overlooked by many decision makers when considering a complete mobile solution.  We'll look at the benefits and drawbacks of a PWA and clarify its strengths and weaknesses compared to Responsive Web and native app solutions. Generally, the awesome, bad, and ugly of them.

Cross Platform Development:

This is quite possibly the discussion which is most likely to elicit the most heated and impassioned conversations amongst both technical leaders as well as developers.  We've all heard it for decades now - "write once, run everywhere!"  We will dive into the realities of this topic on a very deep level, so if you as a business leader agree or disagree with this methodology, you'll be armed with the needed information to make the best decision to determine if this path is for your organization or not. 

Hybrid Development:

This next area is a subject which I believe is often either confused with cross-platform development or simply used interchangeably.   In fact, there may be some readers who admittedly argue that these two are indeed interchangeable.  IMHO, this is a point I disagree with and will give my two cents regarding this difference, because I think it's at least important to understand an alternative perspective.  Why would someone choose this development paradigm over cross platform or others? There are reasons, some technical - some not.. We will dive into all of them here.

Native Mobile Development:

At this point, with a more solid understanding of the various mobile development alternatives and each of their pros and cons laid out, we'll dive into our discussion of native mobile app development.

Often, the pitfalls discussed around native development tend to revolve around development time, cost, and learning curves.  What we'll look at here is the true long and short term impact of native development on these areas of your business.

Many times - often times - native is not the needed route...  Other times, it is simply the must take route and is absolutely the "best" - or "only" option!  We will explore this paradigm's technical team and business impacts in detail.

Wearables Development:

Here we take a look at an area of mobile development which is very much in flux and its potential impact on your organization's mobile strategy.  We will discuss this somewhat "newer" area of mobile which is going to continue to play a significant and growing role in our acceptance of integrated technologies and how we interact with our environment.

While we often see these mobile components as "extensions" of a particular mobile app - if you're looking to the future of having a current mobile strategy which continues to take your organization into the coming years - then wearables will most likely need to be a significant part of that mobile strategy. 

We will dive into this so your business does not miss out on this incredible opportunity.

Look into Future Architectures: 

At this point, with the development posts behind us, we will start our deeper journey into the larger enterprise and future looking solutions.  We'll dive into some of the differences between today's mobile apps and those of only a few years ago.  We'll explore overall apps' functionality and architectures which the enterprise has been developing in recent years as well as consumer expectations.  Further, we'll look at how that is evolving today!

Additionally, we'll look at realistic strategies for 3rd party support and development options and discuss some of the subtle land-minds to be aware of so they don't derail your organization's customer relations and keep you able to support huge volumes of integrations. 

I'm looking forward to writing the future post and hearing from you and any questions you may have.  

Let's dive in....

Read More

MetaVerse Thoughts

Since there will be a lot - a whole lot - of discussion about the coming MetaVerse throughout the future posts to come in this blog - I want to acknowledge the current and wide ranging thoughts, opinions, and misconceptions out there about the MetaVerse, and more importantly to preemptively provide a general idea so I can connect with the reader better. I very much want to connect together with a common picture when discussing the MetaVerse.  So, I wanted to address this 8,000 ton gorilla in the room before proceeding with the future postings of this blog.

First, I do not believe the MetaVerse as it has been widely advertised to date is what it's going to actually become.  While no one knows just what the MetaVerse is going to become, I still think that in fact, the vast majority of current advertising has done far more damage to mass, or really any acceptance of the MetaVerse.

The general consensus I have from most professionals and everyday tech users is that the MetaVerse is pretty much a laughable punchline today with joking references to Stephen King's "The Lawnmower Man" or the 1980's classic "Tron."

MetaVerse As VR:

As much of the hype around the MetaVerse has been displayed as interactions with weird cartoon characters - the thought of having a discussion with a virtual "weeble-Wobble" (Hasbro)" isn't appealing - no matter if its hair color is purple, blue, pink, red, or chartreuse...  Regardless - the idea is not at all enticing personally - let alone professionally.  Not to mention, no one is going to work all day wearing some bulky headset no matter how many "planets" they can transport their conference call to take place on.

VR worlds have been offered in some way since VR first came on the scene, and they've never really made much impact.  VR has - VR worlds have not (Gaming aside).  I think most people want to interact with their world, at least on some level and not be taken completely away from it.  I think if the pandemic proved anything, it is this fact.  So it would appear, most people don't consider VR a "connecting & engaging" experience - otherwise we most likely would have already jumped on that bandwagon. 

To that note, I do believe VR will play more of a role in the MetaVerse than it is already in some industries such as:

• Gaming
• Entertainment
• Business - to some extent.  NOT as a massively consuming component
• Engineering
• 3D Printing
• Medical research (ie: Cellular/Organ structures)
• Military & Law-enforcement Training

However, I think the MetaVerse as strictly a VR "thing" is looking at the MetaVerse as it would be to look at mobile as little more than simple mobile apps that make random sounds.  It's the basic start - but long term success in today's technical world requires real useful purpose beyond the novelty,  and I believe what the MetaVerse is going to become is beyond even the growth of mobile today from its beginnings. 

I believe the biggest VR issue with the MetaVerse is that the MetaVerse is being discussed as "Constantly Connected to - A normal and engaging part of your normal day-to-day, etc...  IE: You're regularly, easily, and naturally interacting with the promise and services of the MetaVerse - VR does not give us that.

MetaVerse & Web3:

Second, I think adding to the confusion around the MetaVerse, is the mixing of the MetaVerse vs Web3.  It is a mistake to think of the MetaVerse as Web3 rather than a component of it.  This is tantamount to thinking of a single social media platform as Web 2.0 rather than a component of it.  ie: Posting what you ate for breakfast is a part of Web 2.0 just as is video conferencing, entertainment, and our educational experiences along with the business opportunities Web 2.0 has brought us. 

Note: I'm using Web3 and Web 3.0 interchangeably.  If that means nothing to you, don't worry about it.  Industry will eventually change the nuances between the two anyways.

Obviously, no one really knows what Web3 or the MetaVerse is going to become, but here are a few VERY high level generalizations:

• Symantec (Fully decentralized Machine-2-Machine comms)
• Spacial (AR along with engaging wearables)
• Additionally, hyper engagement interconnected grids, cities, and nations will become common place
• MetaVerse (What the spacial ecosystem will be referred to along with elements of VR - which will be combined very much with AR)

There's nothing saying I am correct about the above, but where we sit today, it's a place where many have been discussing as a potential starting point.  My gut feel is that it is going to be a massive combination of these.

Essentially becoming a digitally connected world (5G - a lot more to this than just "faster") where we wear our entire device which will overlay information in front of us and we control via our wearables (we are a walking IoT node) - in very much the real world with a highly engaging and hyper useful AR world.

By "wear our device" - it will be functionality that is a combination of connections being made up of our clothes, rings, bracelets, earrings, watches, glasses, etc...

Also, keep in mind that the overlays will be supplemental to our real interactions with our very real world.   The point is, people will still be actually walking down the street and engaging with real people - not stuck in a chair with some huge contraption on their heads talking to weeble-wobble figures with no legs. 

And if there's any doubt what the term "wearables" is going to mean in the near future, or if you still consider "smart watches" as the full spectrum of wearables today...

Then, if you haven't already - check out these super-ninjas from Mojo Vision for some provoking thoughts:

Also, to be certain we never forget a major Giant of Tech (regardless of various opinions) - Microsoft!  These folks are some of the best and what they have done at every turn of new and up-and-coming tech over the past 40+ years is virtually unmatched.  Now it appears the MetaVerse and Web3 are going to be no different.  They are making some amazing progress and producing some absolutely incredible pushes for the MetaVerse with their Mesh.  Highly recommend you check it out - legit...

In full transparency, here's a link to a  Meta Horizon World which appears to disagree with my view of the MetaVerse.  Again, like I said - no one knows what the MetaVerse is going to become so it is possible Meta World's version is spot-on and I'm completely wrong.  Again, full transparency. 

Decentralized MetaVerse:

Thirdly, the fully decentralize aspect of Web3 has been getting a lot of traction - and for good reason!  Most people think of crypto-currency when discussing decentralized computing.  This is a 100% great way to look at it,  but IPFS (disk storage) is often not understood or overlooked, but is also a great architectural example of a decentralized future.  However, there are still centralized aspects, even with crypto or IPFS storage providers.

• Crypto minders are more often than not, using a "centralized" cloud provider for their computing to mine a block to add to the coin's blockchain.

• There are custom server farms with specialized HW which organizations and people have built, but even that is at least quasi centralized.

• There are Filecoin suppliers using cloud providers for their storage

Just as an aside, I don't know of anyone using mobile to mine crypto or support IPFS at scale - but if there is anyone doing this - PLEASE let us know in the comments!

So even centralized - cloud providers still play a significant role in today's decentralized ecosystem and are likely to play an equally important role to Web3 and the MetaVerse's capabilities and success - at least for some considerable time.   

However, I think where we will see significant changes is with today's service providers' business models and strategies as they will need to move from the centralized to decentralized mindsets.  

I think those that don't will go by way of BlockBuster video failing to see what Netflix saw.

Conclusion:

In closing - I just wanted to post this article so that as Web3 and the MetaVerse are being discuss going forward in post relating to other topics, that the readers of this blog have a gist regarding what the envisioned, possible MetaVerse looks like that I'm thinking of and referencing.

I do believe the MetaVerse is coming and its success is going to be overwhelming and awesome!  I am actually extremely excited about it!  However, it will not be a world of happy glowing, legless "weeble-wobbles" wiggling around on some purple people eater methane planet - at least I really hope not.

Read More

Mobile Strategy Introduction

Want your mobile dollars to maximize the massive engineering investment?  Let’s begin our journey by diving into developing a solid mobile strategy.

There are some seriously innovative technologies coming together creating an incredibly bold and hyper integrated world and at the very heart of this ever growing inner connected world is mobile!  Mobile phones, IoT, Fog & Edge computing, AI/ML, robotics, wearables, and the coming MetaVerse - all will heavily revolve around a very mobile world.  

Over the past 10+ years in the mobile industry and having encountered an incredibly diverse set of opinions and viewpoints, I wanted to start this blog to bring - if not a common vision - a more common understanding around today’s mobile capabilities and possibilities, with a focus on business and technical leaders rather than a “how to develop” blog for just developers.

Mindset: Mobile of old

Even now, in 2022, I find it incredibly strange when I hear organizations make statements such as “mobile’s dead!  Or - No one does mobile anymore…”  Now, I’m not 100% certain what “does mobile” means, but I hear it more often that one might expect.  I understand organization’s have different business needs, but mobile is anything but dead. 

Instead, these organizations seem to be stuck and cannot see mobile beyond simple apps instead of the massively connected and distributed global network which most of us are actively engaged with and using on a nearly constant basis.  It seems they’re missing IoT’s impact, or the future of wearables, and the coming MetaVerse.

Regardless, Mobile is actually in its infancy, not on its deathbed.  It is largely around this vastly differing understanding of mobile which inspired this blog.

Questioning Mobile today:

Even as developers are asking the question - “should I learn mobile development?” and organizations are asking how much they need to worry about a mobile app vs a simple responsive web page.  Rather than answering these questions directly - in this blog I’ll be diving into mobile’s architecture and capabilities and their associated strengths and weaknesses to help answer these and many other mobile strategy choices from a multitude of perspectives. 

Often, the success of today’s business strategy which fully leverages mobile revolves around 2 aspects regarding mobile (with the “app” being the consequence of the following):

• How does the business strategy solution fully leverage mobile well beyond the isolated phone (ie: What tech. does your organization’s mobile solution connect to, additionally leverage, expand your data input - customer engagement - etc…) 

• How well will the business strategy evolve/shift to adjust to mobile’s fast changing eco-system

An example which shows how today’s successful mobile is a consequence of a successful business strategy is Uber. 

Disconnected Mobile decisions:

As stated, one of the larger issues which was the underlying motivation for this blog is the vast diversion many organizations have regarding mobile.  The following are some various viewpoints I have heard some of today’s (2022) technical organizations have regarding mobile:

 

• Mobile is dead - No one does mobile anymore

• Should we have a mobile app for the company or just a web page

While other organizations are:

• Developing mobile solutions which scan extremely detailed fingerprints with the device’s camera

• Developing mobile ID acceptance into our nation’s airports

• Scanning biometric pulse and other vital signs which are preparing to disrupt and potentially transform our Telehealth and healthcare

• Developing fibers to be woven into clothing to interact with devices

• Still some mobile app start ups which are focused on hyper performant and feature rich mobile apps.

Clearly, there is a serious disconnect in today’s industry around what mobile is, can be, and even what it really should no longer be.  It often seems there is either hyper awareness or a dire lack of understanding around mobile. We will absolutely be exploring all of these in this blog.

Starting with the complex:

As we explore deeper and more complex mobile topics, I believe it is critical that business leaders and decision makers have the same base technical knowledge. To that end, I want to start off this blog with a series of post addressing specifically mobile development paradigms. This will NOT be from a developers perspective - not at all.  This is from the perspective to help decision makers better understand the pro’s and con’s of each so they can make more informed decisions when investing their engineering dollars.  

As we dive into topics such as Augmented Reality, the MetaVerse, IoT Blockchains, fog computing, etc… Having a baseline technical understanding of mobile will allow for deeply technical posts which will benefit everyone. Primarily due to this point is why I’m starting with the various mobile development paradigms.

I am truly looking forward to this new adventure and am hoping to engage with everyone.

Best

Read More