Design a product to replace smartphones in 5-7 years.

So let me understand the problem a bit further first.

1) We want to design a new type of smarphone or just something instead of a smartphone. (yes).

2) And does it have to be hardware or software? (either)

3) And do we have to be able to have the same functionality as we do now with smarphones suhc as install apps, etc.? (this is supposed to be your solution so I would lke you to tell me what this might look like in let's say 2040).

4) Ok...so we are thinking really really futuristic? (not necessarily...fine let's say 2026. Essentially just want to next thing).

5)I assume there isn't any other specific leadership guidance? (No)

6)Is it fair to assume that considering we are Google we are trying to come up withh something moonshot? (yes)

Ok, Google being a mature company I assume we won't have to worry much about customer acquisition, however, specifically speaking for a product we would possibly have to think about adoption. Let's take Google Phone for instance; they weren't adopted that easily and I thikn they still aren't. I could be wrong if so please correct me. (fair assumption)

So I would want to design something that could attract people. And speaking of new products and moonshot ideas and Google mostly focused on disrupting industry with tech powered products, I think it suits young people for the most part. Yes Google does have older people as well, classic example being Gmail and Google Maps, but even now I see many older people who continue to have Hotmail account (such as my dear old man and my mom though tech savy and has a gmail account mostly still uses gmail and god even my sis who is just 5 yrs elder uses Yahoo). Our best bet at adoption is targeting what might be interesting to young fellows.

I want to think what that attracting factor might be:

1) Not having a physical product and yet doing what cell phones do magically

2) Not having to spend so much money to fix a broke phone

3) SLR quality camera but we sort of have that though for a person who is more of a photographer type I disagree with the overall sentiment.

4) Be OS agnostic.

5) BE carrier agnostic.

I really don't think consumers really care much about #4 (usually people have a choice and those choices don't change much) but care more about #5 (but mostly people don't change). But I think #1 and #2 are definitely higher and #3 I think is definitely important as wel. People are happy wth camera capability but would spring on better camera. Here I think hardware needs t be improved more than the software but I could be wrong. IF we address these problems, we could attact enough consumers.

Wait speaking of these, there are two types of young adults...consumers and those using for business. Let's focus on consumers since that's most of Google users. Not that we can't change that game but I also want to consider that not that many businesses offer phone for employees (minus sales and executives).

What oculd help as we look to future "smartphone" is:

1) A product thats a 3 hollow gram. So I imagine a wrist band such as Apple Watch on which you tap phone icon. Phone pops up in thin air and you use it like you use current cell phone. When you don't want it you simply swipe it off by grapping it phone in a fist and swiping that fist. Privacy would be a concern here though since everyone can see what you see if the phone is in the air. We could eliminate this via Google glass but we know that didn't work. Since I don't know why it didn't work let's not have it on the table for now.

2) One othre thing we could do is a AirPod that's connected to the cloud where you have your phone numbers and such. It could evne connect to Google Maps and financial bank data, etc. So you say "Call Sam" and it will call that number (you don't need a screen). Traditional challenges such as exterior noise, geting better at NLP, etc. lie. Also you could say navigate to x and AirPods speak the direction but we need visual soemtimes (though I don't see the need of one so maybe we could elimiate visual completey or as optional it will pop as a hollogram). For chase bank data for instance it could be speech driven whereby when I say "open Ally Bank", it will say "accessed". As a account owner i would know if I have checking account and/or savings account with Ally so I don'tsee the need for it to say anything more (if app says more it be wasting my time). So it waits my response for 10 seconds and then it will announce "you have been inactive. App closing. Say Keep open if you want to keep it open". I can say "checking total amount", etc...On watch I can see things printed or on hologram based phone. I do think those that these prompts could differ based on what bank it is so maybe we don't wnat to design this further.

3) For taking pictures, I see a scene and I draw an approximate rectangle or swquare with my fingers to form a farme. Hologram phone screen with camera view shows up there. It will adjust WB and ISO, etc. itself and I can modify it. There is nothing private about most pictures we take but there might be things we don't want people to know when we take it so maybe for future we can think about saying camera unseen (in fact this should be a code word you can customize so others listening to our speech don't know what we are attempting to do). And for those pic are only see on our watch but I can still adjust settings on my hologram phone. In terms of iomproving camera I think there should be more ML / AI soluutons whereby it can find similar pictures based on lighting and weather conditions and recommend what best setting works. For these lighting and weather conditions, we might need some API integrations. I could go in further details on this but I think thats a whole new product here.

I think above solutions also solve the problem of braking phone and fixing it. Also, #4) I prob pay subscription to OS and I can load up whatever OS I want for the time being if we wanted to solve that problem but I doubt we should focus on that now.

Do we have any constraints in terms of time / resources, etc.? (No).

Ok considering we are Google, I have all kinds of skills inhouse or I have no trouble sourcing one. I think we are almost there on #2 but I think it be best to refine this tech. This may need some strong collaboration with multitude of banks, etc,. or maybe some standards that any bank has to meet for this idea to work. I thikn #1 is more attractive but we have tons for R&D when it comes to Privacy so I think #2 is mmore of a low hanging fruit that does help us down the line. So I would work on #1 and #2 in parallel with prioritization of going to market with #2 first.

I would launch the feature and test it out with existing phone and airpods (for lack of better words). I would wnat to see # of customers who use the feature and more so % of customers who use it more than once. Using more than once menas you like it but I think that still doesn't tell us if experience is good enough. So maybe using it more than 15 times or iteratively testing if the same customers are using it over and over again. There is something called people use something couple times to get a hang of it and finally quite since it frustrates them and they just can't get it to work like they would like.

Overall, I think the future smartpphone should elimiate me having to carry a physical device, exposing to water damage problems or breakage due to drops, etc. Hence, I lean towards a hologram based phone. In fact, it solves the problem of loosing devices too.