Where the design community meets.
Florian hasn't posted any stories yet.
I thought, except for the Mini every iPad already had pencil support?
Wow, I imagined they would get rid of that stupid "Air" branding, both in the iPad and the Macbook line. Guessed wrong.
But I don't get, who it is for: Is there really a big enough market between the iPad and the iPad Pro? I owned the older 10.5 iPad Pro and now own the 9.7 iPad - to me the difference was negligible. Sure, the hardware was slightly nicer, but the iPad's limiting factor is iOS and I have absolutely no complaints about how iOS performs on my iPad 9.7.
So if the hardware is the main differentiating factor ... Apple imagines there are people, who value a slim profile and a display that much, that they wouldn't buy an iPad, but also wouldn't buy an iPad Pro, because it was too expensive? And for those people they now finally have the perfect offering? I really cannot imagine this niche exists.
You can get a refund from Apple if an app is not to your liking.
Congrats to the launch. As someone, who declared Pocket bankruptcy once, started another account and now AGAIN has thousands of articles in there, your idea and implementation is genius. Btw: I find the self destruction of older articles a great idea. Or maybe a hard limit and when adding new stuff, older articles are pushed out of the queue?
Also I agree with the others, the onboarding is really well done. Though I still had problems and as you obviously care very much about the little things I thought I'd share my experience:
1) A page indicator tells me I can swipe on the content above (or sometimes below). It is no progress indicator. So I was a little confused when I instantly started swiping on the first screen, but nothing happened till I understood I need to tap the button.
2) I was confused after enabling ReadingQueue in the share sheet. Like ... what do I have to do now. Cancel? I read the instructions after "3.", but still wasn't able to grasp it. Obviously, for my brain to add a page in an onboarding process to a reading queue made so little sense, that I didn't understand the instruction. But maybe, that's only a power user's issue, who is too accustomed to the share sheet and knows how it works and what it generally does.
Sure thing ... but the fact, that prototypes take a lot of time and therefore iterating on them constantly is not a viable option in every situation, is not the fault of the tool (which I had the impression you were implying with "dead end" in the first place).
I don't quite understand the argument. Obviously, if you decide to change something, you have to apply these changes to the design file, the interaction prototype and the real product. But how is this the fault of the tools you use in each step?
Which problem of Flinto/Princliple does it solve (better)? I tried it once afair, but didn't stick. Also, I had the impression it lacks traction in the design community, which is never a good sign for new indie software.
Depends on how you define "deadend": In Flinto you are able to edit vector shapes and text layers, which I find mighty impressive and useful. Of course it does not offer all capabilities of Sketch, though.
I lol'd at "world's buggiest app".
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.