sandsmark

5 ms·

1.
by sandsmark 7y ago
Picture of one of the first prototypes (from 2015 or thereabouts) from remarkable.com/careers, guess the naming scheme: https://images.ctfassets.net/og7ujiyra5gx/15KAaMUsNXP8cQu3lP... :-)
2.
by sandsmark 7y ago
We generally have a policy of not communicating externally by default (way too many startups have failed because of loose lips and over-promising), but I'll answer with what's already known publicly. :-) > How many people are i
3.
by sandsmark 7y ago
Hmm, I thought we were at 2017.75, are you sure your device is up to date? We shipped the first software with an old dropbear, though it had backported patches for the known CVEs: http://cgit.openembedded.org/openembedded-co
4.
by sandsmark 7y ago
> [...] but having a mosh console on there would allow here to ditch her macbook. [..] Being able to code on it would also cause me to get one and ditch my iPad Pro. Not officially supported or endorsed in any way, shape or form, and I d
5.
by sandsmark 10y ago
please see https://news.ycombinator.com/item?id=13114550 for an explanation of the bad wording of "best" developers. I'm not trying to imply anything, but what I personally want and what we can do are two dif
6.
by sandsmark 10y ago
we're far too late in the development process to add to the features of the hardware, but backlight is one of the ideas for a next generation.
7.
by sandsmark 10y ago
> If your software is closed source, then I don't understand how anyone other than you effectively (or practically) would be able to solve or fix any security holes. I'm sorry if I wasn't clear. I meant that for pretty muc
8.
by sandsmark 10y ago
there are two epdc drivers in the kindle gpl releases. the source for the lab126 one is only available in the tarballs you linked (named mxc_epdc_fb_lab126.c). as for the waveforms, I'm talking about support for the REAGL (sic) wavefor
9.
by sandsmark 10y ago
Again, I can't discuss too many technical details. But yes, it's an i.MX6SL, I thought we mentioned that on the web page. And there are actually several drivers for the EPDC available. Two from freescale for the imx6 and imx7 (tho
10.
by sandsmark 10y ago
it won't take many weeks (or days) from we release the device until our solution is reverse engineered, no matter how much we lock it down. but until then we want to keep as much as possible secret. as for hackable device; we don'
11.
by sandsmark 10y ago
just to clear up any possible confusion; don't expect text recognition. it's probably the most requested feature, but it's a really, really hard problem. but please send me a message at martin.sandsmark@remarkable.no if anyon
12.
by sandsmark 10y ago
this is one of the reasons we need to get this in the hands of some kind of ambassadors that can test for themselves and give us some validation. imho the video doesn't do it much justice.
13.
by sandsmark 10y ago
no backlight, and as I explained above we can't promise anything other than what is written on the webpage already wrt. features.
14.
by sandsmark 10y ago
the reasons we decided against usb c are a) the device would have to be thicker, b) our industrial designer didn't like how it would look, and most importantly; c) I still have a hard time finding usb c cables. I always have to bring m
15.
by sandsmark 10y ago
we went to CES this year to see if there was any reason for us to go, but based on that we decided not to. it's insanely huge and hard to get any kind of exposure, even if people knew about us beforehand. but seeing is believing, espec
16.
by sandsmark 10y ago
sssh, it feels good to believe I'm saving the lives of children. :-(
17.
by sandsmark 10y ago
of course, one of the nice things with modern hardware is that we can deliver more features after shipping the device. edit; also, it is a device connected to the internet. not supporting updating the firmware would be extremely irresponsib
18.
by sandsmark 10y ago
> apart from the mass-production uncertainties these uncertainties is why we hired Dragon Innovation early on. they're very, very good at this and has a very good track record when it comes to hardware startups (e. g. pebble and mak
19.
by sandsmark 10y ago
academia is one of the biggest target groups, both in terms of marketing and development focus.
20.
by sandsmark 10y ago
"best developers" was a bit tongue in cheek, it was late and I didn't have time to come up with good wording (I'm not a good word person). but what I tried to convey; we know that even _if_ we can release a toolchain, we
21.
by sandsmark 10y ago
we can't release more technical details than what is on the webpage for now, we're still working on the performance. but to give you a rough idea on where we are on UI responsiveness and loading times, this is what we're usin
22.
by sandsmark 10y ago
no, we don't use Android, unlike pretty much everyone else. and the EPD is designed by e ink based on our requirements, e. g. the size and high DPI.
23.
by sandsmark 10y ago
our goal for solving it was to get it down to where it wasn't a detriment for the writing and sketching experience. one of the first things we did was gather data and read what research there was on what kind of latency was noticeable
24.
by sandsmark 10y ago
> I guess we (i.e techie internet folks, you included) have been served so many crowd funded promises that it's difficult to believe things that are too good to be true. well, I personally have basically stopped contributing to crow
25.
by sandsmark 10y ago
they've been dumping the price and trying to empty their warehouses, so I'm not sure if you can actually buy it anymore. at least not outside of japan.
26.
by sandsmark 10y ago
about epub, that's one format we're already committed to supporting. it's listed in the FAQ. we're very careful about not over-promising, that's partly why there aren't more features listed. edit; really beside
27.
by sandsmark 10y ago
except we waited until we had actual hardware prototypes before going public, from an ODM we've been working on for a while. and (some of our team) are on HN, which gives us much more street cred. and you can find pictures of us. one o
28.
by sandsmark 10y ago
the reason we're a bit scant on technical details so far is partly because we have spent most of our technical resources on actually making the device. but we'll try to get out a more technical blog post soon. another reason is th
29.
by sandsmark 10y ago
the latency is basically the only thing we've focused on for a while, it's a very focused device in terms of what we spend our resources on. the high latency is one of the reasons normal tablets suck for writing and sketching.
30.
by sandsmark 10y ago
this is actually the problem we have solved (for epaper). Compare https://www.youtube.com/watch?v=AKmfyThA9Sg to https://youtu.be/34I27KPZM6g?t=52

More ›