4 ms·

Thanks for launching! I want to submit mine, but can you please add Dart (language) and Flutter (framework?). My starter project is for Flutter, https://github

Thanks for launching! I want to submit mine, but can you please add Dart (language) and Flutter (framework?). My starter project is for Flutter, https://github.com/wiradikusuma/starter-flutter https://github.com/wiradikusuma/starter-flutter and it's part of my upcoming book about building mobile apps, https://opinionatedlaunch.com/ https://opinionatedlaunch.com/

ecuaflo 4y ago
Thank you for the interest and sorry about missing those! They are added now :) Good luck with your own project! Let me know if there are any features that starter.place could add to help you.
- wiradikusuma 4y ago
  Thanks! Actually I noticed 2 issues in any starter project: 1. First thing someone does after clone is search-and-replace e.g. com.example to com.mycompany. Sometimes it results in broken code or partial replacement e.g. bcoz the phrase is whitespace-separated. 2. Starter code can be very complex. For my starter project, I ensure each commit is "atomic" e.g. one commit for unit tests, another for swagger-generation. So that people can follow it easily. So I'm just wondering if you can "standardize" those two, or even provide "UI"?
  - ecuaflo 4y ago
    Those are important but tough problems! 1. I feel like codemods and a setup shell prompt are the best solution to this, but this looks different for each language (eg, in JS there is https://github.com/facebook/jscodeshift https://github.com/facebook/jscodeshift). I could make UI around that for listers to provide parts of the app that should replaced and buyers to provide values for it, but it could be quite a rabbit hole. This is actually why I show the README for the repos, so users can see if the setup steps are comprehensive before buying (for paid ones). 2. I agree atomic commits can help someone navigate a new codebase. In the same spirit as my response to #1, I don't feel confident I could enforce this, but I could surface the commits on the starter repo page so potential buyers could see if the author laid things out well. Thanks for the ideas!

ecuaflo 4y ago

Thank you for the interest and sorry about missing those! They are added now :) Good luck with your own project! Let me know if there are any features that starter.place could add to help you.

wiradikusuma 4y ago
Thanks! Actually I noticed 2 issues in any starter project: 1. First thing someone does after clone is search-and-replace e.g. com.example to com.mycompany. Sometimes it results in broken code or partial replacement e.g. bcoz the phrase is whitespace-separated. 2. Starter code can be very complex. For my starter project, I ensure each commit is "atomic" e.g. one commit for unit tests, another for swagger-generation. So that people can follow it easily. So I'm just wondering if you can "standardize" those two, or even provide "UI"?
- ecuaflo 4y ago
  Those are important but tough problems! 1. I feel like codemods and a setup shell prompt are the best solution to this, but this looks different for each language (eg, in JS there is https://github.com/facebook/jscodeshift https://github.com/facebook/jscodeshift). I could make UI around that for listers to provide parts of the app that should replaced and buyers to provide values for it, but it could be quite a rabbit hole. This is actually why I show the README for the repos, so users can see if the setup steps are comprehensive before buying (for paid ones). 2. I agree atomic commits can help someone navigate a new codebase. In the same spirit as my response to #1, I don't feel confident I could enforce this, but I could surface the commits on the starter repo page so potential buyers could see if the author laid things out well. Thanks for the ideas!