Skip to main content

The Emoji Ideal; Apple's Memoji and Samsung Galaxy's AR Emoji

I'm here to compare; Because digital dollmakers are a hallmark of my past, present, and future.


 

Galaxy's AR emoji were a surprise to me, something I learned when placing images for contacts. I realized I saw one multiple times on a website someone was using for personal branding. Besides that, I'm not sure I've ever seen them in the wild.

Maybe because I can't figure out how to get to the app on my phone without going to my contacts section - and no one else can either.

Because of their simplicity of the smooth heads, emotions on Apple's people emoji - memoji - look better to me.

 


 It's not animated here, so it's not as over the top as the Samsung ones.

 

Samsung's have an oddly fake quality, which is good in its own way. It doesn't lead into uncanny valley - neither options do. It's a quirky, insincere robot puppet with limited animations. Reminds me of Second Life or IMVU.

They give you more options - I was able to adjust ear tips (Pointy!) and minute details on the face. 

Also, bodies! The most Apple gives is a torso, arms, and hands (disembodied or not) so you can shrug and peace sign.

Samsung's clothing options are very pointed toward the Gen Z crowd - Oversized, bright clothing, pants with legs but the crotches are at the knees.

Perhaps this is an attempt to get Gen Z to care about Samsung phones as a cheaper, but just as good alternative - 10 years ago, there was a pretty classist divide between iPhone users and Android users.

 There's also an option to buy more clothing, including some from major studios.

 Apple is not here to overwhelm with choices; Simplicity is always their motto, and they stick with it.

SG AR is very reminiscent of the dollmakers of old - Something Gen Z may not be familiar with enough for a sense of nostalgia.


If I want to edit the base of the Emoji, it's an ordeal. A lot of the menu buttons have unclear purposes until you click.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory