-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📣 Tell me how you're using electron-react-boilerplate #1106
Comments
I hope this helps :) |
Mostly a "Learning experience" kind of app. The thing I was using for Pomodoros got killed, so I'm essentially remaking it. And I wanted to use Electron for it, to learn it. But I tend to get bogged down on the details so I usually "just do it" the first time around, and take more time to read more docs/etc the second time around.
Small
Myself, I might
There's way too much of it all, I get you guys are trying to cover a lot of use-cases, but I wanted a kickstarter and I feel like I got a bit more of a "You wanted a banana but what you got was a gorilla holding the banana and the entire jungle". I might've benefited from choosing a smaller solution, but since I don't know much about electron I wasn't too sure if they were somehow messing up, and this has a lot of stars so there's some degree of a popularity follows guarantee there. Next time I make an electron application I'll definitely just roll my own, though. Even for a large enterprise application I wouldn't use this again.
Flux is throwing tons of errors, app veyor is crashing (On your PRs as well, for the same reasons), but all in all I'm adapting. |
consumer apartment hunting app. works kinda like a web browser but gives users (and their groups) extra features to manage an apartment-hunt (plug: screencast)
small but growing!
small, 3 ppl, 1 main dev
I had some (not too much) trouble customizing the build pipeline. electron-builder docs are great, but maybe some diff't examples w/ this boilerplate would've helped a bit. the 2-json structure also had some 'gotchas,' but this was mainly b/c i wasn't familiar w/ native modules (as is the case, i would hazard to guess, for most folks coming from browser dev)
'frustrating' is a strong word, but coming from all those same techs on the browser side, electron is def. the steepest learning curve. the build/deploy process felt especially daunting at first ("auto-update"? "artifact?" huh?). smart on it now but was an adventure. |
|
CashNotify — monitor your Stripe accounts from your Mac's menu bar 💰.
Small-ish: 32 components, 56 actions, 20 dependencies.
2 people — doing everything related to the business, so far from full-time developers.
We really like what you've decided to include in the boilerplate and the default configuration. For us there is not too much, this is just right. The latest releases do address several of our frustrations, for example the difficulty of debugging a production build. We will upgrade soon. Suggestions:
Thank you @amilajack @chentsulin @jhen0409 for this amazing project! |
What kind of app are you making? What is the scale of the app (small, medium, large)? What is the size of your team? Are you working on this by yourself? Do you parts of the boilerplate do you find frustrating? What parts of the stack (ex. react, redux, electron, webpack) do you have the most troublesome or frustrating? |
@Unforgiven-wanda Could you please tell me about using MobX. I try to put babel transform decorators legacy but didn't succeed. Using MobX without decorators is a pain. |
@nantaphop Haven't used MobX with this particular boilerplate, instead with another one (I'm sorry, I can't remember its name) |
Oh, I already succeeded on add decorators to this boilerplate. It just
about babel plugin order. Thanks.
…On Sat, 14 Oct 2017, 02:22 Unforgiven-wanda, ***@***.***> wrote:
@nantaphop <https://github.com/nantaphop> Haven't used MobX with this
particular boilerplate, instead with another one (I'm sorry, I can't
remember its name)
I'm away for a few days, but I'll give it a shot when I'm home and let you
know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpToj6l670cOrmAVUbjndtP4hvwmjFiks5sr7h7gaJpZM4OI6Fe>
.
|
To make Recollectr (Notetaking/Knowledgebase) Thanks very much to @chentsulin and especially to @amilajack who helped me figure out some of the toughest bugs I faced. |
What kind of app are you making? (Optional) Just an internal tool What is the scale of the app (small, medium, large)? small What is the size of your team? Are you working on this by yourself? Turns out the structure of this thing is just too confusing. Maybe if I was more experienced in react + redux it would make more sense but there seems to be a lot getting in my way. Also the HMR readme pretty much says don't use it other than to experiment so I'm not sure why it's being used. What parts of the stack (ex. react, redux, electron, webpack) do you have the most troublesome or frustrating? Redux and webpack. I would like it to be more simple and straight forward and let the developer how and what they want implemented. |
What kind of app are you making? What is the scale of the app (small, medium, large)? What is the size of your team? Are you working on this by yourself? What parts of the stack (ex. react, redux, electron, webpack) do you have the most troublesome or frustrating? |
Hey @brian-sullivan, just to let you know that you can always open a new issue on this project about your issue, mentioning the steps you took, maybe some logs, etc. and someone will try to help you. |
@brian-sullivan please do make an issue. There are several people here, myself included, who will be happy to help! |
Thank you for the great project.
I've built http://label.live with many, many of native modules: usb (on Mac and windows!), fonts, App Store integration, etc. It's for sale on both Mac App Store and Microsoft Store. 👏
Medium
Solo
I started using back in August 2018 when the two package.json structure was in use. Now I'm struggling on how to migrate to the single package.json structure. It'd be helpful to have documentation on how main/renderer resolve native modules in both setups.
I think counter is a good example, but you need at least one other piece of state for it to make sense to new users. That is, have another dimension such as text, or something else that shows how reducers/actions are segmented and can grow. I have found Immutable to be absolutely necessary for developing a large redux app. |
I hope this help you a little bit :) |
|
@reZach That's awesome! I'd love if you could PR some of those changes back to the boilerplate. I'm sure they'd add a lot of value to a lot of people! |
@amilajack great cool! I'll see if I can put in a PR in the coming days for ya. |
What kind of app are you making? What is the scale of the app (small, medium, large)? What is the size of your team? Are you working on this by yourself? Do you parts of the boilerplate do you find frustrating?
What parts of the stack (ex. react, redux, electron, webpack) do you have the most troublesome or frustrating? Overall, great boilerplate and awesome work @amilajack! Would be nice with a guide on how to update to newer versions (like the one with all the TypeScript setup). |
What parts did you tear away? |
I guess if you don't want to use Edit: Oh, we did remove |
Small
Myself
When I upgrade to Typescript@4, the
I love the current stack. |
not able to see my changes when a change in the main.dev.ts file. using electron-react-boilerplate. |
I appreciate very much creating this awesome boilerplate :) |
|
Thanks for this boilerplate! 🙏
I am refactoring https://autoedit.io to use this template, to see if bringing the "react client", and "electron blackened" together in this architecture has significant performance improvements. Initially I had attempted to do a modular architecture, where with the same code base you could make a web app, desktop cross platform app for mac, windows, and pc, as well as an adobe CPE panel, but overtime it became apparent that the ecosystem doesn't quiet support this kind of setup.
I'd say medium, depending on how you'd define it.
Just myself, on an open source project.
Having some trouble creating a build, and packaging the app with the github actions. And not sure where to turn to.
I try to stay clear of redux. As is, I don't think I wouldn't be able to modify or tweak the webpack configs. But I can use the current setup as a good foundation to architect the rest of the app. I think I found a decent pattern to connect the render process with the main process, but is very verbose (I can share some code if it's of interest) and was also wondering if there are some better patterns. |
@amilajack when you find a minute it would be good to update the original post's text to update the stack text to reflect the changes in recent years (eg, no more Redux.) |
I really like this boilerplate!
I make several apps for hobby and works! (like serialPort Program)
I think 'small'
I am working alone and self-taught.
I know it's hard, but it would be nice if it was better documented.
After all, I think the best is 'react'. Thanks to 'react', I was thinking about user-friendly documentation. Having said that, I am one of those people who would like to see this project continue in the future. I really want to say thank you. |
@BangHyeongSik thanks for the feedback! specifically, what parts would you like to be better documented? |
@amilajack One of the first things that comes to mind is to display the main package in use and the version of that package. And when packaging and releasing a project, it would be nice to have some caution things. |
What kind of app are you making? (Optional) As a dev who has familiarity w/ React but is not as familiar with electron or webpack, this is an absolutely amazing tool to have to quickly get started building platform apps. I would love to see this project evolve and adopt new features such as Vite & as mentioned above improve documentation. The biggest challenge for me right now is understanding all the tooling (.erb files, env vars, linting) so that I can better adapt it to the needs of my project. |
|
What kind of app are you making? What is the size of your team? Are you working on this by yourself? Do you parts of the boilerplate do you find frustrating? What parts of the stack (ex. react, electron, webpack) do you have the most troublesome or frustrating? |
btw: so far I do like erb very much. Thank you for maintaining it! In the process of familiarizing myself with erb, and testing whether I can port my project's features to it, I've made a few erb templates (multi windows, sqlite3, ipfs; might do erb-nostr at some point) that I've pinned to my profile that I hope people may find useful. The sqlite3 one in particular improves a little upon the existing erg-sqlite templates for reasons documented in my readme. (caveat emptor: I'm entirely self taught so there could be issues with these templates of which I'm unaware! 😄 ) |
|
@amilajack Hey! If you want to add it to the list, www.emudeck.com uses your boilerplate :) Thanks for the hard work! What kind of app are you making: EmuDeck, automation tool for automation. Windows, Linux, Mac. |
As a maintainer it really helps to know how people are using this boilerplate. Getting an idea of how people are using the boilerplate can help me correctly prioritize features based how people are using the boilerplate. Answers to the following questions would be appreciated.
The text was updated successfully, but these errors were encountered: