现代天线设计

重点 (Top highlight)

Designing and developing for the web has always been a moving target. Browsers and technologies have been perpetually changing requiring constant evolution of skill set but there are still some overarching truths that remain. In this article I have outlined a handful of what I think are some of the most commonly overlooked challenges when designing for the modern web that we should consider more deeply as we continue to define the future of web design practice.

d esigning和网络发展一直是一个移动的目标。 浏览器和技术一直在不断变化,需要不断发展的技能组合,但仍然存在一些重要的事实。 在本文中,我概述了一些我认为是现代网页设计中最常被忽略的挑战,在继续定义网页设计实践的未来时,我们应该更深入地考虑这些挑战。

网络天生就是摇摇欲坠的 (The web is inherently rickety)

HTML and CSS do things that they were never intended to do back when they were originally invented. My guess is Tim Berners-Lee did not anticipate the hot mess that we find ourselves in today. Rendering code in a browser has always been a tricky thing. Every browser version and update handle things a little differently and always have. How browsers on mobile devices handle the rendering of HTML, CSS and Javascript compounds the fragility of how we not only build web experiences but how we maintain them as well. We have to remember that it has been less than a decade since more users accessed the internet from mobile devices than desktop.

HTML和CSS的作用是它们最初被发明时从未打算做的。 我的猜测是蒂姆·伯纳斯·李 ( Tim Berners-Lee)没想到我们今天会发现自己很热。 在浏览器中呈现代码始终是一件棘手的事情。 每个浏览器版本和更新对事物的处理都有所不同,并且总是如此。 移动设备上的浏览器如何处理HTML,CSS和Javascript的呈现,增加了我们不仅构建Web体验而且还维护它们的方式的脆弱性。 我们必须记住,距移动设备访问互联网的用户超过台式机的用户不到十年。

From a process perspective, clients and designers have never fully embraced the inherently brittle nature of the web as a communication channel. It is human nature to prioritize certainty and our technical processes reflect this. If you think about all of the mediums modern humans create in, only the web starts from a place of uncertainty, incompleteness and brokenness. In essence, the web as a medium is a fluid software that is constantly changing and being updated. The concept that bugs, fixes, tweaks and iteration and refinement are such a large constraint of the web is still a hard thing for some to embrace. To fully succeed within the rickety ecosystem of the web, we have to establish creative mindsets that allow uncertainty and brokenness to flourish with the understanding that finding perfection must be an open ended pursuit.

从过程的角度来看,客户和设计师从未完全接受网络固有的脆弱性作为通信渠道。 优先考虑确定性是人类的天性,我们的技术流程反映了这一点。 如果您考虑一下现代人类创造的所有媒介,那么只有网络从不确定性,残缺性和破碎性开始。 本质上,网络作为一种媒介是不断变化和更新的流动软件。 错误,修复,调整以及迭代和完善是网络的巨大约束这一概念对于某些人来说仍然很难接受。 为了在摇摇欲坠的网络生态系统中完全成功,我们必须建立创造性的思维方式,让不确定性和断断续续蓬勃发展,同时要认识到寻找完美必须是一个开放的追求。

原型不是完整的网站 (A prototype is not a finished site)

In recent years there has been a proliferation of different prototyping solutions. Invision, Figma, Principle, Adobe XD and many others. Part of the reason prototyping has become so important is it allows for visual and UX decisions to be made rapidly without any knowledge of the code that is required to build a site or web product. On the one hand this is great because strategic and visual problem solving is decoupled from the actual build allowing for non-developers to explore what is possible.

近年来,出现了各种原型解决方案。 Invision , Figma , Principle , Adobe XD等。 原型变得如此重要的部分原因是,它可以快速做出视觉和UX决策,而无需了解构建站点或Web产品所需的代码。 一方面,这非常好,因为战略和视觉问题的解决方案与实际构建脱钩,从而允许非开发人员探索可能的解决方案。

