The public transportation system in the city of our headquarters, Poznań, is a little behind on tech trends. While it keeps being modernized, it still leaves a lot to be desired.
With that in mind, two members of our Product Design team took it upon themselves to give our old public transport card a little makeover and make it more suited to the mobile era.
In this article, we’ll take you through the entire work process of our PD team. You can see for yourself how they approach problems, seek solutions, and execute their vision.
Over the past decade, I’ve worked with founders from across the world, helping them build their MVPs (Minimum Viable Products).
Regardless of whether you create an MVP for a startup, a medium-sized company or an enterprise-level business, there are certain anti-patterns you need to steer clear of.
To help you avert easy-to-spot and avoidable mistakes that have sunk countless other businesses, I’ve prepared a list of five of the most common one to look out for, together with ways to solve them.
The right way to start building your digital product is to rely on the knowledge and experience of those who develop software projects on a regular basis.
But how do you go about using that expertise to your advantage? We recommend going through discovery workshops.
Read on to learn:
- What are discovery workshops? What can you expect from the process?
- Why should you take part in discovery workshops? What are the benefits for you?
- What are the best practices for discovery workshops? What questions should you ask to get the most out of them?
Sometimes, there is overwhelming evidence in favor of one over the other thanks to its exceptional benefits. At other times, however, the choice is not so clear-cut.
React vs. Angular decidedly falls under the second category.
In this article, we won’t set out to pick a winner; our goal is to introduce the main benefits and uses of both React and Angular so that you can make an informed decision about which one is more suitable for your project.
Have you just signed a contract with a software development company, or are you considering signing one?
Outsourcing might seem like a big leap into the unknown. How do you ensure that the software house understands your requirements? When will they start coding? If you have your own in-house developers, how do you make sure their collaboration with the new colleagues is smooth and productive?
Client onboarding is the time to have all your questions answered.
When you manage a software development project, getting users to test your product at an early stage of the design process is the most cost- and time-effective way to ensure its success.
Testing your product saves you money by identifying usability issues early on, giving you the room to introduce fixes immediately and freeing up your developers’ precious time.
In this article, we will guide you through:
- the various testing techniques,
- the types of tools you can use,
- the steps you should take to make sure your session is successful.
As we scoured the web for problems we could help you solve, we came across a number of questions centered around UX design.
Lucky for you, we have a very capable Product Design team on hand at STX Next, with Wiktor Pawlik at the helm.
Wiktor is always happy to share his knowledge with anyone who asks, so we sat down with him for a little Q&A session. The result is this post.
Read on for a general introduction to UX design from Wiktor’s point of view.
A common misconception is that the bulk of the work on your digital product is done by launch day.
Nothing could be further from the truth. In fact, that’s when the real work begins.
Once you launch your product, you start getting tons of feedback, both positive and negative. It’s very exciting, since actual people are finally using this thing you’ve worked so hard to build, but it also means there’s a mountain of bugs to fix and changes to implement.
So how do you go about it? How do you choose the features to prioritize?
One of the most important things you have to consider when conceptualizing user interfaces is whether or not these interfaces are future-proof.
Your designs should be able to serve today’s user base as well as tomorrow’s.
How long do you want your project to be used for?
Express the answer to this question in the design.
Let’s say you have a working product, a growing number of customers, and a lot of ideas for new features.
Great! Now what?
It’s one thing to hit the ground running, and something else entirely to keep going. You need a plan for the future and you need it fast, otherwise your lucky streak will end before long.
So where do you start? What do you do first?
Two words: product analytics. Use product analytics tools to develop your software product the right way.