2022 Chromebooks 02

My initial reintroduction (it's been over 6 months) to the world of Chromebooks was perhaps a little disappointing. I made a lot out of my inescapable longing to move back to a Chromebook as my primary computer in my last missive, but in actual practice the time away had stolen some of the glimmer I expected to experience. 

First, I was unable to connect to my Citrix desktop, so the Chromebook was immediately out as a machine available for work. This was disconcerting, as its ability to supplement my desktop for this task was one of the more attractive benefits. I wouldn't be lost without it, certainly, as my workplace has already provided quite a powerful laptop to meet this need. I could absolutely take that laptop out and about as needed to work away from my desktop. I would imagine my workplace would prefer I take this approach. However, the work laptop is a bit unwieldly and it is actively monitored by my employer. As much as I am sure it isn't a big deal, I wouldn't want to browse Amazon or write a blog post while logged in on my work laptop. I'd only want to enter bills, which is my job. In that regard it is perhaps even healthier for me to use my work laptop for work. But I am selfish person. I like my freedom, even if I don't actually intend to use it.

Then, the Android game I've been fiddling with wasn't authorized to run on Chromebooks. Phones only. Which is dumb and totally not my Chromebook's fault. Even so, it was a disappointment. And it made me sad.

Then, all the Android games on every device I own went ahead and installed themselves on my Chromebook. I had to uninstall them all. And then they were all uninstalled from all my other Android devices. I mean... I like the automatic synchronization, but the implementation is a little awkward in this context. I don't actually know how to separate specific devices from what appears to be the communal install pool. I should probably figure this out.

Finally, I was thinking all the extra power under the hood would make for a more fluid and precise drawing experience that what has been afforded by my Chromebook Duet. It does. However, the screen is a bit tackier than the glossy coat on the Duet. This is actually nice when using the Chromebook as ... a Chromebook. But the stickiness isn't super pleasant when using a pen. And then, also (and perhaps super obviously), the Chromebook is a good deal heavier than the Duet. It's not pleasant to write on unless it is sitting on a tabletop. The Duet, on the other hand is light and easy to handle. 

So, with such an array of disappointments, perhaps I should be filled with regret. I am not. But maybe I should.

On Chromebooks in a new year

The central question to my first analysis of Chromebooks revolved around whether or not I could use the platform to replace my dependency on Windows as an operating system to enable my activities. While this was, perhaps, an unfair premise for evaluation, it was also necessary. As Microsoft has more openly discarded any concern for individual freedom or anonymity, the pressing desire to abandon their product has grown. Yet there are very pronounced dependencies to attend. Steam gaming habits. Photoshop projects. File storage. Video editing. Audio editing. None of these pastimes could be abandoned and all would require replacement. Even so, no suitable replacement is found. This was rendered frustrating because of the perceived necessity of migration.

Yet, with honest evaluation, is it really fair to laud the Chromebook as a more private alternative to Windows in its most invasive form? Not really. Google's nascent OS initiative is built upon a Faustian disregard for personal privacy. If my primary concern is being tracked, traced and catalogued then Chromebooks simply do not apply. 

So, in the air of this reality, I tried to disregard the death of my Chromebook. I complained to my wife on the day it refused to charge or boot again, thinking perhaps we would agree to find room in the budget for a replacement. However, we were in dire financial straits at that moment. The idea of purchasing a new computing device was laughable at best - especially when weighed against the fact that I posses plenty of devices, including another Chromebook (tablet). No deprivation would actually occur. These realizations settled in quickly and I sought to save face by not pressing the issue. The machine I once considered my main system ignobly passed from paperweight to trash bin without further remark. And this was meant to be the end of it. 

So, why am I continuing to discuss Chromebooks? As it turns out, Chromebooks are worthy of consideration for their own merits. They do not need to be positioned as a reasonable replacement for something Windows or Mac. They are just great in and of themselves. In the weeks which followed where I attempted to acclimate myself to life without a Chromebook, I found my reliance on Chromebook tablet greatly increased and my reliance on Windows computer unchanged. Windows did not move in to fill the gaps left behind by my deceased Chromebook. In many ways, it couldn't.

That statement probably strikes readers as odd. Rightfully so. Summarily, I just stated that Chromebooks are incapable of replicating many of the necessary tasks performed by Windows-based computers. It is well known that the base functions Chromebooks do offer are also available in the Windows ecosystem. This is the core argument of all those who insist Chromebooks are only good as cheap alternatives for people who couldn't (or shouldn't) afford better. The people who insist this are MANY. There are entire websites run by them. People who own and love iPads and attempt to review Chromebook tablets - inevitably coming to the conclusion that the Chromebook tablet is, in fact, a tablet but not actually an iPad and therefore unworthy of money. People who own and love Windows gaming computers who insist that Chromebooks can play games, but they still fail at running the games which only run on their Windows gaming computer. People who aggregate such sentiments to state that Chromebooks with powerful hardware are merely silly excess because Chromebooks are obviously nothing more than a niche alternative for people who can't afford the real thing.

It is tempting to see the logic in these statements. Indeed, I have bought the false syllogism personally. Yet, one thing remained. I missed my Chromebook. Daily. 

Oddly, when my Windows computer stopped working, I forged ahead and managed to only miss it very circumstantially until I had no choice but to replace it. I have used both iPad and Macbook and somehow manage to live without missing either at all. But my niche, unnecessary alternative Chromebook I've missed daily. Fervently. Passionately. Annoyingly. 

I didn't replace my Chromebook because there were just so many things I couldn't do without it. I replaced it because I wanted to have it for the things I can do with it. I am not sure what that means, but certainly, for myself, I have to recognize that ChromeOS is not just a cheap, less effective alternative to other so-called "full" OS experiences. ChromeOS is a full OS in its own right, worth my money and my consideration.

So, perhaps I should continue to explore why.

Why a Google Pixel Slate?

...or, isn't the Chromebook C302 enough for you?

It is. The Chromebook C302 is and has been awesome. In the years I've owned the device it hasn't lost a single step in terms of speed or usability. Also, as I've grown accustomed to Chrome as an OS, it has become more and more useful. I've learned many of the boundaries of what I can handle as cloud-based and what I need to be local. The benefits of "working in the cloud" are nice, to be sure. 

So... why do I feel like I need an upgrade? What does the Pixel Slate offer?
Well, to be honest, it doesn't offer very much. That's the reason why I haven't really pushed to get one. The processor of the m3 model is not a very large step up in performance (even theoretical performance) over the m3 processor in my current Chromebook. Plus, performance issues have not plagued my Chrome experience - quite the opposite actually. But it does offer one specific thing that I have been wanting to make use of recently and that's the ability to draw.