The down-side is that there remains a separation between what a prototype can accomplish and what a real platform or product must accomplish. As long as prototypes are separated from the code and engineering that actually form its creation they will never ever be the same. There will always be a gap between the idea and the reality.

不利的一面是,原型可以完成的工作与实际平台或产品必须完成的工作之间仍然存在分离。 只要原型与实际形成其原型的代码和工程相分离,它们就永远不会相同。 思想与现实之间总会有鸿沟。

One metaphor I use often is the idea of the avatar of a person. For example, you could have a wide range of interpretations for visualizing a human being. You could do a pencil drawing, a painting, a photograph, a 3d model or even a robot of a person. None of these will ever replace the actual person. In the same way, it does not matter how high fidelity a prototype is, it will never be a replacement for the product itself.

我经常使用的一个隐喻是一个人的化身的想法。 例如,您可以使用多种解释来可视化人类。 您可以绘制铅笔素描,绘画,照片,3D模型,甚至是人的机器人。 这些都不会取代实际的人。 同样,原型的保真度也无关紧要,它永远不会替代产品本身。

Developing prototypes also can give teams a false sense of accelerated progress. Inherent in the term prototype is the idea of something experimental, initial or a model. On the web, there is an easy confusion between demonstrating an idea via a prototype that is created quickly and a final solution that has been properly tested and QAed.

开发原型也会给团队带来错误的加速进展感。 原型一词的本质是实验性,初始性或模型性的概念。 在网络上,通过快速创建的原型演示想法与经过正确测试和质量检查的最终解决方案之间容易混淆。

This misrepresentation of time is also compounded by the imperfect nature of prototypes themselves. The more energy and effort put into a high fidelity prototype to add the UX bells and whistles needed to sell an idea, requires an exponentially longer amount of time to reverse engineer into meaningful and usable components after the prototype has been sold in. As a result, there is an inherent redundancy; you spend time making a prototype of something only to make it again as a real thing.

原型本身不完善的性质也加剧了这种时间上的错误表述。 高保真度原型投入了更多精力和精力,以增加销售创意所需的用户体验,这需要花费成倍的时间,以在原型售出后将工程师反向转换为有意义的可用组件。 ,存在固有的冗余; 您花时间制作某些东西的原型,然后又将其重新制成真实的东西。

The magical solution that no software has fully cracked is making the visualization and implementation of web experiences one and the same. Software solutions like Webflow and UXPin are getting closer by merging visual tools that can produce semantically correct markup and I think this merging of visual and code is where the solution will be found. But the ultimate answer to this dilemma is not entirely in the software.

没有软件可以完全破解的神奇解决方案是使Web体验的可视化和实现完全相同。 通过合并可以产生语义上正确的标记的可视化工具, Webflow和UXPin等软件解决方案越来越近了,我认为可视化和代码的合并就是找到解决方案的地方。 但是,解决这一难题的最终答案并不完全在软件中。

The primary leap that needs to happen is designers must have an intuitive willingness to connect the visual logic of what they are trying to achieve with an understanding of how their visual decisions get expressed in the constraints of code. The fact that the digital industry has not made this leap is more due to convenience and the desire to maintain delineated roles and process than anything else. Right now these two worlds — the visualization of web experiences and the implementation of them in code — are very separated because we perceive these as so specialized that one person cannot not do both of them. This basic assumption is the blocker to the next evolution in web creativity.

需要发生的主要飞跃是设计人员必须具有一种直观的意愿,将他们试图实现的视觉逻辑与理解如何在代码约束中表达其视觉决策联系起来。 数字产业之所以没有实现这一飞跃,更多的是归因于便利性以及保持划定角色和过程的渴望。 现在,这两个世界-Web体验的可视化和它们在代码中的实现-已非常分开,因为我们认为这两个世界是如此专业,以至于一个人不能同时做这两个世界。 这个基本假设阻碍了Web创造力的下一次发展。

People are wired to make these kinds of innovative connections and we eventually will. Like the adoption of any new behavior, at some point in the near future the prototype and the real web experience will evolve and become one due to economic and technological necessity. It is not a matter of if, it is just a matter of when.

