How we create websites, e-commerce and apps

Creating digital products, for SB\Design, means understanding that websites, e-commerce platforms and applications are different manifestations of the same logic: transforming a business model into a digital experience that is clear, efficient, desirable and capable of evolving. Although each of these areas has its own requirements, they all begin in the same place. Before thinking about interface, technology, platform or visual language, we need to understand deeply how the business works. Who are the users? What are they looking for? How does the company generate revenue? What are its products, services, channels, operations, internal systems, limitations and opportunities? Which tasks need to be simplified? Which processes can be automated? Which information needs to be found quickly? What behavior do we want to generate? For SB\Design, no interface should be designed before these questions are answered.

This way of thinking is directly connected to Sandro Bianco’s trajectory. He has been working with digital products for more than twenty years and has followed this universe since the early years of the commercial internet. Over this period, websites stopped being static institutional pages, e-commerce stopped being simply an online store, and applications began to occupy a central position in the relationship between people, companies and services. Technology, behavior, devices, connection speed, payment methods, search systems and user expectations have changed profoundly. What has remained is one fundamental question: a good digital product needs to understand people, information and business before it understands technology.

This is why the first task at SB\Design is usually to build or rebuild the information architecture. Once we understand the business model, we begin organizing what the product needs to contain, how information relates, which paths users need to follow, which levels of hierarchy exist and which actions need to be available at each moment. A website with only a few pages may appear simple, but it still needs to clearly explain who the company is, what it offers, why it matters and how someone can move forward. In larger systems, this architecture may involve hundreds or thousands of pages, products, categories, filters, profiles, permissions, flows and data relationships. The more complex the business, the more important it becomes to transform that complexity into an understandable structure.

Information architecture is therefore one of the foundations of UX. Before thinking about what a screen looks like, we need to understand the logic of the experience. We map journeys, entry points, exits, main paths, exceptions, decision points and different user profiles. A first-time visitor may need a very different experience from someone who uses the product every day. A B2B buyer may have completely different needs from a B2C consumer. An administrative team needs access to information and tools that the final audience will never see. Every digital product has layers, and the role of UX is to organize those layers so that each person can find what they need with as little friction as possible.

From this structure, we begin working on flows, wireframes, prototypes and interfaces. This is the moment when logic, behavior and visual language begin to meet. For SB\Design, UX and UI are not separate disciplines in the sense that one solves functionality and the other simply makes it look good. A visual decision can directly improve or damage the experience. Typography, contrast, scale, space, hierarchy, color, movement, component size and the position of an action influence comprehension, trust and conversion. Interface design needs to help users understand where they are, what they can do and what will happen next.

This relationship between experience and interface is especially important because digital products are used, not merely observed. An image can impress someone for a few seconds, but an interface needs to continue working after the hundredth use. A button needs to be where it makes sense. Search needs to return relevant answers. A form should ask only for what is actually necessary. A purchase needs to happen without unnecessary obstacles. A dashboard needs to transform a large amount of data into usable information. When design is truly good, much of this complexity disappears for the user.

In websites, the work can take on very different scales. We may build an institutional presence, a content platform, a portal, a landing page, a product-launch website, a highly visual digital experience or a corporate system with multiple levels of information. In every case, we seek to balance narrative, usability, identity and performance. A website needs to represent the brand, but it also needs to respond to business objectives. It needs to be visually relevant, but also fast, accessible, responsive, discoverable and easy to update.

The mobile experience is considered from the beginning. Today, much of the contact between people and brands happens through small screens, but that does not mean simply shrinking a desktop version. Context, gesture, orientation, connection, attention span and behavior all change. A menu, an image, a table or a form may require completely different solutions depending on the device. This is why we build responsive systems capable of preserving hierarchy, content and personality across different screen sizes.

When we talk about e-commerce, complexity increases because design begins to participate directly in both operation and revenue. An online store needs to present a brand, organize a catalogue, facilitate discovery, comparison and decision-making, generate trust, process purchases and continue functioning after the order has been placed. Search, filters, categories, product pages, variations, inventory, pricing, payment, shipping, cart, checkout, account, orders, returns and customer support form a single experience. If one of these parts does not work properly, the efficiency of the entire system can be compromised.

SB\Design works with B2C, B2B and B2B2C e-commerce because we understand that each model demands a different logic. In B2C, we are usually dealing with a more direct journey between brand and end consumer, where desire, clarity, trust and simplicity of purchase are extremely important. In B2B, we may need to manage specific price lists, commercial conditions, different access levels, recurring orders, large quantities, internal approvals, multiple buyers, logistics integrations and rules that make the experience much more complex. In B2B2C models, we need to understand simultaneously the relationships between industry, distributors, partners, channels and the end consumer. There is no universal architecture for electronic commerce. The system needs to emerge from the business model.

To build these operations, we can work with existing platforms when they provide the most appropriate solution or develop custom architectures when the client’s needs justify a proprietary structure. Shopify, VTEX, Adobe Commerce, WooCommerce and other platforms can efficiently solve projects at different scales, but we do not begin with the platform to define the solution. First, we understand the business. Then we identify which infrastructure can support it with the greatest efficiency, flexibility, security and capacity to evolve. In some projects, this may mean integrating existing technologies; in others, developing systems and functionalities specifically for that business.

This independence is important because technology should serve strategy rather than force the business to adapt to the limitations of a tool. At the same time, building everything from scratch is not automatically better. A mature market solution can reduce cost, time and risk. The decision needs to consider scale, operation, internal team, budget, integrations, security, maintenance and future growth. For SB\Design, choosing technology is also a design decision because it directly affects what can be built and sustained.

Applications follow the same logic. We can work on native, hybrid, cross-platform, mobile, web or desktop products depending on the needs of the service and the client’s technological ecosystem. An app can serve consumers, employees, sales teams, specialized professionals or internal operations. It may function as a bank, service platform, productivity tool, marketplace, loyalty program or any other experience that requires a recurring relationship with the user. Once again, the work does not begin by choosing technology. It begins by understanding which problem needs to be solved and why an application is the best way to solve it.

In products that are used repeatedly, small details become especially important. Loading time, navigation logic, system states, error messages, notifications, authentication, security, gestures, accessibility and continuity across devices are all part of the experience. An application cannot function only in its ideal flow. We need to think about what happens when a connection fails, when information is incomplete, when the user makes a mistake, when they return after months away or when they need to recover a previous action. Digital design is also about designing for exceptions.

Beyond the interfaces seen by the public, there is an entire layer of internal systems. Administrative panels, dashboards, CMS, back office, product management, orders, customers, content, permissions, reports and different operational tools are often fundamental to the success of the product. An excellent consumer experience may be impossible if the internal team needs to perform dozens of manual tasks to keep it running. This is why we also seek to understand who manages the product and how to make its operation simpler, more organized and more efficient.

Dashboards deserve particular attention because it is not enough to place charts on a screen. It is necessary to understand which decisions need to be made from that data. A good dashboard organizes priorities, reduces noise and helps people quickly understand what changed, what requires attention and which action may be necessary. Data visualization, hierarchy and information design are essential for turning numbers into understanding.

This perspective also allows SB\Design to act in a strategic consulting role before a new product is even started. Many companies have technological structures built over years, with different suppliers, ERPs, CRMs, platforms, databases and systems that do not always communicate properly. Before adding another layer, it may be necessary to understand what already exists. Analyzing technological architecture, data flows, ERP, CRM, APIs, integrations, marketing tools and operations may reveal that part of the problem is not in the interface, but in the structure behind it.

In these situations, design work moves closer to product strategy. We need to understand which systems should remain, which need to be integrated, which processes can be simplified and where redundancy exists. The interface the user sees is only the surface of a much larger structure. The more integrated that structure is, the greater the ability to offer a consistent experience.

Integration is therefore one of the key words in our digital work. A website or e-commerce platform may need to connect with ERP, CRM, payment gateways, carriers, tax systems, customer-service platforms, marketing automation tools, marketplaces, social networks, recommendation systems, analytics and dozens of other services. An application may need to access authentication, geolocation, payments, notifications, internal data and external services. The quality of these integrations directly affects the quality of the product.

Artificial intelligence becomes part of this ecosystem across multiple layers. For SB\Design, AI should not appear simply as a feature added because it is currently in focus. We seek to identify where it can genuinely improve the experience or the operation. It can support search, recommendation, customer service, personalization, content production and organization, data analysis, automation, team support or different forms of interaction.

In commerce, for example, intelligent search can understand intent and context instead of depending only on exact keyword matches. Recommendation systems can help people navigate extensive catalogues. Conversational interfaces can transform the way products are discovered. WhatsApp-integrated support can answer questions, retrieve information, assist with a purchase or escalate more complex situations to people. The important thing is to design these experiences so that technology expands the usefulness of the product without making the relationship artificial or confusing.

AI is also beginning to profoundly change how digital products are discovered. For many years, much of the discovery strategy was concentrated around traditional search engines and SEO. That work remains fundamental, but it now needs to coexist with a new layer of discovery through artificial intelligence systems, assistants and answer engines. This is why we think of SEO and GEO as parts of a broader architecture of content, information and technology. A website or e-commerce platform needs to be understandable to people, search engines and systems that interpret and reorganize information.