The Chromebook C302 is a magnificent device that has served all of my needs in unexpected ways and convinced me of the soundness to the theory of moving away from a Windows-centric computing experience. It does more for me than any Windows-based laptop I've ever owned or worked with and has completely convinced me to stick with ChromeOS as my go-to mobile operating system. Even so, you cannot draw on the C302. It wasn't designed for it and it doesn't have the hardware for it. 

So why not simply buy the hardware for the Asus C302?
Well, that seems a decent solution, but a lengthy round of Google searches will reveal that drawing tablet support on Chromebooks is a bit spotty. Google won't acknowledge it, which is disappointing. Even more concerning, though, is the fact that compatible apps are hard to determine and seem to be dependent on which input device you've purchased. Furthermore, decent input devices are still quite pricey (though not $800). These concerns lead me to a place where I would feel much safer and wiser in simply purchasing a device that is designed to work for drawing from the ground up.

Why not get the HP X2 or the Pixelbook?
I would. The Pixelbook especially. If the $999 version of the Pixelbook ever went back on sale for $699, I think that's easily the best option of the bunch. It seems like that this is the event to look out for. The detractors here are 1) the Pixelbook is supposedly discontinued and 2) the sale events are unpredictable. 
The HP X2 is another amazing option and I only have two small concerns about it: 1) it is heavy. 2) it is ugly. Neither one of these concerns are deal-breakers by any means.

However, even with the two potentially better options stated above, there is something that the Google Pixel slate has which neither of these does: style for a similar price. And I am vain. I would love to have that sweet, understated Google style to slip into my bag in a light and convenient package built for drawing and chromebooking. 

But the ability to draw is not yet worth $800 either way.

On Chromebooks - Second Week [Part 02]

Shortcuts to happiness

It is no secret that I love shortcuts in my computing experience. I like the built-in shortcuts. I like custom macro actions. I like shortcuts I can define for myself. I've even caused problems for myself by becoming too reliant on the shortcuts I've programmed into my mouse at work. In all the time I've spent learning the Windows computing environment, I've become very accustomed to the shortcuts offered by Windows and I've immediately noticed their absence where ChromeOS diverges from Windows.

For instance, there is no need for a Windows key in ChromeOS, yet I continually try to press it to open the "search" (where all of the Chrome and Google Play apps reside). There is, in fact a key to accomplish this action, but Google placed it where the caps lock would normally reside. I use the word "normally" because it is normal for me. Of course, if I had used ChromeOS all my life and was moving to Windows, I would find the placement of the Windows key strange. But that was never an option, so let's ignore it.

If I connect a standard Windows keyboard to my Chromebook, I can observe the Windows key is interpreted as the search key. The caps lock key is interpreted as the caps lock key. Therefore, my assessment of the situation is that Google decided to change the caps lock and... well, I am not sure what to call it now. Is it the search key or the windows key? This depends on the environment, but I think a universal term would be convenient. It is probably something else in whatever Apple calls their operating system. It is the menu key, perhaps. The UX dongle. Anyway, this Chromebook keyboard has placed the UX dongle where the caps lock would be located on almost any other keyboard and I am not certain I am in favor of this decision.

I have noted there is a shortcut to the caps lock function via alt+UX Dongle. This isn't horrible, but it will take some measure of adjustment. I have also noted ChromeOS will allow me to change the UX dongle to a caps lock key and assign some other combination of alt+key to the search function it is assigned by default in ChromeOS. This seems reasonable, but I am not completely sold on doing so. Should I need to powerwash my Chromebook and move to a different channel, I would have to remember to make this change again. This isn't a hardship, simply a matter of whether I want to remember to do so each time or simply become accustomed to using the key the way my Chromebook is asking me to.

The print screen combinations for ChromeOS are a bit more streamlined in my opinion. Perhaps this is because it is so clearly laid out in the help sections for the OS, whereas in Windows there is some mystery as to when, why and with what button combinations the print screen feature will work, The task switcher button is expected and this in concert with the ctrl key will capture your screen. Add shift and it will capture the app in focus. That is fairly simple to remember.

F2 is more problematic. In Windows, this is the default key for rename across all applications. In ChromeOS there is presumed to be no need for a universal rename/insert function. I have found a replacement in ctrl+enter which seems situational, but perhaps I have just not explored it enough. There is, of course, always the option to rebind some other key, but as stated before I am not necessarily interested in this. I have also observed that using a mouse button bound to F2 has no meaning in ChromeOS. It doesn't recognize the command at all.

F5 is not refresh in ChromeOS. It is the task switching button. Refresh is bound to F3 instead. Aside from this undercutting my old concept for a web design company named F5 (for refresh or refreshing), it isn't that terrible of a change. I do find myself pressing the task switcher by accident, though, as the positioning is different enough to confuse my unfocused muscle memory. I don't think I hold this change against ChromeOS as much as I simply wonder why it is necessary. Why move refresh at all? Most people would be familiar with the F5 placement, so why not just arrange things according to this familiarity? These are probably not questions I can ever answer, but there they are.

Otherwise, all of the shortcut keys in ChromeOS appear to work exactly as I would expect them to, which is a bonus. I haven't attained enough distance from either computing environment (nor do I think I am likely to) to be able to say objectively which arrangement is better. My current conclusion is that neither is better, but since once is more pervasive it should be used as a standard. Therefore I see the changes made in ChromeOS as a disadvantage instead of simply as a change.

I try to assess all of this via the perspective that versatility breeds complication. In Windows I can assign complex macros to my mouse buttons. In ChromeOS, I can do the same, but not natively - I still need a Windows computer nearby to program the mouse. The macros I program in Windows don't necessarily work in ChromeOS and the macros I program for ChromeOS don't necessarily work in Windows (there is a little overlap). No real advantage there to either system.

The more I use ChromeOS, the more clearly I see that the goal here is simplicity. I want to replace my Windows computer, so I keep trying to complicate things. Doing all the activities I have become accustomed to is complicated. I don't think ChromeOS will ever "get there" in terms of what I am trying to do with it. I don't think the people developing it have those intentions. ChromeOS is a beautifully simple and focused environment. It is meant for simple things and it is meant to do them simply. I am starting to see how that can be good, even though I foster disappointments over the things I hoped for when beginning this process.

On Chromebooks - Second Week

Beta Blues

