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.
The internet is composed of input fields.
Whether it’s signing up for a social media platform, conducting ecommerce credit card transactions, or applying for a financial product within an online banking system, filing a form is the first and/or final step of nearly every action you perform on the internet.
Working in a Product Design team brings many possibilities to design (and redesign) application forms.
In this article, I’ll present some general guidelines and best practices for application form design.
SuttaCentral approached STX Next for support with a website collecting early Buddhist texts and their translations. They wanted their product to be easy to access, simple to use, and available to all.
To that end, we helped the client build a Progressive Web App to provide them with offline functionality and a mobile component.
As a Product Owner, working with SuttaCentral has been an absolute highlight of my professional career. This is a story of the deciding factors that made our cooperation a glowing success.
Let’s say you’re dealing with a software development project. You’re trying to develop an app or any other software product. Here’s how the story usually goes:
Your project is approved. Check.
You’ve assembled your development team. Check.
You’ve allocated your Product Design budget… Have you?
Being a CTO (Chief Technology Officer) takes insight and vision, in technology and business alike. Part manager, part software engineer and part entrepreneur, the CTO can benefit from a wide range of sources to brush up both on the newest developments in tech and to shape the software philosophy of the company.
We know it might be challenging to find useful reading material, or a strong starting point for newly-appointed CTOs - which is why we’ve created this list of must-read books for CTOs. Let’s begin!
While working in various IT projects I realized that regardless of all these ‘lean’ product development movements, many companies still encounter major issues in terms of product validation. In other words - it is hard for people to understand if the product they develop is what the market desires.
To help you with your validation efforts, I’d like to give you an inside look into the day-by-day product validation process for a live product that we have worked out with one of our clients. Let’s start by answering the fundamental question: What is product validation?
They say that a job well begun is half done. Software development projects are no different.
Each software development project starts with a project kickoff. My work at STX Next involves quite a few of those, so today I’d like to share what you can do to ensure your kickoff is as productive as possible. I've also included a sample kickoff agenda and the checklist I use to measure kickoff success.