This requires structure. Clear content, semantic architecture, organized data and consistent information about products, categories, brands, authors, services and companies increase a platform’s ability to be found and correctly interpreted. Producing hundreds of pages without logic simply to generate traffic is not enough. The better the quality and organization of information, the more useful it tends to become across different forms of discovery.

Artificial intelligence is also integrated into SB\Design’s own creative process. Research, analysis, architecture, prototyping, content, code, testing and visual exploration can be accelerated by different tools, allowing more time to be dedicated to decisions that genuinely require judgment. But, just as in art direction, technology does not replace vision. Generating faster does not necessarily mean generating better. The role of design continues to be selecting, organizing, testing and deciding.

Once architecture, UX and UI are defined, we move into the development layer. HTML, CSS, JavaScript, frameworks, components, APIs, databases, CMS and different technologies begin transforming the designed system into a real product. For SB\Design, there is a very close relationship between design and code. An interface is only truly resolved when it can be implemented with quality. Motion, responsiveness, microinteractions, transitions, accessibility and performance all need to survive the journey from prototype to final product.

This is why design systems play an important role in larger projects. Instead of designing every screen as an isolated solution, we build components, patterns, rules and behaviors that can be reused. Buttons, fields, cards, menus, modals, tables, alerts, typography, colors, spacing and different elements begin to form an operational language. This system increases consistency, accelerates development and allows the product to grow without losing identity.

Testing is also part of the process. A flow that appears perfectly logical to the person who designed it may create doubts for someone who has never seen the product before. Prototypes, usability testing, analytics, behavior maps and real data help identify problems and opportunities. Digital products have one important advantage: they can evolve. Unlike a printed object, an interface can be modified after launch. But that possibility should not justify launching carelessly. It should make continuous learning possible.

This is why we consider launch the beginning of a new stage rather than necessarily the end of the work. Once real users enter the system, we can observe behavior, abandonment, conversion, paths, search and difficulties. This data reveals information that no prototype can fully anticipate. The product can then evolve based on evidence, preserving what works and correcting what does not.

Security, privacy, performance and accessibility are also part of a good digital experience, even when they are not visually visible. A user needs to trust that their data is being handled correctly. A page needs to load quickly. A person with different abilities needs to be able to navigate. A system needs to remain available and work across different devices and conditions. High-quality design cannot treat these factors as the exclusive responsibility of technology.

There is also one question we consider central: digital design needs to serve business objectives without treating the user as an obstacle to be manipulated. Conversion matters, but trust matters as well. An interface can try to force a purchase through confusing patterns, or it can build such a clear experience that people choose to continue. For SB\Design, the second option creates far more value over time.

This is exactly where UX and UI can become decisive factors in the success of a digital product. Two services can offer virtually the same functionality and create completely different perceptions depending on the experience. A simple process, efficient search, clear hierarchy or an interface that communicates trust can determine which product someone chooses to use. Design is not simply an aesthetic layer over technology. It directly affects adoption, comprehension, efficiency and perceived value.

On a website, this can determine whether someone quickly understands the company or leaves the page. In e-commerce, it can mean the difference between discovering a product and abandoning a purchase. In a banking application, it can mean completing an important operation with confidence or feeling uncertain at every step. The more complex the service, the more important it becomes to transform that complexity into an apparently simple experience.

This may be one of the best definitions of what SB\Design does in the digital world: **transform complex systems into clear, coherent and usable experiences**. Behind a simple button there may be databases, commercial rules, authentication, integrations, logistics and multiple systems. The user does not need to understand all of that. They simply need to be able to do what they came to do with clarity and confidence.

At SB\Design, directed by Sandro Bianco, websites, e-commerce and applications are not treated as isolated disciplines. They are digital products built through the integration of strategy, business, design, content, data and technology. We may develop an institutional presence, a large-scale e-commerce operation or a complex application, but the principle remains the same: first understand the structure that needs to exist, and only then decide how it will be seen and used.

This is how SB\Design creates digital products: by beginning with a deep understanding of the business model, analyzing people, market, content, technology and existing data, building a new information architecture, designing journeys and experiences, developing UX and UI, structuring design systems, dashboards and administrative panels, defining integrations, choosing or developing the most appropriate technological infrastructure, incorporating artificial intelligence where it genuinely creates value and preparing content and architecture for new forms of search and discovery.

Because a good digital product is not one that simply looks contemporary when it is launched. It is one that can transform complexity into clarity, technology into utility and interaction into value. Whether it is a website, a B2C, B2B or B2B2C e-commerce platform, or an application for a highly complex service, the role of design remains the same: understand the problem deeply, build the right structure and create an experience so well resolved that the technology practically disappears and what remains for the user is simply the feeling that everything works exactly as it should.