易辅客栈 从零学辅助

易辅客栈 从零学辅助

Want to launch a side project, but not sure where to begin? Since 2017, I have launched several projects, including Spider, Pretzel, Stitches and Dribbble color palette.

想要启动辅助项目，但不确定从哪里开始？ 自2017年以来，我启动了多个项目，包括Spider ， 椒盐 脆饼 ， Stitches和Dribbble调色板 。

At first, it wasn’t clear which steps of the launch process were more important than others. But after my third launch, I had hatched a plan and started tweaking it. In this article, I will share the lessons I learned and walk you through the process of making a product. Hopefully you can take this as a starting point or inspiration, and make something tailored for yourself.

起初，尚不清楚启动过程中哪些步骤比其他步骤更重要。 但是在我的第三次发布之后，我已经制定了一个计划并开始对其进行调整。 在本文中，我将分享我学到的教训，并引导您完成产品的制造过程。 希望您可以以此为起点或灵感，并为自己量身定做。

Start by checking out this checklist that I’ve developed over a number of side projects. Feel free to run with it and adapt it for your own projects.

首先检查一下我在多个附带项目中开发的清单 。 随意运行它，并使其适合您自己的项目。

Every time I launch a project, I tweak this process a little bit. Seems like a lot, but I enjoy every aspect of it ⚡️ #indiehackershttps://t.co/4XN4yUm6bZ

每次启动项目时，我都会对此过程进行一些调整。 似乎很多，但我喜欢它的各个方面⚡️ #indiehackers https://t.co/4XN4yUm6bZ

— Amie Chen (@hyper_yolo) April 12, 2019

-Amie Chen(@hyper_yolo) 2019年4月12日

1.保留问题笔记本 (1. Keep a Problem Notebook)

Many of us keep an idea notebook, but I would advocate keeping a “book of grudges”: one with problems and wrongs you find intriguing to solve. Mine is a kanban board with different labels — design, social, security, etc. With these labels, I know what problem could be easily solved with a post-it note, and what could be solved by a clever app. I stare at this board often and maintain it diligently — it tells me what my current priority is, and what the next long term goal is.

我们中的许多人都保留着一个想法笔记本，但我会提倡保留一本“怨恨书”：您会发现有趣且容易解决的问题和错误。 我的是一个看板，上面贴有不同的标签-设计，社交，安全性等。有了这些标签，我知道使用便签纸可以轻松解决哪些问题，而聪明的应用程序可以解决哪些问题。 我经常盯着董事会，并努力地维护它-它告诉我当前的优先事项是什么，以及下一个长期目标是什么。

2.首先了解自己 (2. Know Yourself First)

If you’re like me, your book of grudges is extensive. To figure out what is worth spending time on, let’s start with why. Why do you want to create a product?

如果您像我一样，您的怨恨之书就很广泛。 为了弄清楚什么值得花时间，让我们从为什么开始。 为什么要创建产品？

For me, there are two reasons:

对我来说，有两个原因：

I like helping people and listening to their daily struggles. It gives me different perspectives on life.

我喜欢帮助人们，倾听他们的日常挣扎。 它给了我关于生活的不同看法。 Nothing brings me as much joy as making things. The satisfaction of creating something of my own is far greater than any shiny new job or huge paycheque.

没有什么能像制作东西一样带给我最大的快乐。 创造自己的东西所获得的满足远胜于任何崭新的工作或丰厚的薪水。

With the two causes combined, I noticed I’m drawn to smaller and refined issues. You can spot a trend among all the products I’ve made — they are utilitarian and focused.

结合这两个原因，我注意到我对较小和精致的问题着迷。 您可以在我生产的所有产品中发现一种趋势，它们既实用又专注。

So, ask yourself why to narrow the field of selections. If new technologies and the possibilities they bring fascinate you, maybe an open-ended, AR powered camera app would excite you. Whatever you choose, starting by understanding your cause will help you feel less overwhelmed.

因此，问自己为什么要缩小选择范围。 如果新技术及其带来的可能性让您着迷，那么开放式，基于AR的摄像头应用程序可能会让您兴奋。 无论您选择什么，从了解您的原因开始，都会帮助您减少不堪重负的感觉。

3.构思与设计 (3. Ideation and Design)

Once you have a problem to tackle and you’re armed with enough knowledge regarding the problem, it’s time to ideate the solution. During ideation, the only goal is to generate as many solutions as possible without being judgmental. I write my ideas out in a Markdown file and keep the session around 30 minutes.

一旦您有问题要解决并且已经掌握了足够的关于该问题的知识，就可以构思解决方案了。 在构思过程中，唯一的目标是在没有判断力的情况下产生尽可能多的解决方案。 我将自己的想法写在Markdown文件中，并将会议时间保持在30分钟左右。

Sometimes, I sit on this Markdown file for several days while doing more research. Once I decide on an approach, then I can start writing user stories and sketching wireframes. Because these latter two steps both require a clear path, I try to iron out all the doubts and questions beforehand.

