A 'screenless smartphone'
vice.com
vice.com
> “Visuals may be half the fun of technology, but there are pros of owning a screenless smartphone, such as giving your eyes a break, saving moolah on high-roaming phone charges, and avoiding germs on screens”
> “… an adjustable base memory cable for your neck, and is charged through an A type C-USB cable pod“
“A SIM stands for security information management, and traditionally collects, monitors, and analyzes security-related data.”
This writer has never worked in IT before and is wholly unqualified.
Edit: I do not know who the writer is. The mangling of “SIM” is enough to know they should not be writing tech articles.
The problem is only one: PROPRIETARY APPLICATIONS
Could you write a custom and simplified Facebook Messenger client that would allow clear and complete navigation through hardware buttons or vocal commands? Abso-fucking-lutely!
Can you do it without Facebook's approval which will never come? Abso-fucking-lutely not!
"What’s the Value of Hackable Hardware, Anyway?" https://www.bunniestudios.com/blog/?p=6031
Although the hardware, the precursor, is more akin to a PDA than a smartphone it very well allows for mods targeting e.g. impaired vision, as the featured prototype of a braille keyboard shows.
Most open source software I've used has terrible accessibility, both for blind and sighted people.
[1] - https://ec.europa.eu/info/strategy/priorities-2019-2024/euro...
You got me so thrilled that I posted it for a discussion. Right here: https://news.ycombinator.com/item?id=33309576
This would actually create a nice loop, and it would (hopefully) make app Devs take supporting blind users more seriously.
To me this device resembles my Motorola flip a lot more than it resembles Apple's iPhone. And that's fine, but let's not try to stretch an already nebulous term beyond all recognition.
In the first ipod touch and iphone there was a flag set to not be able to create events in the calendar app! (Calendar was read-only).
Later updates fixed it but if you had an ipod touch you needed to pay for the update (maybe 15$?).
I remember it being huge that you could do that and pinch and zoom rather than use a d pad to walk around a bad render of a webpage.
https://en.wikipedia.org/wiki/Wireless_Application_Protocol#...
Post-iPhone that demarcation got muddled a bit by touch-driven UI and the occasional touchscreen feature-phone will be considered a basic "smartphone" by many, but in the historical context when that distinction still mattered it was all about the installables, and J2ME did not count.
PS: neighbor poster reminds us that the iPhone at first did not have user installable apps either, I guess that could be seen as muddling my demarcation line even more. But on the other hand the reality was that when it happened, the iPhone was so much a standout that nobody really cared where it would fit in the emerging field of mobile phone classifications, it was just The iPhone. And iirc "smartphone" as a term wasn't quite as established as we like to think it was, the conceptual bound were more clear than the name. When "smartphone" eventually emerged as the definitive shared superclass of iPhones and Android devices it inherited almost accidentally (and there's-an-app-for-that era Apple did not try too hard pointing out that inaccuracy...)
Mobile websites went through a phase where everything looked like iPhone menus for a while and that was often quite annoying because I was used to just reading normal web pages, even if they were often slow.
I think the iPhone made an important change in that it was significantly more powerful (and expensive!) than most phones people used. These devices were out there and they had been for years, but Apple normalised spending ever increasing sums of money on a phone.
On the Nokia side, Symbian S60 vs S40 indicated the distinction, with the former usually implying a ton of first-party features and a native SDK for apps that could offer functionality beyond the J2ME API limitations.
Windows Mobile also went through several revisions before we got to 2007. I believe Nokia had a few releases in the PDA form-factor as well, but the only real value-add there was being able to use webpages made for the desktop.
Many Palm OS devices came increasingly really close to a smartphone/iPhone concept and experience, especially when paired with a GPRS phone (over RS232, IRDA).
Handspring/Palm Treo (e.g Treo 180g) was probably the closest thing to the iPhone concept on many levels.
Had some Palm III, then a Sony Clié SJ30, and finally a Palm LifeDrive, when the iPhone was announced it felt like the most natural evolution (and actually with the first one two steps forward yet a step back because PalmOS had a wonderful app ecosystem)
I remember a college friend of mine playing games on his "smartphone" while sitting on the toilet in 2002. (The iPhone came out in 2007.)
His phone ran Windows CE, and I think it even had a browser on it. I even remember going out to look at "smartphones" in 2003, and later in 2005, and just being generally disappointed. The one that I looked at in 2003 was too expensive and clunky, (I was a college student on a budget,) and the one that I looked at in 2005 was too hard to figure out how to use. (Windows CE).
Ballmer's criticism of the first iPhone was that Microsoft had been shipping almost the same thing on phones with Windows CE for quite a few years. The big difference was the UI: The iPhone was a touchscreen and easy to figure out; Windows CE was difficult to figure out and used a stylus.
For example there are spatial audio libraries that can make sounds apparently originate from any location for a user wearing headphones. Why not use that to create a spatial user interface?
Speech-based interfaces are of course very important, but i feel like there could be much faster ways of doing "window management" or diving through standard menus by using synthesized sounds for feedback. This would be attempting to go a step beyond just playing a sample or sound effect, and conveying more detailed information with different aspects of sound texture.
One of the biggest advantages of screens is that they also act like short-term memory. I don't need to remember where I am in a document because the scroll bar holds that information, for example. I feel like it should be possible to do an equivalent thing with audio-only without it becoming overwhelming. Our ears can take in about as much information as our eyes, and we can also "switch focus" and ignore background sounds when not immediately relevant. I don't know of any projects that seriously attempt to do this, unfortunately.
I can't imagine providing much state to the ears constantly, monitors are pretty information rich... but maybe we could get ed in our ears. It is the standard editor...
Subscriber Identity Module?
Article: (proceeds to include a dozen unique-looking links which actually all go to the same exact analytics/tracking/shortening/affiliate link)
But I can’t get over the fact that this is just a glorified $29 dumb phone with a e-ink screen for ten times the price.
I have at least two screens with me at all times and that’s kind of the limit for me. Put the phone in the watch and bring back the iPod.
I just want a wearable that allows me to communicate with people, and get basic info from the web like weather. And that has better battery life. Here’s hoping…
https://www.youtube.com/watch?v=qDm7GiKra28
[1] https://support.apple.com/en-au/guide/iphone/iph3e2e415f/ios [2] https://support.apple.com/en-us/HT201443
You could give someone a smooth rock and they'd be able to use it as a smartphone no problem as long as you put on a normal OS (none of this locked down bullshit) and integrate the existing accessibility service well. There'd be loads of space for batteries and you only need to care about the limits if the capacitive layer, the screen tech itself doesn't need to be foldable!
Perhaps for tech service you'd need to add some kind of display out, probably over USB so you have hook it up to a hub and have a non-impaired techy service it if necessary, but there are opportunities here way beyond "just buy a screen you'll never be able to see".
The iphone’s accessibility works because it’s a core part of a device intended for anyone - not a weird bespoke ‘here is your blind phone’ device.
Regardless of how well-integrated the accessibility service is, it's accessibility tacked onto a device designed primarily for the common denominator. The system is oriented around communicating what's on the screen but the screen itself is an artificial limitation for those that don't see it.
A well-built accessible device like this should also work for people with good eye sight, as long as they have good hearing. Screens are distracting and attention grabbing, apps and websites are designed to suck up as much of your time as they possibly can, which is a reason many people use accessibility settings to set their screen to grayscale for example.
Portable smart speakers can be one solution for a world where everything tries to ruin your attention span by grabbing your attention. Combine the mobile app market and a novel design and you should be able to get a decent experience as long as the "accessibility" software is written well.
Sure, such a device would be fiddly for those that don't need accessibility per se, but I think a well designed project can leverage the huge mindscape that blind people navigating the world can develop to create human-device interactions that go beyond "here's a way to also use the thing developed for sighted people".
Blind people use cameras all the time for the same reasons sighted people do - sharing images with others! They have sighted friends and family too you know :)
Blind people want the choice to use all the same apps and experiences that sighted people do with their benefits and pitfalls. This is only achievable with accessibility baked in to an established platform - which iOS accessibility is, it’s certainly not ‘tacked on’. The marginal cost of a screen is so irrelevant.
In many ways what I’m saying is the same as any new entrant to the smart devices market - if it doesn’t use one of the two established ecosystems it’ll be marginally useful at best. For better or worse it’s iOS/Android from here on out.
Who'd thunk it; we're all weird now.
Pebble tried something similar with the pebble core, not sure what happened to it: https://www.techradar.com/news/wearables/pebble-core-everyth...
I'm assuming this thing's running Android under the hood and someone will figure out how to hack the hell out of it.
1. Triple press the side button if you have Face ID or the home button if not. This will turn on VoiceOver. 2. Tap the screen three times with three fingers to enable screen curtain. This will disable your screen with the exception of VoiceOver. 3. Same steps to turn these features off.
If you can learn how to use your phone with VoiceOver and the screen curtain, you will now get ~4 days of battery life.
Yeah, I'm out.
Could not tell you the amount of times that Siri has misunderstood me due to my accent, or Google Maps voice guidance has tried to summon eldricht horrors by attempting to pronounce "Länsiväylä". Voice is an awful interface and should not be a main/easiest way of interacting with any device.
I find Google's natural language AI extremely lacking in Dutch but I'm not switching languages to get my phone to do what I want it to do. I need to say broken sentences to get reminders to work right (the equivalent of "OK Google, remind me at 9 turn on washing machine" because any connecting words between the command and the input will be parsed as part of the input).
At least Google Assistant seems to work better than Siri, but I'm not sure if that's because Google's AI is better or if Apple's is just worse. If Google can't get it right, their tiny competitor will never be able to get this working outside their tiny target area.
Vice, if you are reading this, I could write you a better article in 30 minutes. I have IT certifications and a certification in Writing, which is more than your writers.
I do feel like we just lost a generation worth of “calling” skills with people somehow surprised when you just call and start talking. I wonder if we can get that back.
That's because the earbuds are not a platform in themselves, you can't run stuff on just the earbuds. They are connected to something, which is the platform, and outputs audio from what the platform tells them to.
So unless we come up with earbuds that have built-in computers, they'll remain an accessory to platforms and won't become platforms themselves.
Granted they do have a phone in the movie.
Interesting movie you posted (old) haven't seen it will put it on my watch list.
Frankly I'm never remotely seeing this as a successful product though (from a business perspective), a niche hype at best.
From how large a selection?
That’s the worst definition of SIM that I’ve seen in my life.