I was surprised and disappointed when, upon receiving my new Chromebook I discovered Google Play had been reverted to the dev channel from the stable channel (more on this below). I wasn't devastated by the change as I truly didn't purchase the Chromebook solely for its purported access to my Android apps. I've spent time discussing why this was an important part of my purchase decision, but the main goal for this device remains writing. I don't need Android apps to write. I don't really even need a new device, though the look and feel of this one has certainly inspired me with a desire to use it.

Writing is well and truly in hand at this point, though I do need to deal with some of my (possibly self-inflicted) trauma over past... efforts. I wanted to write "failures," but they weren't actually failures. They did lack the level of success I anticipated. Of course, the level of success I had anticipated was lost in that realm where the mind can confuse hopes with purpose and dreams with direction. Despite my disappointments, I can't escape the knowledge I am meant to write a story. I still don't know if it is a good story, a trite story, a forgettable story, a meaningful story, or a selfish story. I have to learn to accept my own ignorance in this regard.

I am still struggling to find that balance between writing what I am capable of writing and honing my capabilities into something greater. There is a parable about Mona Lisa to be applied here, but I will abstain. I think both are important and while I struggle with the fear of writing again in a way that is no better than what I've written before, I am also fearful of never bringing myself to write again. There is actually quite a bit at stake here. I highly value my desire to be seen by my children as a writer and to share my stories with them. Malachi is at the age now where he would accept anything I write as amazing and fuse it with his childhood memories. He will not be at that age forever. If I start writing again when he is a teenager, struggling with hormones and his own desire to be the leader God made him to be, then my stories may no longer have any impact for him. This isn't a tragedy in the larger sense, but it would be a personal tragedy. He has already lived seven years without any tangible evidence of his father's supposed love for writing.

So, in this regard, $500 is a small price to pay to stimulate my waning desire to risk my pride on another attempt at crafting my narrative. In this regard, the fact that my Chromebook fails to support Android apps the way I expected it to is a miniscule concern. Alas, I am an incurable problem solver. I can't simply accept the way things are when there is a better way in sight. I've tried.

It seems ChromeOS has three "channels" available to the end user. There is the stable channel, where everything is meant to work the way one would anticipate. This is the bug-free and dependable environment Google is selling as an alternative to other computing platforms. For a trouble-free Chromebook experience, the stable channel is the only option. There is the beta channel where most of the bugs have been eradicated. This environment isn't guaranteed to be stable, but it is pretty close. There are potentially more features to be found in the beta channel. Google allows access to new capabilities not fully developed to the point where they can be safely added to the stable channel. Lastly, there is the dev channel. This is the "unstable" version of the operating system that grants access to features and ideas which haven't been developed very far yet. This channel is meant to provide access to the earliest additions to ChromeOS, but comes with a sort of "use at your own risk" caveat. Things may not work as expected on this channel. In fact, your Chromebook might crash or lose data. Apps and features might crash unexpectedly. That's the tradeoff.

Having enjoyed ChromeOS on the reliable, Android app desolate stable channel for a few days, I was compelled to abandon it in favor of the dev channel, where I could experiment with the missing feature I anticipated so voraciously. Having done so, I can say with confidence that running Android apps on my Chromebook, even in the current dev state is pretty wonderful. It's not a thing that Google can really sell, though. I would characterize my usage of Chromedroid as light. I am not trying to be an app power user at this point. I just wanted to fiddle around with some games to see what the experience would be like on a large screen.

For the most part, the large screen Android experience has been satisfying for me. I have invested my time mainly in puzzle games, where the occasional, inexplicable lag is a non-issue. Mini Metro runs without a hitch, and I really prefer playing it on a 12 inch screen to a 5.5 inch screen. Ankora works well. The occasional lag is noticeable, though it doesn't really affect the gameplay. I like this type of game with a mouse instead of a finger, so I would say this one is also better on the Chromebook than the phone. Almightree is, again, easier to use on the Chromebook and better suited to the mouse in my opinion. It is also less fun, because its design flaws become more apparent in this environment. Zookeeper works fine, though this is an instance where I feel the smaller screen works better for the game. Shoot the Birds has some obvious ChromeOS oddities. However, since this one doesn't really work with any Android device I currently own, I am happy to be able to enjoy it again. Beyond some aesthetic concerns, it works fine, so it is another win. Lost Echo barely functions and although I paid a higher price for the game, I've already abandoned it. I thought it would be a good candidate for Chromedroid awesomeness. It is not. Vainglory does have game-affecting lag issues. They seem random to me as the user, having nothing to do with the intensity of the game itself. Most of the time, Vainglory runs as smooth as butter - even better than what I can achieve with my phone. But there are a few scattered moments where it becomes unresponsive for a second, which cause problems in a MOBA environment. Overall, though, this is a much better experience on my Chromebook than it ever was on my phone.

With these experiences in hand, I am reluctant to give up my access to Android apps on my Chromebook. There are other things going wrong with the ChromeOS experience as a result of my entry into the dev channel. For instance, Google Drive is completely unusable for me. The worst shortcoming is that I can't edit or view Google Sheets on my Chromebook any more. I have to use Chrome Remote Desktop and connect to my Windows PC to use Google Sheets.

In light of these problems, I know there may soon come a day when I have to abandon Android apps as a thing on my Chromebook in favor of ChromeOS being the thing. I am disappointed about this, but apparently shoehorning Android onto ChromeOS isn't such a simple thing. Who could have guessed?

On Chromebooks - First Week [Part 05]

Body Issues

Although I am not generally a fan of the style used for the Asus Chromebook Flip C302, there is a lot of good here. I enjoy simple and understated devices. What makes a device understated is a matter of opinion, though, so I will share mine. To me this is something that is not flashy or gaudy, yes. It is also something which is unassuming and, often, utilitarian. Sometimes I admire function over form. Sometimes I don't. I am not certain even I could say what the difference is between my admirations. I am not even certain I wouldn't assess devices differently at different points in time.

The Asus Transformer Prime had a style I loved. There was excellent attention to fit and finish. The entire device was made of aluminum, which made it heavier than it needed to be, but also made it feel nice and solid in the hand. It was anodized aluminum with a dark purplish blue hue that looked almost black from a distance. I felt the device would not stand out in a crowd, or even be noticed in any particular way when sitting on a desk. It could look akin to a digital picture frame when turned off. Despite this, holding the device felt very special, with smooth finish and solidity. It also helped that there were very few tablets on the market with this level of attention to detail at the time. The iPad was similarly well appointed, but in flashy silver instead. I don't know that it would be fair to call an iPad gaudy, but it was definitely more flashy than I prefer.

