Miért fontos, hogy a fejlesztési projekt megfelelő specifikációval legyen ellátva? Körülbelül olyan kérdés ez, minthogy: kell-e egy nyolcemeletes lakóparkhoz részletes építkezési terv? Fontos, hogy lehetőleg minden részletre kiterjedjen? Igen, kell! Igen, fontos!
Hogyan tud egy könyvelés, statisztika, számvitel tananyagokkal foglalkozó oktatási szervezet hatékonyan megjelenni mobil felületen, milyen kapcsolódó rendszerekre van szükség? Ezzel a céllal készült el a Könyvelő kAPPtár alkalmazás, amelyről ez a blog bejegyzés szól.
Over the course of the past few years, we have designed and developed hundreds of mobile apps. We made some of these applications for large companies, some for startups and we have made a couple as our own products. We always focused on some of the core areas where we felt we have great expertise. Two of these areas are messaging and communication. We always felt that this should be one of the most important reasons someone would use their smartphone to download software. Later on, this was validated with a large amount of data, both from analytics and feedback.
A couple of weeks ago we finally put our hands on some Apple Watch. The guys in the office were eager to test it, although we knew that in the current version there are way too many limitations. The results were mixed and instead of making one post, we have decided to give a chance for some of our developers to tell their experience with their own words.
Last week an awesome event took place in Dallas, TX, where we validated an interesting case using an iBeacon supported mobile app at a conference. This is the second time we used the Bluetooth enabled device with our mobile solution and the result is outstanding. We got higher user engagement and more efficient communication, since 90% of the visitors used the app all event along.
I was looking for a drawing tablet for a while, as everyone who designs, whether it is for web or for print, needs one sooner or later. Choosing the right device mainly depends on how much and for what tasks the designer intends to use it.
For about six years ago I bought a Wacom tablet and it was perfect for making smaller illustrations. Later I got a scanner and switch to the process of first drawing by hand, then scanning the sketch, and finally creating the digital illustration. For the few cases that required a drawing tablet, the small Wacom tablet was enough.
During their careers, every developer must face the question several times that whether they should use an existing solution in their project, or write a new one from scratch. Generally speaking, an own development is better because you will know its inner workings in details and you don’t have to learn how other developers’ code can be used. However, sometimes it’s more economical to use a well-coded open source library, so you will have more time (and energy) to work on other components of the project.
When we started our development firm a few years ago, not every new information technology company was called as a startup. The concept of a lean startup was also easier to apply: just make sure that costs are kept to the minimum and time is managed as efficiently as possible.
Once you take this mentality and your thinking shifts towards creating a company and building a product this way, you will see how immensely productive this approach is. Of course, a collaborating team is also crucial to succeed: there is no place for individual privileges, nor for workplace drama, as it can make product development substantially slower, or even end it entirely.