人们渴望建立这种创新的联系,而我们最终会。 像采用任何新行为一样,在不久的将来的某个时候,由于经济和技术的需要,原型和真实的Web体验将发展成为一种。 这不是问题,只是时间的问题。

注重细节与大创意一样重要 (Attention to detail is as important as the big idea)

For any given responsive web experience, the number of parts and pieces that need clear user experience definition, visualization and implementation can be extraordinarily large. Defining, creating and documenting these to ensure a cohesive experience requires an inherent love of detail. Depending on the flavor of designer you are, you may hate the fussy nature of web design and just want to design the big idea or you may be the kind of person that totally falls in love with the nit picky details.

对于任何给定的响应式Web体验,需要清晰的用户体验定义,可视化和实现的零件和零件的数量可能非常大。 定义,创建和记录这些内容以确保凝聚力的体验需要对细节的内在热爱。 根据您的设计风格,您可能会讨厌网页设计的繁琐本质,而只想设计一个大创意,或者您可能是完全爱上精细挑剔细节的那种人。

For the best web designers, beauty, sophistication, ease of use and a love of detail are a complete and interrelated package. Like great visuals and great code, good taste and attention to detail are not always found in one person. I have been lucky enough to work with a handful of designers that know how to expertly strike this balance but more often than not you need a team that can work together to provide overlapping expertise. In the context of contemporary brand building, digital detail is a fundamental requirement. One needs only to look at IBM’s Design Language to see that the detail and nuance in digital is both a competitive differentiator and a reflection of the level of quality, reverence and integrity designs team hold for their brands.

对于最好的网页设计师而言,美丽,精致,易用性和对细节的热爱是一个完整且相互关联的软件包。 就像出色的视觉效果和出色的代码一样,良好的品味和对细节的关注并非总是一个人找到的。 我很幸运地与少数几个知道如何熟练地达到这种平衡的设计师一起工作,但通常您需要一支可以共同提供重叠专业知识的团队。 在当代品牌建设的背景下,数字细节是基本要求。 只需查看IBM的设计语言,即可发现数字化的细节和细微差别既是竞争优势,又反映了设计团队为其品牌所拥有的质量,崇敬度和完整性。

您不能让网站做任何事情 (You can’t make a website do everything)

The internet is quite vast these days. Billions of sites doing billions of different things for different reasons. Some clients and some designers love cataloging all of the specific design, content, UI, and UX moments they see on the web with the intention of having these serve as a kind of reference toolbox for future site experiences. This is a great impulse. To add to this, sites such as Dribbble are also great for inspiration and have become a space to showcase idealized UX animation approaches that can make sites and apps look way cooler than they can be in reality. Much of this inspiration finds its way into project mood boards and can be incredibly helpful when you are working to align on creative approaches and to get people excited.

如今,互联网非常庞大。 数十亿个站点出于不同原因而做数十亿种不同的事情。 一些客户和一些设计师喜欢对他们在网络上看到的所有特定设计,内容,UI和UX时刻进行分类,目的是将它们用作将来站点体验的一种参考工具箱。 这是一个很大的冲动。 除此之外,Dribbble之类的网站也很受启发 ,并且已成为展示理想的UX动画方法的空间,该方法可以使网站和应用看起来比实际的要酷。 这些灵感大部分都可以用到项目情绪板中,当您努力调整创意方法并激发人们的热情时,它们会非常有用。

For all of this great inspiration and reference, we know that you can’t make a website do everything you see on the web all at once. It would be like shopping for a car by going to every dealership and glueing all of your favorite features together to make your own car. If you do this, your car will certainly not run well and it will certainly look terrible. The same goes for websites.

对于所有这些伟大的灵感和参考,我们知道您无法使网站一次完成您在网络上看到的所有事情。 这就像去每个经销商处购买汽车并将所有您喜欢的功能粘合在一起以制造您自己的汽车一样。 如果这样做,您的汽车肯定不会运转良好,并且看起来肯定会很糟糕。 网站也是如此。