The Asus Chromebook Flip C302 is more like an iPad than a Transformer Prime. It is entirely silver and it is definitely noticeable. Most of the professional reviews I've read of the device like to compare it directly to a Macbook Pro, so I am given to understand the body is in an identical style. Fit and finish are excellent, so I have complaints in that regard. Some seams can be seen, but none are obvious and none manifest any sort of gap flaws. The body is made entirely of aluminum with a drab silvery hue. I suppose some people might find it unassuming, but compared to my former devices this one practically screams "touch me I am awesome" which isn't my preferred look.

On the other hand, while toting my 10 inch tablet as a laptop setup, I generally noticed many dubious sideways glances. I never really felt like a professional writer because the diminutive form factor and tightly packed keyboard were not great for the exercise. It was very functional, but only with a good amount of adjustment. I can imagine some people might not even be able to use the keyboard, which honestly felt really small in use. This Chromebook feels nothing like that. The keyboard is spacious and comfortable and the device feels like a serious tool in use. I can't imagine anyone looking at this computer and thinking it just a toy, it has the air of professionalism and production, which are nice feelings to have accompanying one's laptop.

The aluminum itself is apparently called "soft touch" which means almost nothing to me beyond the fact that it does not feel cold and hard. It does not feel glossy smooth either, though it is also not rough by any measure. In all, I would say "soft touch" is a good description of it. While this feels nice - even comfortable - I have noticed the aluminum appears especially susceptible to scuffing. The smudgy scuffs aren't really an issue, though. One could say they add character.

Overall, the body feels satisfyingly solid, which is encouraging given its impossible thinness. Intel, for all its faults, has really done marvelous things with the core-m architecture to allow for such a thin, light device that doesn't require any exhaust vents or fan ports. Despite this generally encouraging strength, I do notice just a tiny amount of flex in the center of body between the keys of the keyboard. The keyboard itself has no flex, but the metal around the keys can be flexed inward if pressed in the right spots. I don't know if this will lead to any damage in the long-term. For now I am satisfied to ignore it and avoid putting pressure in those spots. I would also note I observed identical flex in my Asus T100, even though that device has a much smaller chassis.

The wrap-around hinge supporting the screen is bafflingly solid. After examining it for several days I cannot determine what gives it strength, but I am happy it works well. It is possible to position the screen at any desired angle, which is helpful. This device has a tablet mode, so the strength of the hinge helps alleviate concerns that the transformation of the Chromebook would eventually cause problems.

Speaking of tablet mode, it is well formed and executed for what it is, but I do have some comments about using this device in the place of an Android tablet (which is my intention). Moving from a laptop with a keyboard to a tablet is fairly slick. The system response is appropriate and immediate, though I don't know what triggers it. I suspect the connection of the magnet in the lid with the magnet along the lower edge of the body disables the keyboard and touchpad. This is almost always perfectly effective. I have noticed a time or two when I had inadvertently pressed the volume keys built into the keyboard and the volume changed in response, which is not the way it should work. So, the system isn't perfect, but it is almost there.

Using a 12 inch tablet can be exceptionally awkward, depending on positioning. In fact, using a 10 inch tablet can be awkward as well. The most natural and comfortable feel for a tablet I've found is in the 7 to 8 inch form factor, which closely resembles holding a novel. 10 inches and 12 inches is more akin to holding a textbook in repose, which is to say it likely isn't something most people would want to do. I've more or less committed to attempting the feat, so I won't devote too much thought to complaining about it. I merely wanted to note that if the sole goal is content consumption, there are better systems for it.

My goal is not simply content consumption, though that is a part of it. My goal, as stated before, is to find an all-in-one device that suits these varied desires inclusively and at an acceptable cost. So, having acknowledged there is discomfort in holding such a large device, let me speak no more of it.

The Asus Chromebook Flip C302 is not a particularly heavy device in my experience, though comparatively speaking it is a beast. It weighs 2.7lbs. Compared to almost any other laptop I've spent time with, it is amazingly light. However, in terms of tablet performance, it is comparing to the 1.29lb Asus Transformer Prime I loved and the 1.2lb Asus T100 I also loved. It is a bit more than double the weight I am accustomed to holding. What I've determined anecdotally is that the weight doesn't matter nearly as much as the size. As the largest device I've owned, it is the most awkward but not by a large margin. I don't have any particular trouble holding a 2.7lb device for a half hour or so. I wouldn't attempt to lie back and watch a movie with it in my hands. Honestly, I wouldn't do that with my phone either, so there's nothing lost for me in this observation.

I don't think the tablet mode of the device would be for everyone. I have trouble envisioning a time when I would have any desire or capacity for sitting with a tablet longer than a half hour stretch. I have an entire family to keep me busy and sitting around tapping on a tablet screen is not actually very interesting by comparison. I usually play games in 15 minute spurts, for which the tablet is not only comfortable enough in size and weight, but is also quite pleasant because of the relatively enormous screen.

My final complaint against the tablet mode of the device relates to the flipping form factor itself. I find it quite off-putting to rest my fingers on the keyboard for support as I am holding the device. This method fills me with concern, nay, worry that I might be damaging the hardware. It is theoretically possible to hold the tablet from the opposite side, where most of the support would come from resting my fingers on the edges around the touchpad, however, I've not found this to be the natural method for holding it. I think this is mostly because there is a much more accessible bezel along the bottom edge of the screen. This sort of invites the user to place their hand there instead, which means the fingers will rest on the keyboard.

Despite the downsides, there is a lot to enjoy about the 12 inch tablet that is the Asus Chromebook Flip C302. The screen is large, beautiful and responsive. The games I've installed and tested scale well and are generally easier to use and enjoy with a larger screen. On my phone the controls will often cover what seems to be the majority of the screen, or be too small to handle. Scaled up to the larger screen, the controls are easier to select and appear to also scale to an appropriate size for the screen, meaning they don't still cover the majority of the application. I suppose this is, to a certain extent, dependent on the app itself and who developed it, but I have found it to be a really nice change.

The bottom edge of the screen has a slight rounded bump, which I take to be necessary for the hinge. It provides very nice leverage while holding the device and also makes portrait orientation vastly preferable to landscape. Whether portrait or landscape is ideal for the current application is up to the application itself, so this doesn't always work out for the best. Even so, holding the device like a book is really quite comfortable.

All in all, I am very pleased with the tablet side of this device. I can definitely still see a strong argument for owning a dedicated Android tablet and I don't think convertible Chromebooks are going to replace those at any point. However, if searching for a happy medium which includes both laptop functions and tablet functions, this is it. I won't be buying a tablet nor do I feel any need for one.

