Why am I writing about charts when there are already tons of amazing libraries that could be used in your app? Because most of the time they don’t really look or work as we expect, and I’ve seen many developers who are afraid of this and spend too much time trying to customise libraries, especially when they should be dynamic.
At Supercharge we build highly polished digital products, mainly for mobile screens. Recently we’ve created a new library called ShimmerLayout, which allows you to create shimmer effects on your layout in a memory efficient way-even when working with big layouts.
At Supercharge we specialise on working with enterprises that operate in industries which are being disrupted by digital. In such a fast-paced environment short release cycles are a crucial factor for success. For actual agility in development, Continuous Integration is really important. First of all, it makes you able to produce valuable applications in short cycles and it ensures that the software can be reliably released at any time. It may not be so easy to build your pipeline, but if you spend time setting it up, you can save a lot of time and focus on other more important things.
Craft is a kick-ass Budapest based conference about software craftsmanship which was held between April 26–29. Coders flock to the event as it has remarkable speakers year on year.
If it is too good to be true, it probably is. That flat we rented for a great price but had the loudest neighbours. That Kickstarter product we ordered that turned out to be a joke. That outfit we bought which only looked great online.
The saddest part of any UX practitioner’s career is when a product based on the designs becomes reality, but looks and behaves nothing like imagined. It happens surprisingly often in any kind of environment — I have observed this phenomenon in enterprises as well as startups. In my opinion, this problem normally stems from one of two possible root causes, or in the worst cases from a mixture of both.
Can anyone guarantee that a product will be successful?
Like everyone else who ever tried to write iOS applications, after some point we were also getting fed up with the so-called ‘Massive View Controller’ pattern in the iOS world.