Reverse engineering cool web ideas you see out in the world is not inherently bad. What is bad is assuming that combing many ideas you like is the right way to solve the digital problem at hand. Ideally we develop web products and experiences by coming from a clear and informed strategic foundation with a firm understanding of business needs and technological limitations so that we do not create experiences that do not solve the intended problem, that are difficult to build, and are impossible to maintain.

您在世界上看到的反向工程很酷的Web想法并不是天生就坏的。 糟糕的是,假设将您喜欢的许多想法组合在一起是解决当前数字问题的正确方法 。 理想情况下,我们通过清晰明了的战略基础来开发Web产品和体验,并且对业务需求和技术局限性有深刻的了解,以便我们不会创建无法解决预期问题,难以构建且不可能的体验保持。

People that are not technical tend to focus on what they can understand and that is the surface. As an example, I have been in situations where I have had to convince a client that we were not creating a web experience optimized for their personal iPad. We had to educate them on how the behavior of your finger navigating a site is inherently different than navigating a site on a person’s desktop using a mouse. For them, apps and sites were one and the same thing and they were annoyed that their site could not do everything a native app could when they were chilling at the office on their iPad. This probably seems rather silly and naive to people that design and build for the web but for many these basic misunderstandings and false assumptions persist. Due to this lack of knowledge we must acknowledge that without proactive education and context, some level of dysfunction will remain within any project.

非技术人员倾向于将重点放在他们可以理解的内容上,那就是表面。 举例来说,我一直不得不说服客户我们没有为他们的个人iPad创建优化的网络体验。 我们必须教育他们,用手指导航站点与使用鼠标在人的桌面上导航站点的行为有本质的不同。 对于他们来说,应用程序和网站是一回事,而他们恼怒的是,当他们在iPad上办公时,他们的网站无法完成本机应用程序所能做的一切。 对于为网络设计和构建的人们来说,这似乎很愚蠢和幼稚,但是对于许多这些基本的误解和错误的假设仍然存在。 由于缺乏知识,我们必须承认,没有积极的教育和背景,任何项目中都会存在一定程度的功能障碍。

Providing ongoing context and client education and at the very least understanding how savvy your clients are is crucial. To reduce the danger of trying to make a UX hodge-podge “Dribbble soup” of a site you have to build a process that aligns strategic and business goals with design and experience solutions that are contemporary and cool but are also focused and realistic. This requires lots of talking, rationalizing and education but it is a necessity to ensure that our web collecting eyes don’t get larger than our performant and complaint digital stomach.

提供持续的环境和客户教育,并且至少了解客户的机敏至关重要。 为了减少尝试在站点上制作UX大杂烩“ 滴落汤”的危险,您必须构建一个流程,使战略和业务目标与现代,凉爽但又专注且切合实际的设计和体验解决方案保持一致。 这需要大量的讨论,合理化和教育,但必须确保我们的网络收集人员的眼睛不会超过我们的表演者并抱怨数字胃。

形式和内容不是一回事 (Form and content are not the same thing)

A website is only as good as the information within it. Over the last 20 years, this basic concept still remains the most challenging for clients to understand. Some folks still have a hard time grasping the idea that no amount of good design can improve bad content.

网站仅与其中的信息一样好。 在过去的20年中,这个基本概念仍然是客户理解中最具挑战性的。 有些人仍然很难理解这样的想法,即没有多少好的设计可以改善不良的内容。

If you put a TV show on a more expensive TV does the show become narratively better? If you put a baby behind the wheel of a Lamborghini do they become an expert driver? You get the idea. Developing well crafted information — language, photography, video, illustrations, audio and the like is the necessary baseline for a great site experience. Full stop.

如果将电视节目放到价格更高的电视上,电视节目的叙事效果会更好吗? 如果您将婴儿放在兰博基尼的方向盘上,他们会成为专家吗? 你明白了。 开发精心制作的信息-语言,摄影,视频,插图,音频等是获得出色网站体验的必要基础。 句号

