What is Flow and what are its top alternatives?
Top Alternatives to Flow
- Git Flow
It provides excellent command line help and output. It is a merge based solution. It doesn't rebase feature branches. ...
Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code. ...
Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process. ...
Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update. ...
Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android. ...
- Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support. ...
A new tool that blends your everyday work apps into one. It's a unified and collaborative workspace for you and your team ...
Flow alternatives & related posts
- Type safe102
- The best AltJS ever47
- Best AltJS for BackEnd27
- Powerful type system, including generics & JS features15
- Nice and seamless hybrid of static and dynamic typing11
- Aligned with ES development for compatibility10
- Compile time errors10
- Structural, rather than nominal, subtyping7
- Garbage collection1
- Code may look heavy and confusing5
related TypeScript posts
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...
I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.
A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.
In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.
If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.
related Git Flow posts
- Unidirectional data flow44
- Structure and Data Flow19
- Not MVC14
- Open source12
- Created by facebook6
- A gestalt shift3
related Flux posts
We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.
But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.
With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.
- Great for collaboration716
- Easy to use627
- Fun user interface126
- Snappy and blazing fast83
- Simple, intuitive UI that gets out of your way30
- Clean Interface21
- Card Structure18
- Easy setup18
- Drag and drop attachments17
- Markdown commentary on cards10
- Integration with other work collaborative apps9
- Satisfying User Experience8
- Cross-Platform Integration8
- Recognizes GitHub commit links7
- Easy to learn6
- Versatile Team & Project Management4
- Better than email4
- Trello’s Developmental Transparency3
- and lots of integrations3
- Easy to have an overview of the project status2
- flexible and fast2
- Simple and intuitive2
- Kanban style1
- Personal organisation1
- Email integration1
- Great organizing (of events/tasks)1
- Name rolls of the tongue1
- Easiest way to visually express the scope of projects0
- No concept of velocity or points5
- Very light native integrations4
- A little too flexible2
related Trello posts
So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.
When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA
With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.
I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.
In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a
Description field. So I am adding
User Stories &
How To Test in the Markdown of the
Description if I could have these as custom fields then my #Agile workflow would be complete.
For Etom, a side project. We wanted to test an idea for a future and bigger project.
What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.
You kind of need a map to work as a proxy between the software and Google Maps API.
We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.
Thanks to all the people behind Create React App it's easier to start any React application.
We also chose a module called Reactstrap which is Bootstrap UI in React components.
An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to
Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.
- Wiki search power93
- WYSIWYG editor62
- Full featured, works well with embedded docs42
- Expensive licenses3
- Expensive license3
related Confluence posts
We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.
We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.
This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.
As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:
- Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
- Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
- Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
- And last, but not least - select the right tools to support effective communication and collaboration:
- All feeds and conversations come together in Slack
- #Agile workflows in Jira
- InProductCommunication and #CustomerSupportChat in Intercom
- #Notes, #Documentation and #Requirements in Confluence
- #SourceCode and ContinuousDelivery in Bitbucket
- Persistent video streams between locations, demos, meetings run on appear.in
- #Logging and Alerts in Papertrail
- Super fast task creation160
- Flexible project management149
- Free up to 15101
- Followers and commenting on tasks99
- Integration with external services57
- Email-based task creation25
- Plays nice with Google Apps17
- Clear usage14
- Plays nice with Harvest Time Tracking14
- Supports nice keyboard shortcuts6
- Integration with GitHub4
- Slack supported2
- Integration with Instagantt for Gantt Charts2
- Integration with Alfred1
- Both Card View & Task View1
- Easy to use1
- Friendly API1
- Slick and fast interface0
- Not Cross Platform0
related Asana posts
Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.
I'm comparing Aha!, Trello and Asana. We are looking for it as a Product Management Team. Jira handles all our development and storyboard etc. This is for Product Management for Roadmaps, Backlogs, future stories, etc. Cost is a factor, as well. Does anyone have a comparison chart of Pros and Cons? Thank you.
- Complete and powerful55
- Huge extension ecosystem31
- Azure integration27
- One Stop Shop For Build server, Project Mgt, CDCI26
- Flexible and powerful25
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- GitHub Integration7
- Cost free for Stakeholders6
- Project Mgmt Features6
- One 4 all6
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Jenkins Integration2
- Link Test Cases to Stories2
- GCP Integration1
- Still dependant on C# for agents7
- Many in devops disregard MS altogether4
- Not a requirements management tool4
- Capacity across cross functional teams not visibile4
- Half Baked4
- Jack of all trades, master of none3
- Poor Jenkins integration3
- Tedious for test plan/case creation2
related Azure DevOps posts
Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps
#Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.
Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.
Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure
Secure Membership Web API backed by SQL Server. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD.
We have .Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. For this service I opted to keep it as a classic WebAPI project and deployed to AppService.
- Trusted Authentication Provider: @AzureActiveDirectoryB2C
- Frameworks: .NET Core
- IDEs: Visual Studio Code , Visual Studio
- Libraries: jQuery @EntityFramework, @AutoMapper, @FeatureToggle , @Swashbuckle
- Database: @SqlAzure
- Source Control: Git
- Build and Release Pipelines: Azure DevOps
- Test tools: Postman , Newman
- Test framework: @nUnit, @moq
- Infrastructure: @AzureAppService, @AzureAPIManagement
- One place for almost every project management work20
- Easy to get started15
- Very structured documents15
- Dark Mode9
- Beautiful design8
- Simple Online Databases7
- Integration with slack4
- Quick edition with shortcuts4
- Api is still in development5
- Lack of database permissions4
- Evernote import flaky2
- No markdown editor1
- Unable to hide key fields in table1
- No integrations with tools like Slack1
related Notion posts
Google Analytics Elasticsearch Amazon Route 53DevOps
GitHub Docker Webpack CircleCI Jenkins Travis CI Gradle Apache MavenCooperation Tools
Jira notion.so Trello