有时，我会在这个Markdown文件上呆几天，同时进行更多研究。 一旦确定了方法，就可以开始编写用户故事并绘制线框草图。 由于后两个步骤都需要一条清晰的道路，因此我尝试事先消除所有疑问。

Writing user stories is like envisioning how the user would use the product in detail. Here is an example of what I did for Spider:

写用户故事就像预想用户将如何详细使用产品。 这是我为Spider所做的示例：

As you can see, every step explains “what user sees and what user does.” It creates a clear workflow that makes drawing wireframes a breeze.

如您所见，每个步骤都说明“用户看到的内容以及用户所做的事情”。 它创建了清晰的工作流程，使绘制线框变得轻而易举。

4.品牌和高保真模型 (4. Branding and High-fidelity Mockups)

Often times I spend one or two days working on the visual design and branding. Many would argue that’s unnecessary for an MVP — but I think there’s a value in a good first impression and cohesive branding. Plus, the designer in me really enjoys this part.

我经常花一两天的时间进行视觉设计和品牌塑造。 许多人会认为这对于MVP来说是不必要的，但我认为良好的第一印象和具有凝聚力的品牌是有价值的。 另外，我里面的设计师真的很喜欢这一部分。

To design efficiently, I recommend maintaining a small toolkit that consists of:

为了高效设计，我建议维护一个小型工具箱，其中包括：

an extensive UI kit in Sketch or Figma

Sketch或Figma中的扩展UI套件 a few of your favorite fonts and pairings

一些您喜欢的字体和配对 a few of your favorite color palettes

一些您最喜欢的调色板 a versatile SVG icon library

通用的SVG图标库

Also, focus on nailing these design assets first:

另外，首先要重点关注这些设计资产：

The button style in hover and normal state

悬停和正常状态下的按钮样式 The body font vs the title

正文字体与标题 The input style

输入样式 The navigation

导航

Remember, try not to spend too much time fussing over details.

记住，不要花太多时间在细节上忙乱。

5.编码 (5. Code It Up)

When it comes to development, I (would rather) believe no one spits out beautiful code on the first go. Though time consuming, an iterative approach works better for me. Usually, I start by writing a functional app (with terrible code) to prove the concept. After that, I play with the end result and think about how I can do it better. Finally, I scratch the whole thing and rewrite everything — this time with quality and maintainability in mind. The second iteration should result in better quality code.

在开发方面，我(宁愿)相信没有人会一开始就吐出漂亮的代码。 尽管很耗时，但是迭代方法对我来说更好。 通常，我首先编写一个功能强大的应用程序(具有可怕的代码)来证明这一概念。 之后，我会尝试最终结果，并思考如何做得更好。 最后，我从头开始，并重写了所有内容，这次是考虑到质量和可维护性。 第二次迭代应产生更好质量的代码。

The Basecamp team rewrites their app from the ground up every four years. It’s an approach I find necessary if you want to keep a focused product and maintain a manageable code base.

Basecamp团队每四年重新编写一次其应用程序。 如果您要保持专注的产品并维护可管理的代码库，我认为这是一种必要的方法。

6.传播圣言 (6. Spread the Word)

All the usual marketing strategies aside, what I found to be effective is simply telling someone about a thing by showing them how it’d be useful to them. With that in mind, it’s crucial to focus on these things:

除了所有常规的营销策略，我发现有效的方法只是通过向某人​​展示某件事对他们有用来告诉他们。 考虑到这一点，关键是要专注于以下方面：

A clear elevator pitch for the product

产品的清晰电梯间距 Demo video of how the product can help people

产品如何帮助人们的演示视频 Marketing website with a feature list and FAQ

具有功能列表和常见问题的营销网站 Documentation

文献资料 Consistent, high-quality promotion assets for various platforms like Product Hunt/Twitter/email

适用于各种平台的一致，高质量的促销资产，例如Product Hunt / Twitter / email

When people are confused about your product, they move on. Be as honest and clear as you can be — it speaks to people better that way!

当人们对您的产品感到困惑时，他们会继续前进。 尽可能诚实和清晰-这样可以更好地与人交流！

结论 (Conclusion)

We all have something inside that we’d like to share with the world: it could be an idea, a project or a talent. Don’t let the imposter syndrome cripple you. More likely than not, you are ready to create something of your own. Add something to the world that only you can add to it.

我们每个人都有想要与世界分享的东西：它可能是一个想法，一个项目或一个人才。 不要让冒名顶替者综合症使您瘫痪。 您很有可能准备创建自己的东西。 向世界添加一些只有您可以添加的东西。

Want to learn more about building side projects? Head over to SitePoint Premium and check out The Profitable Side Project Handbook by Rachel Andrew, alongside hundreds of other web development books.

想更多地了解建设附属项目？ 前往SitePoint Premium，并查看Rachel Andrew撰写的《 Profitable Side Project Handbook》以及其他数百本We​​b开发书籍。

翻译自: https://www.sitepoint.com/how-to-launch-a-side-project-from-zero/

易辅客栈 从零学辅助

相关资源：jdk-8u281-windows-x64.exe