The push and pull between form and content is as old as the need for clear communication. Designing for the web is one of those unique mediums where you can actually develop formal systems that can serve as a forcing function to improve content creation.

形式与内容之间的推拉与消除清晰沟通的需求一样古老。 Web设计是那些独特的媒介之一,您可以在其中实际开发形式系统,这些系统可以用作强制功能来改善内容创建。

Creating modular content patterns that leverage the natural information consumption behaviors of the web can be extremely useful when a client is unsure how to optimize their storytelling. Building a formal scaffolding that also serves as an ideal narrative guide can provide more rigorous parameters around how and what to write in a way that has the most impact online and especially on mobile devices.

当客户不确定如何优化故事讲述时,创建利用网络自然信息消费行为的模块化内容模式将非常有用。 构建一个正式的脚手架,也可以作为理想的叙述指南,从而可以提供有关如何写和写什么的更严格的参数,以对在线尤其是对移动设备的影响最大的方式进行。

Brands like Notion and Apple understand how digital craft, editorial economy, visual impact and crisp communication can all come together to provide a great online narrative experience. To do this right takes discipline as well as a solid understanding of how developing replicable narrative systems that seamlessly blend the form and content of a site can help keep communication sharp and beautiful.

诸如Notion和Apple之类的品牌了解数字技术,编辑经济,视觉冲击力和清晰的沟通方式如何融合在一起,以提供出色的在线叙事体验。 要做到这一点,需要纪律和对开发可复制的叙事系统无缝地融合站点形式和内容如何有助于保持沟通的清晰和美观的深刻理解。

倾听并尊重您的开发人员 (Listen to and respect your developers)

The web would not function as a contemporary communication medium unless really smart developers cared deeply about their work. There has never been enough really, really good developers on this planet. We always need more. As a designer I admit I am biased. I think we have too many “good” formal designers in the world but not enough amazing designers that also know how to work with developers in an integrated and nuanced way to make great experiences.

除非真正精明的开发人员深切关心他们的工作,否则网络将无法充当现代通信媒介。 在这个星球上,从来没有足够的真正优秀的开发人员。 我们总是需要更多。 作为一名设计师,我承认我有偏见。 我认为我们世界上有太多“优秀”的正式设计师,但没有足够出色的设计师,他们也知道如何以集成且细微的方式与开发人员合作,以创造良好的体验。

Since the advent of mobile devices and the wholesale adoption of responsive design, we probably all agree that designing for the web has become really annoying. There seems to be too many moving parts! We can’t escape this but we also can’t ignore it either. We are at an inflection point where developers are really co-designers because a smart development team has a better understanding of the technological dependencies and constraints that fundamentally inform the sandbox an amazing designer has to operate within.

自从移动设备问世并大量采用响应式设计以来,我们可能都同意,为Web设计变得非常烦人。 活动部件似乎过多! 我们不能逃避这个,但是我们也不能忽略它。 我们正处在一个拐点,开发人员是真正的联合设计师,因为一个精明的开发团队对技术依赖性和约束有更好的了解,这些技术和约束从根本上告诉沙箱一个出色的设计师必须在其中工作。

In the past, people in business, management and creative roles did not deeply consider all of the technology infrastructure work required before a project begins. Again, it is human nature to focus on the things you understand and ignore the things you don’t. This kind of blissful ignorance is rapidly fading as creative and technology tools and processes merge. In the not too distant future design teams and development teams will blend in a way that will produce better work faster. I’m not talking about a world of all night design and development hackathons. In contrast, I believe that the developer mindset is rubbing off on the design mindset (and vice versa) and that we will find more and more common ground and mutual admiration happening as these two worlds continue to overlap and inform each other.

