jacobkrajewski

[jacobkrajewski]

Whereisapp.com

An ai powered app that helps you find concentrations of anything around the world. Designed and front end development by me.

[jacobkrajewski]

BlackCalc.com - a financial tool for non-financial types. Designed and developed by me.

[jacobkrajewski]

skylines.ai - an ai assisted project management tool that allows users to skip the hardest part of writing requirements - writing. Designed / developed by me.

[jacobkrajewski]

Work in progress. Frontend for Backend. API and interaction design. This UI isn't for consumer eyes, rather it's to use while developing complex interactions between different objects in the UI. It's extremely helpful in separating the function of an app from the look and feel, allowing for maximum coverage of the backend infrastructure before skinning it with a friendly UX.

[jacobkrajewski]

Biz stuff. Sometimes we have big projects and we need to figure out 1. Why we're doing them, 2. How do we know if we're succeeding. A simple business and CX objective and metrics analysis lets you understand what the goals of your design should achieve, and how to measure if you reach your goals. You should usually work with your product owner or product manager to put together something like this. Why do one of these? It helps motivate gatekeepers to understand why supporting your work is important.

[jacobkrajewski]

Personal GPS radio-communication device. Full design, hardware, UI, circuitry. This is a personal project. Things were going well until COVID hit and we lost our electrical engineer, Sam 🕊️

[jacobkrajewski]

From my talk, Design for users, not for requirements.

[jacobkrajewski]

Original pixel art for a memecoin landing page. The idea was you wallet sign-in, place a crypto bet, and play. Winner takes all.

[jacobkrajewski]

How to reverse aging. Original content

[jacobkrajewski]

Feature images for Skylines.pro, AI task management app.

[jacobkrajewski]

Complete market ready proposal with UI + interaction from start to finish. Based on extensive foundational research, competitive analysis, with the help of one dedicated UX Researcher.

[jacobkrajewski]

Simple dark mode variant created with exclusion and difference layer overlays.

[jacobkrajewski]

Here is a screenshot of an actual interface created in React.The vision was to take a complex, dated system for manual input and create a system that would work for 1 or 10,000 entries. I was responsible for the design of the product and focused on clear calls to action, one page functionality, focused around the user input.

Everything boils down to information hierarchy and priority of importance. This was also one of the only places where our official purple accent was used, but i think it fits nicely against the dark theme!

[jacobkrajewski]

Collaboration in the remote age

There are tools like Invision Freehand that are useful for virtual meeting collaboration, but all too often, a call with product is looking at tables and spreadsheets, or JIRA tickets for requirements. There are many challenges to defining a product while remote, but one thing that tends to work well is to do live product definition sessions.

Shown here is a document that is the result of several live sessions. Starting from very broad with several ideas to getting more and more refined as time goes on. It helps define interactions, get stakeholder buy in early on, and allows for the posing of relevant questions and suggestions from all parties, including engineers.

The great part is, this can be used as a graphical reference and even as an engineering specification!

[jacobkrajewski]

Quick specifications

Sometimes you're working with a team that is aware of all the features and functionality, and is just waiting for a visual specification of a feature. In those cases products like Zeplin or automated specs can be extremely useful.

Because this was a rather standard feature, I quickly created a hand spun visual spec after internal reviews that would allow engineers to rapidly implement the component without requiring the need for costly prototyping and user research.

In this case, the rule was to rapidly provide exactly what was needed to implement the task and no more.

[jacobkrajewski]

Configuration problem

Complex configurations

"The program" had been struggling for years to standardize and simplify a means for configuring a wide array of their digital service offerings. The complexity of each service created the need for several complex and unique properties, such as on-the-fly calculations, interdependencies and many configurations in a just in time fashion. They had unsuccessfully tried long forms, smart wizards, but nothing seemed to simplify the experience for users.

The challenge was to create a system that could be loaded with any service and allow it to be configured and saved without the need for extensive customization of the UI.

I designed a language involving reproducible, scalable, small forms and states based on the requirements of each service.

As a result, I created a flexible, robust configuration flow that was able to handle every service by simply showing a different set of reusable components. Long term users were extremely pleased to be able to finally see their services in a largely simplified format. "Yes, yes, yes!" one of them said, when it was first presented to them.

[jacobkrajewski]

Responsive component dynamic states.

The size of a viewing area determines what can and should be shown for any given component. The way things are laid out should feel natural for the user at any screen area.

In this particular case, I designed a charting element that contained all the required user actions, but utilized basic information hierarchy principles to adjust the layout to be both aesthetically pleasing and functional.