On Chromebooks - First Week [Part 04]

Battery

Battery life is a subjective thing. I know that sounds odd, because even as I type it my mind objects. Which is to say, batteries drain in an objective manner, so "battery life" ought to be an objective quantity. It isn't, though. It depends on the needs of the system and the usage scenarios applied. These are objective things, perhaps, but working together in unpredictable ways they make a device's "battery life" more a matter of perception than quantification.

I have no idea if the battery life of my new Chromebook is better or worse than my previous, Windows-based convertible. This is mostly because I keep the former device plugged in at all times. I had no confidence at all that the Asus T100 was going to get me through an entire day on a single charge. In fact, if I left the device on - but locked and closed - for the duration of my drive home from work (about 20 minutes), it would arrive with less than half battery remaining. I doubt it was always this way. No doubt, years of leaving it plugged in at all times has produced undue strain on the battery it has.

Other than this anecdotal evidence, I have only my memories to aid me. I don't recall the T100 being particularly adept in the longevity department, but I do know I used to take it to the YMCA and write on it for an hour each day. I also know I never had any troubles with the battery during those excursions. I think it is safe to say that device might have given as much as five hours of use (probably not heavy interweb browsing, gaming or video watching) on a single charge in its prime. It is no wonder I kept the device plugged in.

The device I used before that, and the one I did far more writing on, was the Asus Transformer Prime. Again, I have very few memories of its actual battery life because by the time I was actively spending time away from any outlet I had already purchased a keyboard dock for it which essentially doubled the battery life of the device. For the Transformer Prime, battery life was never an issue. I could use it for twelve hours uninterrupted without any worries.

Moving back to the present, I've been testing my new Chromebook as an actual laptop. I don't want to have to plug it in or worry about the battery. For the most part, it lives up to this expectation. So far, it has lasted through my entire workday of 10 hours without actually running out of battery even though I am using it for always-on music and occasional typing. This kind of use isn't really constant use because the screen turns itself off while unattended. Doubtless there are other efforts at play which are extending the battery as much as possible. Regardless of what is factually happening, subjectively the battery life seems very good to me.

I have the confidence to grab my Chromebook and head to any place feeling assured I would be able to use the device for whatever needs I might have. I may need to charge it afterward, depending on the duration of the day, but it appears to fulfill my needs. I don't know if the battery life will remain exceptional as time marches onward. These devices only allow for a limited number of recharges before the battery's life cycle has ended. Using a power cord is hardly the worst fate I can imagine, though. The only real ramification of that eventuality is the tablet mode would cease to be as effective.

Keyboard

I ultimately made the decision to choose the Asus Chromebook Flip C302 over the Samsung Chromebook Plus for two reasons: internal storage and the keyboard. I've already covered why I think internal storage is much less of a factor than I had originally assumed. Now I should cover the keyboard.

Firstly, the keyboard has backlighting which is a big deal for me. I am not sure why it is so important to me as I never look at the keyboard while typing. Nevertheless, I have trouble accepting any keyboard that doesn't light up. There is one logical reason the light up keyboard has important, which is that I never learned touch typing. I taught myself to type. While I range in speed between 80-110 words per minute, I do so without any real technique. I've called what I do "advanced hunt & peck" which seems an adequate description. Once I get started, I have no need to look at the keyboard again, but just when I place my hands on the board, I need to know where to find the keys. In the dark, light up keys help with this tremendously. The other possible reason is that I am simply a snob. Having attained the glories of lighted keyboards, I am unwilling to give up my prize. Whichever it might be, Asus has it and Samsung doesn't. This is inordinately meaningful to me.

Secondly, the keyboard has a snappy and responsive feel to it. I would be lying if I claimed I was not disappointed in any way. The advertisements for the Asus Chromebook Flip C302 (yes, I will continue to type its full name) had portrayed the keys as making a loud and abrupt snapping noise when pressed. This is not true. These keys are silent and soft, just like nearly every other laptop key in existence. They have shorter travel than I am used to (likely because I spend most of my time on full stroke mechanical keyboards) but not in a bad way. Sometimes keyboards with very short keystrokes are a bane to my typing because the keys tend to activate at unexpected times. Not the case here. The short travel also helps to mask the wobbly post feel of scissor-switch keys. They aren't actually wobbly, of course. It is just play in the scissor mechanism (and the scissor mechanism is far superior to other membrane alternatives discounting Razer's "mecha-membrane"). It's not the best typing experience I've had. It's not even the third best. Still, it is a really good feel. I have no trouble sitting with the Chromebook and typing for extended periods. I have no real desire to attach any other keyboard to it (except for the times I just have a desire to use a different keyboard).

Thirdly, the sizing of the keyboard is exceptional. I hadn't anticipated the differences in keyboard layout between a standard qwerty keyboard intended for a Windows environment and a qwerty keyboard for ChromeOS. The F1-12 keys are gone as are many of the superfluous Windows-specific keys typically added to the bottom row. There could be function keys on this keyboard, as there is a row of action-specific keys designed for ChromeOS along the top but there is no purpose for them in this environment. The result of these differences is a group of relatively large and well-spaced keys, which surprised me given the Chromebook's diminutive 12" layout.

Lastly, the Chromebook suffers from the same problem as every other laptop with a touchpad in that while one is typing one's palm will move the mouse and occasionally click in unexpected places. I can't criticize this device for a problem that exists with every device of this form, though. The touchpad is actually positioned fairly well and the problem manifests less often than I have noticed on other devices, so that isn't nothing.

Overall, I am not entirely surprised that this is the best keyboard Chromebooks have to offer. It is a really good keyboard. I in no way object to the idea of spending much or most of my time typing on it, and that's a pretty big plus for the Asus Chromebook Flip C302. Is this a plus for Chromebooks though? Not at all. There are great keyboards all over and there are better keyboards out there. It's just a hardware thing and this particular hardware is great.

On Chromebooks - First Week [Part 03]

While getting my brand new Chromebook up and running, I began to ask myself the typical questions. Mainly, I wanted to know what the capabilities of the machine were. I wanted to know where to find the productivity software, games and files.

Productivity software lives as extensions of the Chrome browser, and I've already discovered many of my preferences in that regard, so I was well set.

Games are spread across two separate ecosystems within Google's larger structure. Some of the games live as Chrome extensions and the rest live as Android apps.

