Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
12
Likes
60
Comments
by
I’m building Doka an image editing plugin and am using Svelte for the next major version. It’s very fast and the resulting codebase can be used in other frameworks + Svelte can compile to web component.
👉 https://pqina.nl/doka/
Quick impression:
Dev updates: https://twitter.com/rikschennink/status/1260215801602244608?s=20
That looks super-nice, @rikschennink. So polished.
Very refined tool.
Looking really good!
Thanks 🙏
This comment was deleted 6 years ago
This comment was deleted 6 years ago
I've been quite into Tailwind CSS. It's pretty much the least number of characters possible to achieve good CSS styling - the entirety of getfluency.io fits in like, 100 lines: https://github.com/noahsark769/fluency-website/blob/master/src/pages/index.js#L78
I built an online video editor Story Creator
I am just using good old React.js
Elm! Actually I haven't started my project yet, but the next one will be an excuse to program in Elm again. It's such a joy to create a frontend app with Elm. I'm actually quite surprised not many IndieHackers use it, as it completely avoids one of the biggest time-suckers of a new project: bugs.
I know it's a functional language and it can look pretty alien compared to languages as Javascript, but it only takes a few days to be fluent with the language and the architecture.
I have to use React + Redux (actually Redux is heavily inspired in the Elm Architecture) at my current company and it's a total pain compared to Elm.
For those interested, I recommend this great video by the great Richard Feldman:
https://www.youtube.com/watch?v=FV0DXNB94NE
Angular, Angularfire + Firebase, amazing stack imo, angularfire has great support, and firebase firestore is incredibly fast.
TypeScript + React + Material-UI for the front-end of my analytics platform: https://www.usertrack.net/
It's funny that the backend is really simple in comparison, plain PHP + MySQL, without any framework. Each API end-point/database call is just a separate file getting the query parameters from POST data, checking permissions and returning the query results.
I've designed and developed three pretty complex apps over the last few years. The most complex by far was built for a mosquito misting company with approximately 5K users (around 1K active) and 4K data-reporting devices spread throughout 15 countries.
For that app, and for the other two I've been working on more recently, I've used the same two core libraries:
Happy to answer any questions if anyone has any. As far as a CSS framework goes, I've recently transitioned to Tailwind over from Tachyons, but find that I don't particularly like the new setup even though I can see the benefits of using it.
I use Gatsby for my blog for SEO, speed and image performance.
Create-react-app for a custom CMS admin (admin no need SEO). NodeJS for backend for now, but will likely move to Serverless for cost cutting.
I built 2 projects using Vue/NuxtJS but recently moved to ReactJS for my latest project (which is SaaS). I find React much better to have the flexibility needed.
This project is a schema.org builder, it's been fun working on React project so far.
Hi kayz0r,
I worked with both VueJS and ReactJS, but in the past 3 years only with React. I was thinking about switching to Vue due to the cleaner syntax and simpler implementations, but then React hooks came out and the React code is cleaner now.
What things are you missing from Vue after the switch?
Actually vue code make things look cleaner, I love the way we do v-if/v-for and such. I love the way Vuex works in vue. Also vue router is way better than react-router-dom.
Also Vue is true "Reactive" platform whereas in react you have to "setState" for it to react to changes.
However React has much better community/frameworks associated with it. Also the fact that it's used in large scale projects makes it the preferred option.
Another big issue for me in VueJS is that most plugins/3rd party components are poorly maintained and are a bad copy of existing react plugins.
I love the simplicity of vue really, but overall react made my life much easier.
I agree, I love Vue for what it is and what it tries to be, but it sometimes feels like a toy compared to React, which instead feels a lot more powerful and with a bigger ecosystem.
I also feel that Vue development rate went down a lot, I think Vue 3 was announcened like 2 years ago and it's still not released.
yes Vue was a bit over hyped, I think the main reason was the simplicity of writing your first pages. But when you do some real stuff you see huge weakness in their ecosystem (this is especially true for Nuxt which is very fragile and not meant to be used for professional project imo).
While Vue get you on the run very quickly (it did for me), if you want to do something complex with it, you will loose all the time you saved trying to find a decent option/component (mostly are Chinese components that are poorly functioning with poor documentation and never tested in real production environment). Overall I think VueJS is good if you want basic website and nothing more.
This comment was deleted 6 years ago
@ybrickman thanks, the reason I started this project is because of the struggle I faced with building proper schema for my websites. with this tool now you can build 100% professional schema in few minutes and publish it. Still though I have a lot of features to add to make it production ready.
React components can be class based or functional which gives you great way to do things that are difficult in other libraries. You can define a component as function and call it anywhere, pass it the parameters you want, inject it inside of a component or child-component etc, this makes react powerful to build complex apps. In addition this makes it easy for others to build react components that you can use in your projects.
The downside of react is routing. its really primitive compared to vue router but I can live with that.
Currently I am looking into api-platform.com and quasar.dev.. These 2 things in combination can do many things for a business
api-platform is built on top of Symfony framework (PHP). It can generate API for any given data model in 2 minutes.It can also generate admin CRUD screen in any of the popular frontend JS frameworks. Quasar is one of them.
Quasar is built on top of Vue.js. With this using a sigle code base you can create SPAs (Single Page App) ,
SSR (Server-side Rendered App), PWAs (Progressive Web App), BEX (Browser Extension), Mobile Apps (Android, iOS) through Cordova or Capacitor , Multi-platform Desktop Apps (using Electron) all at one shot.
I am feeling this a complete development kit right now.
Quasar is nothing less than amazing!
Been using it on 3 projects now - 2 web apps and one website.
Building something from scratch is blazing fast, and the learning curve is really quick.
It has all the components you can (and can't) imagine, and you can always use any vue component that you want (vue itself was also quick and fun to learn)
The result looks professional out of the box, even if you're not a designer.
Oh, and they have great documentation.
You can see my last project with them here : https://editor.charttt.com
This comment was deleted 6 years ago
I spent around one day on this. My experience was really good.
I am planning to use it in my next product.
Personally I use VueJS for all kind of web apps :)
This comment was deleted 6 years ago
Generato.com is built with Angular and Ant Design, and I liked it because of the separation of concern and the streamlined development process.
Give it a try 😉
This comment was deleted 6 years ago
I have been around with Angular since version 1, and I like to follow these concepts of services, which can be injected into each other. Also the simple binding management of smart and dumb components and their pages seems pretty easy for me.
The best thing about Angular in my opinion is that it includes that many functionalities right out of the box, like service-workers, web-workers, schematics, serverside, ...
In terms of CSS, I'd just use Tailwind.
One of those is not like the others!
Webflow and Slack both have pretty mundane needs. You could use any of the popular SPA frameworks, or none and just use lighter libraries (just like HipChat, the product Slack cloned).
For Figma, the complexity and the performance requirements are extreme. For something like that, I'd work at a lower level, using Rust and WASM and I'd avoid a heavier front-end framework. In fact, I don't think you could make a Figma clone without WASM.
This comment was deleted 6 years ago
It probably is more complex, but you could use the same tools to build it.
Figma is in a different class because there's a LOT of vector graphic processing involved in it and TBH all its real competitors are native apps for that reason.
P.S. Not sure why I'd be downvoted to zero for my above comment but it's a pretty strong discouragement from trying to help people out.
I would go with Vue + Vuex + PWA buildpack, and I have gone this way with huge success in many of my projects: ease of maintenance, clear codebase, readable code. It just works and it's really fast. Some of my PWAs feel almost like a native app when installed on the phone's homescreen (tramspotter.com is a good example).
I worked for a year with React + Redux on a commercial project for a big UK grocery chain, and I would not recommend it. I'm a purist, so the JSX syntax is like kryptonite to me. Also prop drilling and a component abstraction are the seventh circle of hell.
As for Redux, I wouldn't touch it again. I don't know who made it, but it doesn't make any sense to me. That said, I'm no software engineer, just an old-school frontend dev, so I might not understand "the great React/Redux way".
The choice for me comes down to how close to the bare HTML/CSS/JS a given framework is. React is way too abstracted and looks like something from a different world. In case of Vue, I can write my code using Web Components compatible syntax and not worry about the future, while the framework does the heavy lifting and is very performant.
This comment was deleted 6 years ago
I was able to compare them side-by-side, and honestly, the only reason my team went with React + Redux was because that's how they rolled before.
So I spent time learning React and Redux, and the previous comment is my honest evaluation after a year of using both, shipping some serious software daily for a big grocer.
Wouldn't go back to React (or Redux) even for a single day, unless for really big bux.
I'm using NextJS and Redux for Makerlog.
It's a fast, SEO friendly stack. I actually had to go through a transition process - moving from Create-React-App - it was seriously hurting my SEO. Took almost a total frontend rewrite, but was totally worth it!
In terms of Redux, it's fine. It's less boilerplate-y if you use the Redux Ducks pattern.
So... word of advice: use NextJS! :)
How did you identify that it was hurting your SEO, out of interest?
Makerlog's a community product, and not being able to do things like dynamic social cards was really hurting shareability.
This comment was deleted 6 years ago
That was one mistake I'm never making again. NextJS or bust!
I use VueJS, mainly I am comfortable with it already, don't want to spend time on a different tool learning curve.
This comment was deleted 6 years ago
I built this https://app.howuku.com/share/playback/Qj9WHoax with VueJS. I have some past experience with Angular but when VueJS comes along I immediately got hooked for how intuitive is it to start building stuff.
This comment was deleted 6 years ago
I'm using Vue.js + Inertia.js with Ruby on Rails on backend for flowboardpro.com. I recently tried to sum up my stack in a tweet (https://twitter.com/BilalBudhani/status/1258607575110737929)
I read multiple comments on this thread who pointed out they moved or planning to move away from Vue to React. Well, I actually moved from React to Vue and couldn't be happier. I personally find Vue very productive and easy to work with, also there is a huge collection of libraries available in Vue ecosystem as well.
This comment was deleted 6 years ago
Rails, ActiveAdmin, React
Great community and great support documentation. Using rspec and capybara for end-to-end testing. Rails is well known for being really great for getting going quickly
I was scrolling trying to find if there was any RoR response yet :)
I'm just finishing an MVP with plain Rails and will look for the react integration after the first round of feedback. Did you have good experience migrating typical Rails projects to React + Rails or...? In order to let open door I have started been careful to not abuse assets-pipeline and using webpacker, but I expect some surprises on the way.
I did do this a few times before (migrate entirely from Sprockets to Webpacker). I was planning to write a blog post for some steps to set up React in a Rails app. Would you be interested in reading that?
If so, would you like to join my mailing list so I can get in touch when I finish the article? http://eepurl.com/g2ixBT
That would be great, joining! :)
This comment was deleted 6 years ago
It works seamlessly. Rails 6 (latest) has native support for webpack (the package is https://github.com/rails/webpacker).
If you want a brief demo of how that might work, take a look at: https://medium.com/@cionescu1/how-to-use-react-components-in-active-admin-184ff63b378d
It describes the integration between an admin framework in Rails (called ActiveAdmin) and React
React + Gatsby + Figma and Netlify for Hosting.
Ant Design for components.
http://aasaanai.com/
This comment was deleted 6 years ago
Next.js + React + Mobx
https://getworkrecognized.com/
I am using Next.js mainly for Server-Side Rendering and React because I am comfortable with it. I am coming from Vue.js but the transition was kind of smooth. I ditched Vue.js for now because I am not really convinced by the approaches they are taking with Vue.js 3 and so on. React also has more open-source components that I can use.
Mobx was just used for the user state. Normally I handle everything with local state and hooks. Really clean. I mostly style my components by my own with styled-components.
What would I change? Nothing to be honest. I am super fine with my stack and can develop quite fast with it :)
This comment was deleted 6 years ago
The trend is probably observed because React is used more in the industry and that's where the money is.
I just wanted to try Mobx to be honest. I am using Redux at my full-time job and do not really like it. But I guess its just an opinion.
More or less you are right with Next.js + React comparison. Next.js gives you things like routing on top though. Of course I could use create-react-app and have multiple applications but I am a big fan of a mono repo. Since my backend is an express app, integrated into Next.js everything is a monolith. I can share TypeScript types from database entities to the frontend easily which makes it super easy to make changes.
This comment was deleted 6 years ago
I am using loose type checks aka "strict": false. It is what is working out best for me. I plan on doing strict typing at some point but not for now.
I mainly use it for the communication of backend entities to the frontend. The rest might be typed if it is a bit more complex component but in general, no types.
React + Redux
mowned.com
Not near that complexity level.. but lots of logic implemented here. 44.130 LOC according to "LineCount" (vscode extension).
I wanted to try and learn React. So I decided that's the best way with a SPA (single page application) - everything in the frontend is React. For animations I'm using Framer Motion.
Probably I wouldn't switch to anything (for this project), though I like also Vue and been used it lightly in other work related projects
This comment was deleted 6 years ago
No problem!
Here is a demo account if you want to check the onboarding too:
demo@mowned
demo
I've picked Redux because I've wanted a global store. I've store there all loaded phones, showcases and so on in a normalized way. I cache the results with a timeout, so if you go on the same page, i try to load from cache (store) first.
As for SEO, no server side rendering. Google crawlers are very capable, the site is indexed in google. But the indexing is slower than in normally served projects (don't know how much).
Most of the traffic is viral (eg: user x share, user y, z register, user z share, and so on).. so yeah, seo is a weak point.
Vue.js, Vuex because I had a lot of experience with it and it is a good library.
https://tranzlate.io
But I would like to change to React.
This comment was deleted 6 years ago
The amount of libraries for React is extensive. It looks to be more widely supported and improved.
But hopefully Vue 3 will have some considerable improvements that will help it progress. Vue 3 is already starting to be more React-like.
I actually moved to Vue from React and honestly finding it very productive. I believe Vue ecosystem is equally rich and vibrant. Sure Vue 3 is moving to more functional approach like React but it still has a lot of differences.
React, nope.
https://versoly.com/ probs 20k+ LOC using a ton of open source libraries.
I have built software that rivals companies with 3000+ employees by myself frontend wise.
This comment was deleted 6 years ago
I tried angular 1 back in the day and it gave me nightmares lol.
After trying react for 30 minutes I was a believer.
I tried Vue but by then I was sold on how React did it.
Yes I use CRA, I also used Gatsby.
For my next projects I will use next.js
Why next.js over Gatsby for your future projects?
Felt like I had to fight gatsby all the time.
Thanks for the feedback. I just switched from CRA to Gatsby recently. The transition was a little rough at first but seems good now. Are you planning on using next for static site generation or as a server-side renderer? I originally chose Gatsby because I thought it seemed better than next for static site generation which is my preference over ssr. I saw next recently made some improvement to static site gen features so it looks like they are focusing on that more.
This comment was deleted 6 years ago
use Keajs on top of redux
Figma and Slack are completely different levels of complexity - you can totally build Slack w/ React. Figma was built in C++/WebAssembly (as per https://www.figma.com/blog/webassembly-cut-figmas-load-time-by-3x/)
This comment was deleted 6 years ago
I’m using React/Next.js for divjoy.com and it’s worked out well. The built-in app editor is fairly complex and would have been hard to build without taking advantage of many open source React libraries (such as a React DnD and React Sortable Tree). I’d definitely stick with React because it’s what I know and it has a great open source ecosystem.
This comment was deleted 6 years ago
This comment was deleted 3 years ago
Stencil looks very promising, thanks for sharing.
This comment was deleted 4 years ago
I'm using Vue and Vuetify as well.
This comment was deleted 6 years ago