Privacy is UX by Alex Schmidt September 22, 2015
Government snooping. Identity theft. Sale of personal data. Privacy is out there in a big way. But it’s not in here, meaning on most product development teams.
A professional perspective on JS by Cory House:
It’s hot to talk about how improving API User Experience can make end users happy. UX is important to consider with APIs and with any kind of development. But sometimes we forget about the middle men and women who are often the true intended audience and customers. When developing an application programming interface, or API, it is essential to keep developer experience or DX as a priority in everything we do.
Developers are People Too! Building a DX based API Strategy
Imagine you’re in a game with one objective: a bestselling product or service. The rules? No marketing budget, no PR stunts, and it must be sustainably successful. No short-term fads. This is not a game of chance. It is a game of skill and strategy. And it begins with a single question: given competing products of equal pricing, promotion, and perceived quality, why does one outsell the others? The answer doesn’t live in the sustainably successful products or services. The answer lives in those who use them. Our goal is to craft a strategy for creating successful users. And that strategy is full of surprising, counter-intuitive, and astonishingly simple techniques that don’t depend on a massive marketing or development budget. Techniques typically overlooked by even the most well-funded, well-staffed product teams. Every role is a key player in this game. Product development, engineering, marketing, user experience, support—everyone on the team. Even if that team is a start-up of one. Armed with a surprisingly overlooked science and a unique POV, we can can reduce the role of luck. We can build sustainably successful products and services that rely not on unethical persuasive marketing tricks but on helping our users have deeper, richer experiences. Not just in the moments while they’re using our product but, more importantly, in the moments when they aren’t.
I tried out Apple WatchKit to bring Sorting Thoughts on an Apple Watch and I’m really impressed how simple it is. It takes me only a couple of hours to show the most important task thoughts of a Sorting Thoughts collection in a glance and special app view:
The layout of an app is very simple and focused on the important information. For the glance view Apple advises a couple of default layouts and I think it is a good idea to use one of this layouts because there are well thought and fit for the watch concept. What is interesting is to see that the upper glance layout group always have a right margin – see also the Xcode 6.2 screenshots below. I think it is not understated to see over 10k apps if the Apple Watch will be sold in April 2015.
Interessanter Artikel über agilere Use Case Beschreibung: “Use Case 2.0: Agile Projektplanung mit Use Case Slices” von Ursula Meseberg
Use Case 2.0
In Use Case 2.0 wird für jeden Use Case zunächst jeweils der “Basic Flow” festgehalten. Er entspricht dem herkömmlichen Hauptszenario, ist also eine Folge von Schritten, die auf “geradem” Weg zum erfolgreichen Abschluss des Use Case führt. Zu einigen Schritten und Schrittfolgen des Basic Flow gibt es im Regelfall Alternativen, das heißt bedingungsabhängige Abweichungen vom “geraden” Weg. Diese Umwege werden als “Alternative Flows” bezeichnet.
Use Case 2.0 und Scrum
Wie greifen das Use Case Slicing und Scrum ineinander? Ein aus Use Case Stories und Testfällen gebildetes Use Case Slice wird als Backlog-Item in das Product Backlog der agilen Entwicklung eingestellt. Bevor der Scrum-Ablauf beginnen kann, muss das Product Backlog zu einem gewissen Grad gefüllt sein. Es sind also Use Cases identifiziert und daraus Use Case Slices abgeleitet. Use Case 2.0 setzt nicht voraus, dass zu Beginn eines Projekts alle Use Cases vollständig definiert werden. Um erste Backlog-Items zu gewinnen, genügt es, einige zentrale Use Cases zu identifizieren. Das erfordert den folgenden Vorlauf:
mehr auf “Use Case 2.0: Agile Projektplanung mit Use Case Slices” von Ursula Meseberg
Great summary about the current smartphone market:
The state of smartphones in 2014: Ars Technica’s Ultimate Guide
All the phones you need to know about, and everything you need to know about them.
Tl;dr: Just tell me what to buy!
Before we get started, here is the version of this article for people who just want purchasing recommendations.
If you like iOS, get an iPhone 6.
If you like Android, get a 2014 Moto X. If you like Android but hate the Moto X’s camera and battery life, get a Samsung Galaxy S5. If you like Android and want a big phone, get a Samsung Galaxy Note 4.
If you like Android or don’t have a preference and want a solid, inexpensive unlocked phone, get a Moto G. We’d favor the larger 2014 model because it’s newer and more likely to be supported for longer, but the smaller 2013 version is cheaper and essentially identical.
If you like Windows Phone and you need something today, get an HTC One M8 for Windows. If you can possibly wait, sit on your hands until a new Lumia flagship comes out.
— Hendrik Ebel (@sortedThoughts) 10. Januar 2015
Woohoo! Sorting Thoughts for iOS is now available in the App Store :-)
It feels great to have this milestone behind me. And I look forward to many feedback and to the next release of the desktop version. With Sorting Thoughts for Mac and PC 2.0 the sync cycle will be closed and Sorting Thoughts will be a great tool on desktop and iOS devices with a secure and private sync service.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.