[bborud]

reMarkable might do it for me if they had a more powerful CPU onboard and a way to get your code to run on it so the device can be tailored to solve more use-cases.

I'm hesitant to say I want an app-store, because it implies a lot of stuff I don't want, but something like an app-store would make it a very different proposition. It would turn a single use device into a platform. It feels a bit silly to point this out in 2021. I can't say I understand the reMarkable product strategy. There is something extremely Norwegian about it: let's limit our scope to what we're comfortable with and keep ambitions in check. We Norwegians like to play it safe - so we rarely make a difference when it comes to innovation.

I've been on the fence with reMarkable since it was launched. Waiting to see which direction it would head in. I think this announcement probably means it isn't going to be a device for me.

I'm simply not looking for yet another device that requires some form of ongoing engagement (monthly payment) to merely work. I try hard to reduce the number of things sucking money out of my account whether I use them or not.

In order to justify that it would have to be on par with my mobile in terms of "importance" - and right now the reMarkable kind of struggles to beat pen and paper for me. This makes me a bit sad, because I think there is a lot of untapped potential in eInk form factors. Especially form factors that lend themselves to interactivity.

I think reMarkable needs to multiply all their ambitions by an order of magnitude or two, find funding and get to work. This announcement feels a bit like they're giving up on having ambitions.

[idorosen]

They give you SSH root access to the device. There are many many apps people have developed for it, look for the reHackable GitHub repos.

(The SSH root password is in the help/about section where the open source licenses are listed.)

[bborud]

If you are going to run third party code on the device there needs to be a bit more than a hackish way to upload software to the device.

My dad isn't going to SSH into a tablet.

"Feature phones" illustrated this. I wrote a few (very simple) apps for Symbian phones, and for Java Mobile Edition way back when. But there were good reasons why this never caught on and why I never bothered doing any serious development on them.

[idorosen]

I was responding to this in GP:

> reMarkable might do it for me if they had a more powerful CPU onboard and a way to get your code to run on it so the device can be tailored to solve more use-cases.

And there are a few app loaders/package managers that let you download new packages for it, but I agree that reMarkable isn't yet a product for your dad. Another serious product design flaw is that it does not support full disk encryption, or any encryption of documents for that matter. That means that anything uploaded to reMarkable cloud is accessible to reMarkable staff. That makes it basically unusable for work for me. It's a shame because the Screen Share (f.k.a. Live View) feature makes it a really great whiteboarding tool.

> "Feature phones" illustrated this. I wrote a few (very simple) apps for Symbian phones, and for Java Mobile Edition way back when. But there were good reasons why this never caught on and why I never bothered doing any serious development on them.

Back in the day, WhatsApp did spend the time to build a messenger app in J2ME (this was long before the Facebook acquisition), which made it possible for them to serve a very large worldwide population where smartphones hadn't penetrated. There weren't too many cheap, accessible smartphone options that had app stores or package managers available for under $500USD back then, but you could get a Motorola phone for cheap or even free from your carrier in most countries, and those supported J2ME apps. Their J2ME apps were a key (if not THE key) customer acquisition channel that got them a large underserved userbase from countries that Facebook hadn't penetrated deeply at that point. In my opinion, this non-overlapping set of users that were using WhatsApp daily was one of the reasons they were able to command a premium during acquisition. It was a hell of an increase to DAU/MAU.

In that era, per-message SMS fees, per-minute phone plans, long distance charges, and other extortionate fees were commonplace. Many WhatsApp users used it to avoid SMS/MMS charges, for which the J2ME UI was good enough to deliver tons of value, especially in low income areas.

[bborud]

How long did that time window last?

I started working for a telco that had a lot of business in emerging (Asian) markets in 2009. Three months after whatsapp was founded. What I do remember from that period was how quickly smart phone prices fell and how rapidly they came to dominate much of the picture in just a few years.

[idorosen]

Long enough for the network effect to take root in many countries. IIRC, it was at least 1-2 years in Israel and other countries, and today WhatsApp is ubiquitous there. J2ME apps showed up on a few smartphones too.

[bborud]

Sounds about right.

The reason I asked is that working in the telco industry gave me a slightly different perspective on time. Nothing happens fast in the telco industry and what would take perhaps a quarter in my previous jobs could easily stretch out for a couple of years (for a number of reasons largely having to do with organizations that do not respond well to changes).

[ThrowawayR2]

> "reMarkable might do it for me if they had a more powerful CPU onboard and a way to get your code to run on it so the device can be tailored to solve more use-cases."

The reMarkable is very intentionally an e-ink notebook and very little else. If you want a device that can be tailored to solve more use cases, one of the e-ink Android tablets would probably be a better choice.