过去,担任业务,管理和创意职务的人员没有深入考虑项目开始之前所需的所有技术基础结构工作。 同样,专注于您理解的事物而忽略您不理解的事物是人类的天性。 随着创意和技术工具与流程的融合,这种幸福的无知正在Swift消失。 在不久的将来,设计团队和开发团队将以一种可以更快地产生更好工作的方式融合在一起。 我并不是在谈论一个通宵的设计和开发黑客马拉松的世界。 相比之下,我认为开发人员的思维方式正在设计思维方式上逐渐削弱(反之亦然),并且随着这两个世界继续交叠并相互交流,我们将发现越来越多的共同点和相互钦佩。

拥抱最佳做法,文档和可访问性 (Embrace best practices, documentation and accessibility)

Personally, I’ve always had a kind of “Life Hack” philosophy when it comes to designing for the web. I have poorly rigged Lottie animations into sites, stolen heaps of Javascript, butchered WordPress Themes, you name it. As a designer, I felt I should do whatever I thought was required to sell in an idea. This approach is fine if you plan to throw it all away later. But in this day and age, you have to lead by doing things the right way even if it might be a little harder or a little slower.

就个人而言,在设计网络时,我一直都有一种“ Life Hack”的哲学。 我没有很好地将Lottie动画装配到网站,被盗的Javascript堆中,却将WordPress主题屠杀了,随便您如何命名。 作为设计师,我觉得我应该做我想卖出一个想法所需的一切。 如果您打算稍后将其全部丢弃,则此方法很好。 但是在当今时代,即使有些困难或更慢,您也必须以正确的方式做事。

In the fast paced world of the web, the worst thing you can do is half-ass it now because it will come back to haunt you later. Unraveling someone else’s undocumented code base is a horrible thing to have to do. When it comes to the web, a stitch in time saves nine. To this end, establishing a digital philosophy and clear tactics around handling best practices is an absolute necessity. A big part of this is about clear documentation. Building sites can get gnarly and the only way to not have this information be in the head of just one person is to write it all down.

在快速发展的网络世界中,您现在最糟糕的事情就是半打它,因为稍后它会再次困扰您。 破解别人未公开的代码库是一件非常可怕的事情。 当涉及到网络时,一针一针可节省九个针脚。 为此,绝对有必要围绕处理最佳实践建立数字哲学和清晰的策略。 其中很大一部分是关于清晰的文档。 建筑工地可能会令人生厌,只有一个人才能掌握这些信息,唯一的方法就是将其全部写下来。

Your technology stack should be created in a way so that someone not as smart as you can understand it and spin it up locally. This is because no two developers work in the same way and given the rapid nature of what we do, you may need to onboard someone new that is also less experienced. When it comes to developing for the web, the more you can think ahead and future-proof the better.

应该以某种方式创建您的技术堆栈,以便不那么聪明的人可以理解它并在本地旋转它。 这是因为没有两个开发人员以相同的方式工作,并且鉴于我们所做的工作具有快速性,您可能需要聘请经验不足的新手。 在进行网络开发时,您可以思考的越多,面向未来的越好。

Compliance is also something you need to understand and have a stance on. Currently minimum requirements for ADA compliance are still open for interpretation but you never know when someone might have an issue so it is better to know what your baseline is so that you can clearly articulate how you are handling WCAG 2.0.

合规性也是您需要了解并保持立场的东西。 当前,有关ADA遵从性的最低要求仍然可以解释,但是您永远不知道何时有人可能遇到问题,因此最好知道您的基线是什么,以便您清楚地阐明如何处理WCAG 2.0 。

网络糟透了。 网络万岁! (The web sucks. Long live the web!)

Designing and building for the web will always be a fluid evolutionary vocation. Nothing really stays the same and new things are always on the horizon. This is what I love most about designing for the web. It keeps us learning and growing but it can also be extremely frustrating.

网络的设计和构建将永远是一项不断发展的职业。 没有什么可以保持不变,新事物总是在眼前。 这是我最喜欢的网络设计。 它使我们不断学习和成长,但也可能使他们非常沮丧。