Files were a bit more of a mystery to solve. There is no explorer interface built into the basic computing experience. File browsing is a separate activity with a dedicated application to handle it. This isn't necessarily a bad thing, but it is fairly far removed from the Windows experience. ChromeOS views the computer as a web-first machine. Windows views the computer as a files-first machine. There are a lot of logical reasons for this difference, but the upshot is a difficulty in my learned behavior. I tend to think about computers as file systems which have tools built atop them. ChromeOS feels more like thinking of computers as mechanical UI components. There really isn't any focus on file systems or the underlying architecture supporting my on-screen activities.

I have a lot of thoughts about this difference. I can see some benefit in both. I don't think just because the Windows way is the old way, it is necessarily bad. I understand the idea behind an experience-first UI. It is sensible in its own right. However, a files-first UI is pragmatic. After all, the experiences offered by a computer are all ultimately file dependent. Either way, I decided to simply accept the ChromeOS approach and see where it took me.

It took me nowhere, really. ChromeOS seems to pretend files don't exist, so I pretended right alongside it. For the most part, this worked. All of the basic and native experiences offered by the Chromebook are uninterrupted by the relative lack of file interaction. I can name documents and I can even save them locally, if I so choose. There is no real indication of where I have saved them locally and no effort to present an accessible container where I can locate these local files.

In many ways this is beginning to elucidate Google's approach to storage and particularly external storage sources like Flash drives and memory cards. Some people have posited that Google doesn't want to become encumbered with concerns over the relative value of external storage sources. Which is to say, some memory cards work better than others, but Google can't police what you put into your phone. I think there is validity to this suspicion, but I think the approach goes much deeper than this. ChromeOS wants me to ignore files and storage altogether. It gives no place for me to worry about whether I need to upgrade my USB drive or insert a better memory card. The impact of these decision is opaque in the user experience.

I think there is some brilliance in this approach. In terms of differentiation, not needing to worry about whether or not I have the space to accomplish a task feels freeing. It is an interesting vision of the computing experience. Perhaps a less distracted version of interaction. I like the idea. However, practically speaking, it doesn't completely work. I do still run out of space. I do still need to find my files. I need to, because I still want to do things differently.

Strictly in terms of my experience as a writer, learning to operate in the way ChromeOS is asking me to is probably beneficial. Stop worry about where my files are and how to manage them. Focus instead on the project I am working on. Chrome will make sure the files I need are at my fingertips when I need them. I have yet to encounter a circumstance where this version of computing isn't working as intended with ChromeOS. I haven't encountered a lot of circumstances yet, so I can't judge ChromeOS on things I don't know.

Google Drive makes my writing platform agnostic in a compelling way. It is a first party experience on the Chromebook and it is easily available everywhere else I do any computing.

Outside of writing I ran into some walls fairly quickly, though. For instance, I have a series of video files I've captured from a project I worked on. I haven't finalized the files yet, because I want to review the video conversion to ensure there are no obvious flaws or defects due to compression or trimming. I don't want to add these files to my server until they are finished, but I need to be able to watch them in order to finish them. I wanted to toss them onto my Chromebook so I would be able to review the files wherever I might happen to be that I could find some time to watch.

Chromebooks have a file browser built in. It isn't the main thrust of the operating system, but this video project is the type of project which demands an interface like that. Which is to say, I won't simply plug the files into my Plex server, where they don't really belong. They have to properly finished, named and categorized before I would feel comfortable doing what I would think of as "publishing" them to my server. My media server is no testing ground. I don't currently have a second server, though this is potentially a work-around I could use by setting up a testing server where I can share unfinished files for review. It's not a bad idea either, but it isn't something I am ready to commit to yet. Therefore it isn't relevant to this project. This leaves me with the basic and familiar file handling approach to the need. And this is something ChromeOS doesn't excel at.

Opening the file browser is straightforward. It shows a simple interface which displays my Google Drive, local downloads and SD card. Perfect. If I insert a USB drive, it shows up immediately in the window. Now that I know I can use a USB device to transport files, I know I will be able to transfer my videos for review, so I know the issue is addressed. However, using a USB device isn't the ideal method. If possible, I'd like to simply access my file server directly and copy the files to my SD card. Accessing a networked file system is something even Windows has struggled with in different versions. Not any more, of course. File sharing in Windows 10 is as simple and straightforward as I can think it should be. Simply create a homegroup, share folders to it, join it and you're set. I don't know how it could be easier without sacrificing any sense of security.

So, does ChromeOS replicate this ease of use? Not natively. Not at all, actually. There is no method built into the file browser to explore a network or a file system. The ChromeOS file browser shows only the locations it thinks are accessible file storage devices. These entities can be explored, but new entities cannot be discovered. I decided to Google the problem and immediately discovered Google had addressed this shortcoming. It is not native to ChromeOS, but a Chrome app called "Network File Sharing for ChromeOS" has been provided to support my need. Wonderful. I installed this app, connected to the samba server share for my video project drive, selected the files I wanted to review, copied them, selected my SD card and pasted the files. All was exactly as simple as I had hoped.

The problem is, the file copy procedure was painfully slow. Then it stalled and cancelled itself. Annoyed, I tried again, but with a single file. This time it worked as expected. I continued, copying files one at a time with success. I think this is an odd limitation, but I can work with it if needed. Then some files refused to copy at all. Then the shares reported as disconnected. I couldn't get them to reconnect. I turned the Chromebook off and then back on and the shares reconnected. I tried copying a file again. The share immediately disconnected.

Now, I hesitate to say this is the fault of ChromeOS. I've only set these shares up for a Windows to Windows transfer, so there may be issues with the way the directories are shared that have been invisible to me because Windows is working so hard to make everything easy. It may be that ChromeOS is perfectly capable of communicating with network shares in exactly the way I am expecting. I haven't seen it yet, but I am not discounting it.

The problem I see here is that Windows is files-first. Everything about the interface is offering me tools to dig into problems like these, should they arise. ChromeOS is not concerned with files. There is a way to access files, but nothing else. It is presuming the heavy lifting will be done elsewhere. Strictly in terms of my Chromebook experience, I feel completely powerless to address the problems I am having with the network shares. I opted to copy the files via USB drive. That worked perfectly and that is the extent of what I can do with my Chromebook.

On the other hand, the server is running Windows. So, Windows is the ideal interface for solving what I might presume are Windows problems. This could run no deeper than two ostensibly competitive operating systems not working very hard to support each other. But in this paradigm, Google is asking me to use their ecosystem exclusively. So, where is my alternative to a 15TB file server in the Google ecosystem? It is Google Drive, and a very expensive monthly fee ($199.99/month works out to $2399.88/year). If that's where I am supposed to go with the problem, then Windows is suddenly no longer the more expensive option. Running my own home server is vastly cheaper than paying Google for the privilege (My file server costs average out to about $400/year). Therefore, I still think the onus is on Google to find a better way to deal with problems like these. Providing me a cheap computer is great. I am interested in it because I don't have money. I'd just like to see the proposition stay inexpensive.

