Good LTE band support is something you might take for granted if you are used to using flagship Android or iOS devices.
At the moment I'm wishing I'd bought the dev kit, I'd be happy with it slapped into a 3D printed case as my phone.
I know that, for instance, Verizon has certified a variety of modules to work on it's network, and a phone (or laptop) that uses that module need not be certified by Verizon to work on their network, for instance. Every Verizon compatible laptop doesn't get certified, it just tends to use one of a handful of Sierra Wireless LTE modems which are. Similarly, my understanding (and hope) is that Purism is going to support dropping in various LTE modems so that people can get support for the networks they need.
Last update we had was that the boards would ship August 2018. I'm wondering if they're still aiming to ship them this month.
In this case, if we consider that it is still the 1st half of August, so a lot of companies are closed or on reduced activity with reduced personnel; that after the schematic is finished, the PCB has to be drawn, the PCB has to be built (that's quick), the PCB has to be populated with chips (it can be quick... if everything is in order, otherwise add a small delay); that the first boards have to undergo some minimal amount of testing before the full run is produced and shipped to customers to ensure that at least its major parts are working kind of OK ; that there was no prototype board before this run (IIRC) ; that if this testing does not go well, major issues will have to be found and corrected before shipping, possibly implying ditching the existing PCBs, correcting the schematics, rerouting the corresponding PCB parts, and starting a new batch of boards... I bet there is very little hope they keep their promise.
And globally, considering that their reports are always 95% about software and 5% about hardware which seems to be more and more outsourced, we can say it is one more time the case of a bunch of software developers and software designers underestimating the amount of work (people, time, and the cost of iterations in hardware compared to software) and the amount of experience needed to produce the hardware side. As it has already happened many, many times in similar projects, with similar goals, with similar people involved.
I expect them to ship some 'development boards' eventually, but my hopes for an actual phone are seriously diminished.
I don't say this to put them down, I hope they succeed, but I am 100% skeptical of any crowd funded hardware device.
Is there a reason the programmers couldn't just implement the design as given? They added a bunch of useless borders and gradients, and removed all the labels. This looks exactly like the Parable of the Concept Car: https://daringfireball.net/linked/2008/08/12/concept-cars
EDIT: designs almost always look nicer than the first pass at implementing them, as designers can put pixels wherever they want to make things look pretty, while developers are constrained by the technical restrictions of the frameworks being used.
Pretty sure they just used the existing GTK theme, the didn't add anything. If you're worried about how it looks you can install you're own theme and have it apply in every app.
Display: an LCD display that is 5.7″ at 720×1440 pixels
They mention, that such resolution is caused by heat dissipation issues (since they by design don't use integrated SoC). May be size is also caused by separate chips?
Regarding the browser, it would be nice to have something based on Servo, rather than Epiphany. Are there good mobile browsers that use Servo embedding and can work on normal Linux?
Why is Servo team not focused on general Web compatibility? That sounds like a major must do before anything else. Don't Mozilla plan to replace Gecko in Firefox with WebRender from Servo anyway, so how can they achieve it without good Web compatibility?
No they don't, they're replacing pieces of firefox with pieces developed from servo but there are no plans to ever replace it wholesale.
That's probably why they're focusing on the VR/AR stuff, to put that into firefox once it's ready since it'll be a new set of features entirely and not have any legacy version they need to maintain bug compatibility with too.
> No they don't
It's in progress and due for Firefox 64 later this year (if projections below are current):
It looked like they're writing their apps in gtk, using the CPU for any animation and rendering - as opposed to some OpenGL solution that would do this much more efficiently on the GPU..
For reference, Rendering a simple, animated bar chart using QtQuick canvas, at 720p@60fps maxed out our iMX6 cpus - while doing the same on the GPU took like 30% cpu and the result was much more smooth.
c.f. Canonical running Unity on desktop and phone.
Would love to see a comparison between gtk4 widgets vs. qtquickcontrols 2.0.
From the looks of it, gtk 4 seems to have come a long way since I last tried:
And more importantly, there seem to be fewer breaking changes for applications to leverage these improvements:
The v1 phone would be %80 open, the v2 could be %90 open and so on.
Isn't it very late to start researching and thinking about those things? My general instinct is that security needs to be designed and built in from the start - what about the components they've already developed, and how they integrate with each other? - including as part of the development process and even as part of the culture.
Thats how I like it :-)