The one thing I always try to remind clients and teams is it is just a website. We are not building a suspension bridge or doing brain surgery. We can push code, make fixes and try new things. This ability to iterate is what makes the web a fun medium to work in if you have the right temperament. I hate the web and I love the web as well. It’s a proverbial oily watermelon floating in the deep end that we are always trying to grab ahold of. Just as soon as we have a handle on it, it slips through our fingers. As long as we know this and embrace uncertainty while reaching for perfection, then the web will be an amazing place to push creativity and technology for decades to come.

我一直试图提醒客户和团队的一件事是它只是一个网站。 我们没有在建造吊桥或进行脑部手术。 我们可以推送代码,进行修复并尝试新事物。 这种迭代能力使网络成为一种有趣的媒介,如果您具有适当的性情,则可以使用它。 我讨厌网络,也喜欢网络。 这是漂浮在深处的油腻西瓜,我们一直在努力抓住。 只要握住手柄,它就会滑过我们的手指。 只要我们知道这一点并在追求完美的过程中拥抱不确定性,那么网络将是未来数十年推动创造力和技术发展的绝佳之地。

I would like to give special thanks to our Technical Director at Athletics Ross Luebe. He helped vet this article and gave me many helpful suggestions. As Technical Director, Ross is responsible for interfacing with clients, designers and developers and serves as a conduit and mediator to ensure that our teams are speaking the same language. Ross has the rare advantage of having a Master’s Degree in Graphic Design while having also gained very deep technology expertise over the last decade. This allows him to understand the common ground between design and technology and what needs to happen to get the best out of both.

我要特别感谢我们 田径运动 的技术总监 Ross Luebe。 他帮助审查了这篇文章,并给了我许多有用的建议。 作为技术总监,Ross负责与客户,设计师和开发人员进行交互,并充当渠道和调解人,以确保我们的团队使用相同的语言。 Ross具有罕见的优势,即拥有图形设计硕士学位,同时在过去十年中也获得了非常深厚的技术专业知识。 这使他能够了解设计和技术之间的共同点,以及如何才能充分利用两者。

翻译自: https://uxdesign.cc/designing-the-modern-web-f62860d850f2

现代天线设计


http://www.taodudu.cc/news/show-5964896.html

相关文章:

  • Android不同版本特性知识点
  • 设计模式阶段总结
  • android 屏幕投射_将自定义内容从Android应用投射到电视(2020年方法)
  • 机械表矢量素材分享(三眼表盘意向:过去、现在、未来)
  • Qt汽车自定义仪表盘控件
  • QT绘制仪表盘
  • Android简易仪表盘
  • 73.qt quick-通用可拖拽表盘示例(支持渐变)
  • 【QT 5 相关实验-仪表盘-学习笔记-表盘组件练习与使用总结】
  • android带指针仪表盘自动移动,Android 绘制仪表盘指针刻度
  • 如何更改Apple Watch上的表盘
  • wxid转微信
  • 怎么转换wxid?? 怎么添加wxid的号码???
  • wxid转微信号
  • 【分享】如何在集简云更换账户的微信、邮箱、手机号?
  • php微信号轮播系统,微信小程序的轮播功能
  • WXID怎么转换成微信号
  • 锚链接html target,列锚标签()的target属性中,哪一个可以定义在新窗口中打开链接地址()。 - 问答库...
  • camera资料链接整理
  • 载纳米雄黄磁性白蛋白纳米球/壳聚糖修饰/As2O3磁性Fe3O4白蛋白微球
  • batocera中文整合包_分享一个整合 SSM 框架的高并发和商品秒杀项目
  • windows server 2008R2/2012R2安装
  • 友情代码c语言,我的友情链接
  • 【看表情包学Linux】软硬链接
  • inode和软硬链接
  • 文件系统与软硬链接
  • 微软Windows10LTSC2019官方三月更新版镜像
  • js实现磁性吸附
  • Linux的文件系统和软硬链接
  • VS code 格式化设置代码标签不换行

