cmd命令 启动移动端应用
by Michal Bialas
由Michal Bialas
In this article, I would like to present a short guide on how to release mobile apps. I’ll emphasise the internal releases. I’m also not limiting myself to Android, as I believe this may apply to iOS as well.
在本文中，我想提供有关如何发布移动应用程序的简短指南。 我会强调内部版本。 我也不限于Android，因为我认为这也可能适用于iOS。
I split this article into some points just to increase readability. If you’d like to get to know more, please stay with me! I hope you will like it.
我将本文分为几部分，只是为了提高可读性。 如果您想了解更多，请和我在一起！ 我希望你会喜欢。
1。 确保所有测试都通过 (1 . Make sure all your tests pass ✅)
If you write end-to-end unit and integration tests, you should always take care to check their output. If they fail, make them work.
如果编写端到端单元测试和集成测试，则应始终注意检查其输出。 如果失败，请使其工作。
2.对您的应用执行完整的完整构建 build (2. Perform a clean full build of your app ✅)
If you obfuscate code on Android and use ProGuard, make sure it does not remove code which may lead the app to crash. You can read about code shrinking here.
如果您在Android上混淆代码并使用ProGuard ，请确保不会删除可能导致应用程序崩溃的代码。 您可以在此处阅读有关代码缩减的信息 。
The full build can be performed on your local machine as well as using Continuous Integration.
完整构建可以在本地计算机上执行，也可以使用持续集成进行 。
If you or your company own a server, you can set-up your CI flow using Jenkins (which is free open source automation server). If not, you can easily use one of many CI services available on the market. I can recommend, for example, Bitrise, CircleCI, Travis and Bitbucket Pipelines.
如果您或您的公司拥有服务器，则可以使用Jenkins (这是免费的开源自动化服务器)来设置CI流。 如果没有，您可以轻松使用市场上众多CI服务之一。 我可以推荐例如Bitrise ， CircleCI ， Travis和Bitbucket Pipelines 。
Travis is already integrated with Github, so I if you have a paid plan, it could be your choice. If you use Bitbucket, it is the same for Bitbucket Pipelines.Bitrise has many great integrations with services like Slack, Fabric, XCode Archive, CocoaPods, Gradle Runner, Jira and many more. I wrote a short article about CircleCI some time ago, so if you are interested, you can check it out on my blog.
Travis已与Github集成在一起，因此，如果您有付费计划，则可以选择它。 如果您使用Bitbucket，则对于Bitbucket Pipelines来说是相同的。 Bitrise与Slack，Fabric， XCode Archive ， CocoaPods ， Gradle Runner ， Jira等服务具有许多出色的集成。 不久前，我写了一篇有关CircleCI的简短文章，因此，如果您有兴趣，可以在我的博客上查看。
3.执行静态代码分析 ✅ (3. Perform static code analysis ✅)
Make sure you use tools like:
确保使用以下工具：
Lint (for Java and Kotlin which is available by default in Android Studio ver. 3.1 and above), ktlint, pmd, checkstyle, findbugs, detekt, gradle-static-analysis-plugin for Android
Lint( 适用于Java和Kotlin，默认情况下在Android Studio版本3.1及更高版本中可用 )， ktlint ，pmd，checkstyle，findbugs， detekt ， gradle-static-analysis-plugin( 适用于Android)
OCLint, tailor, SwiftLint, Clang Static Analyzer, Infer, SwiftFormat, Swimat, Faux Pas for iOS
OCLint ， 裁缝 ， SwiftLint ， Clang静态分析器 ， 推断 ， SwiftFormat ， Swimat ， iOS的 Faux Pas
Of course, use only the tools you find helpful to increase the quality of the project you are currently working on.
当然，仅使用发现有用的工具来提高当前正在处理的项目的质量。
4.为内部需求准备调试和生产版本 ✅ (4. Prepare debug and production builds for internal needs ✅)
Make sure you prepare a debug and production version of your app and release it internally for testing. You should also use crash reporting tools like Instabug’s crash reports or Fabric (Crashlytics).
确保准备好应用的调试和生产版本，并在内部发布以进行测试。 您还应该使用崩溃报告工具，例如Instabug的崩溃报告或Fabric (Crashlytics) 。
It is vital to check how your app works with a debug / staging API and then with production. For Android, it also important to obfuscate code and check if it is shrunk properly.
检查您的应用程序如何与调试/登台API配合使用，然后与生产配合使用，这一点至关重要。 对于Android，混淆代码并检查代码是否正确缩小也很重要。
When releasing the version for your team, you can use TestFlight for iOS and Google Play Test channel for Android. You can also consider free tools like Fabric (which will be shutdown in mid 2019) or Hockey App which is currently transitioning to App Center.
为团队发布版本时，可以使用TestFlight 适用于iOS，适用于Android的Google Play测试频道 。 您还可以考虑使用免费工具，例如Fabric (将于2019年中期关闭 )或Hockey App (目前正在过渡到App Center) 。
5.自动化 ✅ (5. Automate ✅)
Preparing builds can be also automated. You’ve probably heard of fastlane. It is a free tool for automating screenshots, beta deployment, App Store / Google Play deployment and code signing. It is supported by all the CI and distribution services which I mentioned earlier.
准备构建也可以自动化。 您可能听说过fastlane 。 这是一个免费工具，可自动执行屏幕截图，Beta部署，App Store / Google Play部署和代码签名。 我前面提到的所有CI和分发服务都支持它。
The configuration for Android and for iOS is quite straightforward but is possible only if you have macOS. Unfortunately there is no non-macOS platform support at this moment. This is painful for Android developers who code on Linux and Windows. But there is a solution! ???
Android和iOS的配置非常简单，但只有在具有macOS的情况下才可以配置。 不幸的是，目前没有非macOS平台支持 。 对于在Linux和Windows上进行编码的Android开发人员而言，这是很痛苦的。 但是有解决方案！ ???
Gradle Play Publisher is a Gradle plugin that automates uploading an App Bundle or APK and other app details to the Google Play Store. And it is a great alternative to Fastlane. I used it quite some time ago, it works really well and I can recommend it. The documentation is comprehensive and it allows you to smooth out configuration of the tool.
Gradle Play Publisher是Gradle插件，可自动将App Bundle或APK和其他应用程序详细信息上传到Google Play商店。 它是Fastlane的绝佳替代品。 我在很早以前就使用过它，效果非常好，我可以推荐它。 该文档非常全面，可让您简化该工具的配置。
6.了解并倾听您的用户 ✅ (6. Know and listen to your users ✅)
So you checked your code, set up tools for an automation, prepared a fully operational and tested build and released it to your team for testing. But how many times have you felt like no one cares or does not have time to give you feedback? I know from experience that it is really hard to engage the team to check and play with your newly released app.
因此，您检查了代码，设置了自动化工具，准备了完整的运行和经过测试的版本，并将其发布给团队进行测试。 但是您有多少次感觉没人在乎或没有时间给您反馈？ 我从经验中知道，让团队参与检查并使用您新发布的应用程序确实很困难。
The answer for this is Instabug. I did a lot of research about tools which help to gather feedback, bugs, reports etc almost 3 years ago, and since then I have stuck to Instabug.
答案是Instabug 。 大约三年前，我对工具进行了大量研究，这些工具有助于收集反馈，错误，报告等，从那时起，我一直坚持使用Instabug。
It is really easy to integrate with any of your apps (it supports Android, iOS, React Native, Xamarin, Unity, Cordova) — it is just a few lines of code.
与您的任何应用程序集成起来都非常容易(它支持Android，iOS，React Native，Xamarin，Unity和Cordova)-只需几行代码。
How you can use this tool:
如何使用此工具：
Your users can just shake the phone and write feedback with already taken screenshots. They can even draw or record a movie, what is missing or how to reproduce a bug. It is super helpful.
您的用户只需摇动手机并使用已截取的屏幕截图编写反馈即可 。 他们甚至可以绘制或录制电影，缺少的内容或如何重现错误。 超级有帮助。
Instead of contacting developers via contact forms, end-users can ask about features or give feedback using In-App Chat. This helps a lot in connecting with the users all the time.
最终用户无需通过联系表单与开发人员联系，而是可以使用In-App Chat询问功能或提供反馈 。 一直以来都有助于与用户建立联系。
Also, developers can easily reply back to users who reported bug reports or crashes to get more context from them or thank them or even tell them that the bug/crash was fixed, and they can update an app to the latest version.
此外，开发人员可以轻松地回复报告了错误报告或崩溃的用户，以从中获得更多的信息或感谢他们，甚至可以告诉他们该错误/崩溃已得到修复，并且他们可以将应用更新为最新版本。
Use In-App Feature Requests and support your backlog by user-driven prioritising. Thanks to this feature the team and the product owner will know which feature to release first.
使用应用内功能请求并通过用户驱动的优先级支持您的积压工作。 借助此功能，团队和产品所有者将知道首先发布哪个功能。
7.监控参与度 ✅ (7. Monitor the engagement ✅)
The app is in production, but you have this feeling that people do not use your app. What to do then?
该应用程序正在生产中，但是您有一种让人不使用您的应用程序的感觉。 那该怎么办？
You can integrate tools like Google Analytics, Fabric, Amazon Pinpoint, Mixpanel or Segment.io to check:
您可以集成Google Analytics(分析) ， Fabric ， Amazon Pinpoint ， Mixpanel或Segment.io等工具来检查：
- active users, 活跃用户，
- session intervals, 会话间隔
- time in the app, 在应用中的时间，
- screen flow, 屏幕流
- retention, 保留，
- conversion, 转换，
- life time value. 生命值。
Checking these KPIs is also vital when releasing new app features to production. Do not underestimate them. ?
在发布新的应用程序功能时，检查这些KPI也是至关重要的。 不要小看它们。 ？
I believe this is it. I hope you enjoyed the checklist. If you have any insight or other tools which may help with application release, please let me know in the comments. You can also check out my other articles:
我相信就是这样。 希望您喜欢清单。 如果您有任何见解或其他工具可能对应用程序发布有所帮助，请在评论中告知我。 您还可以查看我的其他文章：
Lucky 7 new tools and plugins for Android developers & designers
25 new Android libraries and projects to check at the beginning of 2018
If you like my article, please don’t forget to click ??? to recommend it to others ???.
如果您喜欢我的文章，请不要忘记单击???。 推荐给其他人???。
Also, to be notified about my new articles and stories, follow me on Medium and Twitter. You can find me on LinkedIn as well. Cheers!
另外，要了解我的新文章和故事，请在Medium和Twitter上关注我。 您也可以在LinkedIn上找到我。 干杯!
cmd命令 启动移动端应用
5677
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
