mirror of
https://github.com/hnasheralneam/hnasheralneam.github.io.git
synced 2024-11-06 15:45:54 -05:00
80 lines
No EOL
13 KiB
HTML
80 lines
No EOL
13 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta name="viewport" content="width=device-width">
|
|
<meta name="description" content="Hamza Nasher-Alneam's developer profile website!">
|
|
<link rel="shortcut icon" type="image/x-icon" href="icons/race.png">
|
|
<link href="https://fonts.googleapis.com/css2?family=Nunito:ital,wght@0,300;0,400;0,600;0,700;0,800;0,900;1,200;1,300;1,400;1,600;1,700;1,800;1,900&display=swap" rel="stylesheet">
|
|
<link href="https://fonts.googleapis.com/css2?family=Ubuntu+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap" rel="stylesheet">
|
|
<link rel="stylesheet" href="styles/styles.css">
|
|
<link rel="stylesheet" href="styles/thoughts.css">
|
|
<title>Thoughts | Hamza Nasher-Alneam</title>
|
|
</head>
|
|
<body>
|
|
<a class="home" href="index.html">Home</a>
|
|
<br><br>
|
|
|
|
<div class="content thoughtsblock">
|
|
<div class="article">
|
|
<h1 id="imessage-lockin" onclick="copy('imessage-lockin')">iMessage Lockin</h1>
|
|
<h2>Dec 1 2022</h2>
|
|
<p>Apple is known for its "walled garden"; a wonderful lineup of devices that work seamlessly together. But while their products may be great, they don't quite make up for the company's shortcomings, especially their refusal to play nice with other devices. All tech companies have some anti competition problems, like Microsoft trying to be Apple with Windows 11, Office, and Teams. May Steve Jobs protect us all from that horrible future. Every company puts their apps first, pre-installs bloatware, sorry, <i>software</i>, and generally tries to be your one go-to service provider. To make it clear, this is totally a problem that needs to be dealt with, and we can't let Microsoft, Google, Apple or anybody to have a completely locked system, no matter how wonderful. But at least while Android phones are competitors, they all use the same basic standards such as ports and messaging systems.</p>
|
|
<p>Let's start at the beginning. While the concept of SMS had been conceived in the early 80s, it wasn't until the 90s that it was actually implemented. SMS stands for Short Message Service, and supports plain text messages of up to 160 characters. This worked for a while, but by 2002 people wanted more out of messaging, so MMS, Multimedia Messaging Service, was created. It had support for images, links, videos, files, emojis, and more, and was pretty much globally adopted. These systems worked, but in 2007 another standard was created, RCS, or Rich Communication Services, which was officially released in 20016. It standardized features that companies had to individually implement before, as well as adding features from popular messaging apps, like reactions and other small additions that created a smooth texting experience. Additionally, it has much improved security, which is important when texting cross-platform (iMessage uses its own encryption). Basically, it wasn't revolutionary, but it was a great and necessary effort at improving and standardizing texting.</p>
|
|
<p>So 2019 comes around and Google declares that Android is adopting RCS. This is great, but Apple doesn't like standards, or Google. Thus the dreaded “green bubble” was born. On Apple's messaging service, iMessage, blue messages symbolize the other person is using iMessage, which means you can use reactions, high quality image and video files, and that the chat is end-to-end encrypted. Now if someone is using another device, like Android or Linux or HarmonyOS, that message will come in as green, which means iMessage has resorted to the primitive SMS and MMS standards to send you the message. Apple could have collaborated with Google to fix this, or just adopted RCS, but... they don't want to.</p>
|
|
<p>I believe it is time for a digression. You all know about Apple's lightning cable, unless you're a hermit who hasn't left their mountain for the last ten years. In 2012, Apple released a revolutionary new connector to replace their appalling 30-pin connector. It was small, beautiful, thin, and could be put in both ways. It is to this day one of the best connectors, obviously second to the superior USB-C cable. But the time for lightning has come to an end, and Apple should adopt the universal USB-C cable, which comes with benefits all around. It isn't revolutionary, but it has many small, much needed improvements. But Apple has reason to hold on to its outdated cable, and it's not nostalgia. Apple has a Made For iPhone (MFi) program that means for any lightning-certified accessory sold, they get a 2-4 dollar cut (the precise amount is not known, but this is a good estimate). Apple makes a huge amount of money off of this, and it helps retain a huge amount of control. This situation is nearly identical to the iMessage situation, and just goes to show that Apple is a corporation that will do anything to get as much money as possible.</p>
|
|
<p>But iMessage in a way is far worse. While lightning only affects people already in Apple's control, iMessage creates a bad experience for anyone who texts to an iMessage user. Google does their best to handle it on their end, but Apple is not doing anything to help. This situation has resulted in iMessage snobbery, where the people with the broken system look down on green messages, and this doesn't just stop at superiority. It has real consequences, like friends being left out if they have a different device. Additionally, peer pressure among the younger generation means that teenagers will often choose an iPhone just to "have a social life". This has resulted in <i>9 out of 10</i> teenagers who have phones owning an iPhone. I really can't see a company giving up total market dominance like that.</p>
|
|
<p>But don't worry! Because Google, who is strangely framing itself as the people's warrior, has created a Get the Message movement, with an accompanying #GetTheMessage hashtag to boot. And wow, are they serious about this. This is basically an attempt to make iPhone users realize their world isn't so perfect, and that they should join Android users in the fight for better messaging. They even hired some celebrities. I'm afraid Google hasn't noticed that Apple <i>never</i> listens to its users.</p>
|
|
<p>So far, this has been a one-sided battle. Apple is happy with its messaging monopoly, and has no reason to change anything. Google is not the hero though. While RCS is a great standard and it would benefit all users if Apple adopted it, this isn't about users. I believe in this situation the people at Google really care about users, but that isn't always the case. If they <i>really</i> cared about users, maybe their Pixel devices would cooperate with other devices, or Google wouldn't push their own products so much. This time though, they're right. #GetTheMessage!</p>
|
|
</div>
|
|
<div class="article">
|
|
<h1 id="reject-folding-phones" onclick="copy('reject-folding-phones')">An Argument Against Folding Phones</h1>
|
|
<h2>Dec 1 2022</h2>
|
|
<p>Unless you've been living under a rock for the last few years, you should have noticed a growing trend for foldable phones. Perhaps you thought it was cool, maybe you even considered buying one before you noticed the price. But why could anyone hate them? I'll tell you why it's a bad idea for everyone involved.</p>
|
|
<p>Let's start from the developer side of things. When building an interface, it has to be optimized for different screens. The two difficulties that arise are scale and aspect ratio. You can develop a website or app for a computer, and it won't take much scaling down to fit on a tablet or larger monitor. Some tweaks, yes, but nothing huge. Now developing for phones is different. Multiple OSs aside, these devices are tiny. And even if you turn the device into landscape mode, which no one does, the aspect ratio of the device is completely different, making the UI seem stretched. But that's not all, because every phone maker is determined to make all their devices have a unique shape, and thus, a new screen to be optimized for. You can already see how this is a nightmare, even without counting the separate code bases you'd need for each system, but it was about to get far worse.</p>
|
|
<p>In 2019 Samsung revealed the Galaxy Fold to the world. This may have been the first, but in their folly other companies were quick to follow. These weren't flip phones, they were smartphones that folded, a phone that looks like an ordinary or irritatingly skinny phone, until <i>wow, it flips open</i>, giving <i>twice the screen space</i>. How could this be less than perfect? It's the future! Well, sorry to break it to you, even with practical inconsistencies set aside (who has the time to flip their phone open every time they get a message? Most of the time the phone will stay closed, leaving you with a very thick but normal device), this is a developing nightmare. <i>Another</i> screen size to optimize for? So that's monitors, desktops, laptops, phones, and folding phones? Sure, a square screen looks nice, but not nearly enough people use it to make it worth developing for. Which brings us to the user.</p>
|
|
<p>User experience is everything. You might have a great device or operating system, but if you can't easily access the content you need it isn't worth it. Which is why people don't use Linux. Here was a bold new device, but it was about to face a greater challenge than the dubious press: getting developers to make apps and websites for their screens. Apple had great success getting developers to optimize for the iPhone and tablet, but that's not the whole story. Do you remember the Macbook Pro touchbar? Here's how that went down. In 2016 Apple unveiled the new Macbook Pro with a touch bar display where the command keys used to be. They flaunted how the benefits were unimaginable, with every app adding custom controls for easy use. But in 2022, Apple removed it from most of its Pro lineup. Why? Because the biggest feature, custom app controls, was never used by developers. Macbooks already have such a small market share, but for creators it might still make sense. But the fact that it was only on the Pro lineup, such an insignificant amount of users would have been affected that developers decided not to build for it. And <i>that</i> is the reason it was removed, not battery efficiency or whatever excuse they used. The new Dynamic Island feature on their Pro phones is the same mistake, and while there is a larger number of users, if they don't convince developers to build for this it will go the way of the touchbar and 3d touch.</p>
|
|
<p>So <i>what</i> was Samsung thinking? The phones are so expensive and niche that it makes nearly no sense to develop for them. If Android tablets had ever become a thing, then maybe apps would have been ready for that screen size and aspect ratio. But instead, Android apps are optimized for a normal phone screen, so opening nearly any website or app at full size is sure to be a bad experience. Why would someone buy a device where the core feature is extra screen if all their favorite apps and sites are warped and unusable? It just doesn't make sense. So you'd think that at least <i>some</i> phone manufacturers asked the geniuses behind their product design if this was a good idea. But <i>no</i>, everyone wants to get in on it. They think this is the Next Big Thing, and just about every phone maker has made or is rumored to be making a folding phone. But even with all of this aside, folding phones are <i>expensive</i>. The Samsung Galaxy Fold 4 starts at <i>1,799</i> US dollars. That is <i>not</i> a price most ordinary users are going to be willing to pay for a gimmick.</p>
|
|
<p>So, the folding phone. Smartphone makers are betting big when they keep making these, hoping that developers will build for them and consumers will buy. But the simple fact is, the smartphone market doesn't need disruption. The design we've reached, a flat rectangle, is basically perfect. It fits in your pocket, has an all-day battery life, and can run basically any task you want it to. And people are keeping their phones for longer, unwilling to buy another expensive phone that isn't noticeably better than their current one. I think this is the smartphone industry desperately scrambling to find some way to keep their exponential growth. But hey, that's just my opinion.</p>
|
|
</div>
|
|
</div>
|
|
<br><br>
|
|
<div class="footer">
|
|
<div>
|
|
<h2>Find me</h2>
|
|
<p>Github -> <a href="https://github.com/hnasheralneam">GitHub</a></p>
|
|
<p class="faded-footer">Many of my projects are on GitHub</p>
|
|
</div>
|
|
<div>
|
|
<h2>Contact me</h2>
|
|
<p>Email account -> <a href="mailto:hnasheralneam@gmail.com">hnasheralneam at google mail</a></p>
|
|
<p>Discord account -> <a href="#">namegoes.here</a></p>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
<script>
|
|
let url = document.location.href;
|
|
|
|
function copy(txt) {
|
|
let link = `${url}#${txt}`;
|
|
navigator.clipboard.writeText(link).then(() => {
|
|
console.log("Copied link!");
|
|
}, () => { console.log("Error copying link."); });
|
|
let alert = document.createElement("DIV");
|
|
alert.textContent = "Copied Link to Heading!";
|
|
alert.classList.add("tempAlert");
|
|
document.body.appendChild(alert);
|
|
setTimeout(() => {
|
|
alert.style.opacity = "1";
|
|
alert.style.bottom = ".5rem";
|
|
}, 200);
|
|
setTimeout(() => {
|
|
alert.style.opacity = "0";
|
|
alert.style.bottom = "-10rem";
|
|
}, 4200);
|
|
setTimeout(() => {
|
|
alert.remove();
|
|
}, 4400);
|
|
|
|
}
|
|
</script>
|
|
</html> |