现代天线设计_设计现代网络相关推荐

  1. 智能家居数据库设计_设计更智能的数据表

    智能家居数据库设计 重点 (Top highlight) Data tables are hard. There are many different ways to think about them ...

  2. 网页原型设计工具设计_设计工具用完了

    网页原型设计工具设计 by Colm Tuite 通过Colm Tuite 设计工具已超出预期. 这是我们如何修复它们的方法. (Design tools are running out of tra ...

  3. 网络工程课程设计_某学校网络设计

    网络工程课程设计--某学校网络设计 Spring框架是一个开源的JavaEE的应用程序 主要核心是IOC(控制反转/依赖注入)和AOP(面向切面编程)两大技术 1. 需求分析 1.1 用户需求 用户需 ...

  4. java web网络硬盘设计_基于JavaEE网络硬盘的设计与实现

    DOI. 10.14004巧cnkl.ckt. 2015,3111 1课题背景 随着信息化进程的加快,文件的存储数量的逐年递增,在朋友同事之间文件数据相互之间进行分享学习越来越频繁,因此在工作和生活中 ...

  5. 生成对抗网络的损失函数如何设计_生成对抗网络(GAN)

    GAN的全称是 Generative Adversarial Networks,中文名称是生成对抗网络.原始的GAN是一种无监督学习方法,巧妙的利用"博弈"的思想来学习生成式模型. ...

  6. ui设计中的版式设计_设计中的版式-第3部分

    ui设计中的版式设计 and how not to suck at it 以及如何不吸吮它 This is the 3rd and last part of the series. Here we t ...

  7. figma设计_设计原型的最简单方法:Figma速成课程

    figma设计 It doesn't matter if you haven't used any prototyping tools before or you're transitioning f ...

  8. 办公室白墙文化墙设计_设计对文化敏感的人工智能设备

    办公室白墙文化墙设计 By: Mary Huber 创建人:Mary Huber As digital assistants like Siri and Alexa become more commo ...

  9. 物联网络连万物教学设计_设计中的万物有灵

    物联网络连万物教学设计 The complexity of our interactions and relationships with objects and interfaces can be ...

最新文章

  1. oracle library cache lock,【案例】Oracle等待事件library cache lock产生原因和解决办法...
  2. 视觉实战|使用人工神经网络进行图像分类
  3. Zsh vs. Bash不完全对比解析,zsh是一种更强大的被成为“终极”的Shell
  4. Android开发之微信支付获取签名小工具分享
  5. java stopself_如何正确停止前台服务?
  6. php中手机端ajax上拉加载更多,jQuery手机网页上拉加载更多
  7. 软件测试抛出异常,异常测试之异常注入初探
  8. 荣耀MagicV今晚亮相:刷新对传统折叠屏厚重的认知
  9. 使用 nginx 搭建简易文件服务器
  10. 复杂,软件的大敌![转]
  11. MySql常用函数大全(详细)
  12. c#窗体编辑个人简历_C#个人简历完整代码
  13. 2022-2027年中国DTP药房行业市场全景评估及发展战略规划报告
  14. 新知实验室TRTC初探
  15. 解决虚拟机IP地址无法获取和网络无法连接
  16. THUPC 2019 CTS 2019 打铁记
  17. Git命令提交项目代码
  18. vmware虚拟机删除光驱启动报错解决办法
  19. rust提示游戏安全违规_RUST 游戏启动不了 每次都是 Rust Launcher Error: Loading Error - Start Service failed (1450)...
  20. 2011 Asia Beijing Regional Online Contest-1004 hdu4043 FXTZ II

热门文章

  1. 快速开发实用工具VRTK-001:005
  2. linux使用xrdp远程
  3. 2018驾考宝典面试总结
  4. Game(Chinese)
  5. 中国全自动榨汁机行业市场深度分析及发展规划咨询综合研究报告
  6. 【积累】性能测试-响应时间的‘2-5-8’原则
  7. 项目管理 : 开除不合格的项目经理
  8. phpmyadmin常见getshell的方法
  9. 智能AI计算芯片对比
  10. 学习笔记19--自动驾驶智能化指标评测体系(下)