On Chromebooks - First Week [Part 02]

So, I've committed to working with Chrome/Android and I am happy with that decision. Therefore everything in the world of Chrome is great - or at least acceptable. Right?

Not exactly. I feel like the question Google wants people to ask themselves is: "Can I live with just a Chromebook?" It's a reasonable question under some circumstances. I am certainly asking myself that question each day and I am choosing to do so largely without any coercion from Google. This despite the fact that it benefits Google greatly for me to invest in their ecosystem. By choosing to do so I am giving them everything they want. Even so, I fail to see the evidence of Google trying to push Chromebooks on me. I feel more like they have created Chromebooks and then winked at me, shrugged and said: "We can live with just a Chromebook. Can you?" That's not exactly strong advertising. It's also just my feeling, so it could be that I am simply missing what is happening in the world at large. It wouldn't be the first time and it likely won't be the last time.

My reasons aside, there are other great motivations for asking yourself this question. The most compelling question right now is: "Do I have to spend that much money on a computer?" For the most part, Chromebooks are there offering a reasonable alternative that most people could happily live with and doing so for a fraction of the cost associated with systems based on other platforms. Another strong question is: "Do I have to constantly live in fear of viruses and malware?" ChromeOS doesn't solve the problems behind the question, but it certainly mitigates them. It mitigates them to the extent that one could hand a Chromebook to an individual with no experience or tact in their online usage and reasonably expect the computer would continue to function unhindered for years.

But while Google is offering this, there are enormous gaps in the computing experience. Windows has decades of development invested into its platform and not just from Microsoft. It is truly amazing the wealth of tasks which can be accomplished with a Windows computer. Chromebooks are not really there. I've mentioned it is possible to handle audio and image editing with a Chromebook. This is true, but not exactly comfortable. Some of the discomfort stems from the fact that the system is different, so accomplishing things takes some adjustment. Some of it stems from the fact that Google has no interest in expanding ChromeOS to the extent that it can handle the types of things Windows can handle. Google has a very clearly painted corner they are operating in and they aren't planning to venture very far outside this region. Audio professionals, look elsewhere. Google isn't building a solution for you. At least not in ChromeOS. Video professionals, don't give it a second thought. It simply isn't for you at all. Developers move along. ChromeOS isn't trying to suit your needs.

None of the limitations inherent to the goals of ChromeOS are overtly bad. Google has a clear vision and excellent delivery on an inexpensive product that meets the needs of, frankly, 99% of established computing habits. There is a storm on the horizon, though. Google might be fine to leave wide swaths of professional interest to Microsoft, but Microsoft is not fine with leaving the rest to Google. The costs of Windows based computers are dropping and the relative strength of those offerings is increasing. Microsoft is investing heavily into this market and a day is coming when ChromeOS will no longer have the cost/performance edge it is enjoying now.

I also ask myself the question: "If money were no consideration, would I buy a Chromebook or a Windows laptop?" Invariably, the Windows laptop rises to the top. It can do the things ChromeOS can do, plus more. Of course, if money were no consideration, I would just buy both for fun. But that's not the point. The point is whether there is a compelling reason to use Chromebooks aside from the cost differentiation. Once cost becomes a non-factor, wouldn't I simply prefer to use Windows? Presumably, yes but as I work through this experiment I wonder if I might find some things about ChromeOS which are compelling enough to make me reconsider.

As a computer enthusiast, I struggle to see a strong argument for choosing ChromeOS over Windows. As simply a writer, where Windows and ChromeOS are on truly equal footing, things are less clear. So far, just having a Chromebook has been refreshing to my desire to write. I value this, but don't necessarily ascribe it to Chrome. I haven't fully worked out my feelings on the subject, but hope I can catalog their development.

On Chromebooks - First Week

I simply cannot bring myself to talk about Chromebooks without first talking about Android. The two are tied together for me in ways I must explain before I feel like Chromebooks make any sense at all.

I dove into Android because it was free and open source. At the time, Microsoft was doing or threatening to do all manner of things with Windows that I found distasteful. I didn't have any sort of foundation for understanding an operating system as a service offering, which is what Microsoft would eventually move toward. I thought of things solely as possessions. When I purchase Windows, I expect to own Windows with no further obligations to the people who programmed it. I still hold to this thinking as a default setting, but as time has passed I've come to understand how and why companies are moving away from this form of thinking. Yes, I agree most of the motivation behind this is greed. However, some of the motivation is also, I think, longevity. Companies and corporations are becoming transient things in our culture. We've removed loyalty both from employee to employer and from employer to employee. It's been replaced in most instances with loyalty from customer to company, but not necessarily from company to customer. Generally speaking, I think there is more wrong with this generation's corporate culture than there is right. My point is not to enter a discussion about these things, though. My point is to describe my motivations for approaching Android when I did.

I was uncomfortable with the rumors of Windows 7 becoming more closely controlled by Microsoft and more dependent upon them as a company. I was uncomfortable with the idea of relying on this company. I wanted to buy an operating system that would just work for years to come. Sadly, this isn't possible any more. While I was fearful of what Microsoft might take from me in their bid to increase profits at my expense, I failed to consider what black hats were going to be taking from me for the sake of their own profit and amusement. The world where purchasing an operating system could be a one-time interaction has passed away. Constant interference from malicious actors now necessitates constant reliance on the developers of the software we use. My mind is even devious to imagine some of this problem might have been manufactured by companies like Microsoft themselves. Whatever the case may be, while I didn't wish to accept a relationship with Microsoft for access to the service now known as Windows, I eventually accepted it for assurances of increased security and the possibility of avoiding eventual identity theft (my identity has been stolen regardless).

In my reluctance to embrace this brave new future, I began searching for an alternative to windows as a platform for my computing needs. There were really only three alternatives I knew of to consider: Apple's OS, Linux and Android. 

Linux, on the other hand, was and is a world of promise. It is free, stable and fast. It also takes some fair amount of time and effort to use. It was an is an ideal solution, but some experiences I had with LiteStep, a windows explorer modification became a motivation to avoid it. I found I truly valued a user interface which worked without too much effort on my part. I don't know enough about Linux to say definitively that it does not offer this, but my suspicions of it were high enough to redirect my interest.

Into this line of thinking entered Android, a Linux variant developed by Google, which was already a company I appreciated. I appreciated Google because I saw them as a company providing services to me for free. I didn't understand how Google could do this, but I was in favor of it. They gave me the best email experience for free. They gave me Google drive for free. They gave me Google maps for free. They gave me Google documents for free. They gave me Google wave for free (wave is now dead, but largely integrated into Google documents). These are only a few of the things Google hands out in exchange for a simple account with them. I was ecstatic and I ate it all up. Google quickly developed a lot of brand loyalty with me. So when Android came on the scene and offered me an experience like Apple's iOS and Microsoft's WindowsPhone except possibly better and apparently free, I ate that up too. My desire was to have a smartphone running Android and leverage this experience to determine whether Android could possibly become the Windows replacement I was still looking for.

By the time I realized that Google's business model was to collect all of my data and profit off it, I was far too invested in their ecosystem to ever consider abandoning it outside of data paranoia, which I am not afflicted with. I've come to terms with the cost of their service and am willing to accept it. I also have discovered that Android is capable of suiting many of my computing needs, but not all of them. There are two main areas that Android falls short of my expectations: 1) League of Legends (and, to a lesser extent, Steam) and 2) Microsoft Office. It is possible this may seem indicative of a relatively shallow computing experience, and that assessment is correct of some periods of my interaction, but not all. My computing needs encompass image, audio and video editing at different moments in my life. However, these needs can be and are largely met by the capabilities of Android. Well, image and audio editing are. Video editing is not really something I've tried to do on this platform. However, I've also lost my way in terms of video editing. I have no confidence in my capability or vision, so it isn't an interest I pursue any longer. 

As for the first shortcoming, there isn't really any solution. For general gaming interests, Android provides a compelling set of its own offerings that I've been known to partake. Even so, specific games I value on the Windows platform are simply not offered by alternative services. As a result, I've resigned myself to maintaining at least one Windows computer as a full-time resource for these interests.

For the second shortcoming, I am investigating alternative solutions. I know most people would be quick to talk about Google's office suite or Open Office as solutions to the problem. They are not. Speaking of Microsoft's Office suite, I am referencing, specifically, VBA and the easily accessible database front-end of Microsoft Access. I think I can supplement these things if I learn the right resources, but I haven't gotten there yet. Right now, I can accomplish amazing things with Microsoft Excel and Access, so I will continue my reliance on Windows accordingly. In the future, I think moving these skills toward PHP and SQL will be the solution to this dependency. This is more of a long-term solution, though.

Finding Android to be such a capable solution, I've invested as mentioned previously. I have purchased Android applications and games and familiarized myself with the ins and outs of the system. If I had to abandon Windows tomorrow, I don't think I would be crippled. It would still be an adjustment, but the adjustment is not opaque to me any longer. I have a good idea of what I would be living without. I am, in that way, ready to become even more reliant on Android as my primary computing foundation. 

This is where Chromebooks enter the equation for me. Although ChromeOS is not Android, the truth is it actually is Android. They are slightly different versions of the same thing built from Linux. That's not really why I say they are practically the same thing. I say it because Google wants its users to think of them that way. They haven't really pushed this very forcefully yet, but adding Android apps to Chromebooks is a big and telling step in that direction. Google doesn't appear to want these two ecosystems fragmented any longer and I am in favor of this type of thinking. There is also a substantial amount of evidence supporting something currently being called Andromeda. Google is actively working on the codebase for a project which appears to be all about combining ChromeOS and Android into a single operating system capable of running anything from either on any available hardware, seamlessly. That's an ambitious goal, but nothing too far removed from the activities of their competitors (Microsoft's continuum project comes to mind).

In light of these things, I've migrated my own desire for a new Android tablet to a desire for a Chromebook. I've had and interacted with a few Android tablets. The main Android tablet experience I enjoyed was with the Android Transformer Prime of yesteryear. It is a painfully slow device by today's standards, but one I used to validate my suspicions that Android could be used for serious writing pursuits. My second book was written almost entirely on the Asus Transformer Prime after I moved from Open Office to Google Documents as my primary writing application. One trepidation I have had about upgrading this old reliable tablet to a newer model is the platform's focus on consumption rather than creation. Yes, I have confirmed the platform can be used for content creation, but it is truly focused on facilitating consumption. I don't dislike this aspect of it, I am just observing it. As a result, I found myself spending far more time reading, watching movies and playing games on my tablet than on focused writing. Moving to a newer version really only provides benefit in terms of the content consumption side of the experience. The old tablet is still equivalently capable in terms of writing and there is really no need to upgrade it for this. 

In some moments, I even think it better to keep the old tablet as games outstrip its capabilities. Now that it can no longer really be used for consumption, it is even more ideally suited to my real purpose for the device. At least the only real purpose I am willing to admit. So, I've not updated my tablet for years. (There is also the fact that new tablets are expensive). 

Chromebooks, on the other hand, are built from the ground up for writing. Their development has resulted in an even more limited environment than the Android tablet I'd become used to. There is a good argument there for a reasonable update to my writing experience. Yet, I didn't want to invest just for the writing experience. I know I often claim such, but I strongly felt the ChromeOS environment too limited for serious consideration. I felt that way, that is, until Google announced Android app integration last year. Once that direction became official, I was all-in on my desire to own a Chromebook. At last a device aimed at writing, with a larger and more comfortable keyboard paired with a better screen. This was a real upgrade that I could feel was worth my money.

I would have purchased a Chromebook last year, but there were two limiting factors. First, I don't have the money to simply purchase anything carrying a price tag over $100. These types of purchases require consideration and an accord with my wife. Secondly, I didn't find the 2016 Chromebook offerings compelling. Google worked hard to ensure their new Android app initiative was well supported by the existing hardware, but there is no denying these Chromebooks were not manufactured with the intention of supporting Android apps. I wanted to wait for something that was built with Android integration in mind. 

I found what I was waiting for in the Asus Chromebook Flip C302 and Samsung Chromebook Plus. So, I eagerly awaited these two offerings which, admittedly, carried a much higher price premium when considering their Android focus. In the end, I listened to reviewers who maintained the keyboard on the Asus Chromebook Flip C302 was the far superior experience. I am, ostensibly, purchasing this device for writing. Therefore, it is important to buy into the best writing experience possible. 

Now that I've done so, I'd like to share my experiences with this new ecosystem. I'd like to cover my hopes and expectations along with my disappointments and lessons along the way. This new Chromebook is going to be my primary computing device for the foreseeable future, so I might be able to provide some helpful insights to anyone interested in a similar path.