Builder.ai is an AI powered platform that helps users builds software faster and cheaper through no code, with the goal of enabling all businesses to become software powered.
TLDR: 28 months into a 6 month project. They stopped developing it without a working MVP, fired all the developers, and do not respond to my requests that involve figuring out what’s happening and when I will be getting a refund.First, please feel free to reach out before removing this review. Builder.ai has taken down our bad reviews in the past saying they couldn’t verify them. I’ll be happy to point you in the direction of the people I’ve worked with including Jason.Second, when I say this is a fraud from the top down, I’m not exaggerating. Please take a look at the news articles that have come out within the last two years regarding their CEO, CFO, and official auditor.If you are still reading, that means you’re still considering it, so let me tell you about my experience.I started this process by meeting with the sales team at the Silicon Slopes Conference in late 2022. I told them about what I wanted to build and they said that would be very easy and doable. We spent the rest of 2022 meeting with developers who reconfirmed how simple this would be and that even with a relaxed timeframe, we could expect a product in about six months. January 2, 2023, I signed the contract.We had a number of problems from the very beginning, including them giving me the wrong documents to sign and mixing my product up with another. We kept meeting, moving forward, struggled constantly with getting the money flow correct. Weeks turned into months and eventually all of the deadlines were past due with no communication on when they would get updated. Near the end of 2023, we escalated and very clearly said that if they cannot develop this, it’s OK to just say as much and give us our money back. They repeated that they could, added additional developers to the team, and said they would be pushing forward with an MVP shortly.When they released the MVP, the flow of money still didn’t work. Whenever I would bring that up or that I wanted to do end to end testing, they would say that they will be able to do that when it’s ready for full release. Again, months passed of this and I stayed patient. I have to say my patience has been the biggest mistake of this entire process.In November 2024, 23 months in on a six month project, they marked it complete. It wasn’t. The money was still wrong, features I had previously approved had vanished, and when I asked why features I paid for weren’t on there, they said they had questions but decided not to ask them and just mark it complete instead. I was furious, but once again I was trying to make it work. I worked with my project manager, and we spent December creating an entire list of every acceptance criteria. I required photo or video evidence for each piece that it was complete or I wasn’t going to mark it done. I also told them they had until the end of March.As we moved through January and February 2025, they started slipping in comments about how they didn’t think we would make the deadline. I continued escalating, people tried to work with me on it, and I decided to once again, find my patience. It did me no good.On March 26, my project manager told me that they were no longer working on developing my project. They had fired everyone who would’ve been part of developing it and had no plans on what to do going forward. They were supposed to tell me the week before when it happened and he expected that I should get an email about it that week. When I tried reaching out to the legal team that same week about canceling any sort of ongoing contract and getting my money back, they told me they were going to refer me to another group. It is April 18, 2025 and still I have received no communication. My patience now means that I have signed myself up for a painful legal battle. I’m leaving this review to let others know that if they already have a contract, chances are no development work has happened for the last month and they need to demand answers. This is also here for people considering this company. Do not fall for it.
Xamarin is well suited for several reasons. The first, it allows companies to share code across platforms. If the app has a lot of business logic and a fairly simple UI, Xamarin is great for this use case. Xamarin also works well if the developers who will work on the app are already fluent in .NET. Xamarin is less appropriate if the company has a lot of developers. If there are plenty of resources to develop apps natively then the headache of dealing with Xamarin's issues are not worth the effort. If the UI is very complex and has difficult animations it's difficult to debug visual/performance issues in Xamarin.
Having also done a lot of native mobile development, some of the IDE's features need to emulator their native counterparts. For example, trying to extract a string resource on Android in Xamarin Studio is painful. There are many useful tools in Android Studio that Xamarin should implement.
Xamarin will always be behind on native platform features. They must catch up when Apple and Google release new platform versions.
The biggest pain point is the random issues Xamarin continues to have. Having a large code base on top of a native platform makes it very difficult to debug issues. Every developer must decide if its an issue with Xamarin or the native platform. Bugs don't get fixed very quickly. Hopefully that will change with the Microsoft acquisition.
Xamarin has been great for developing different projects efficiently and effectively. It's nice to reuse the core business logic across different platforms so that there are less to maintain and little replications are needed. The biggest benefit is that C# programmers do not have to learn a different language to do mobile development.
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and efforts from your development team to be able to build applications seamlessly for android, IOS, windows, and web on a single platform instead of requiring multiple tools to get the job done
I never had to contact support for any help. Most of the problems we ran into, we were able to identify and use peer support through blogs and other internet sources to resolve the problems. There are plenty of sources online which provide tutorials, discuss problems, etc. Example: StackOverflow
Just with any programming tasks, have a plan first. Design out the system, spend time to build it correctly the first time and have plenty of testing and user acceptance opportunities. Xamarin was easy to implement for a C# programmer. However, you need to do tutorials to realize the platform's capabilities.
Xamarin runs natively on MacOS, and the debugger and other integration and auto-complete tools are far better than Eclipse for C# .NET. It also carries much of the plugin/add-on capabilities that are so desirable on Atom. Eclipse is a better for generalized software development, provided a developer is comfortable switching between the IDE the command line for certain parts of their workflow, like building, package management, or debugging. But for C# .NET development on MacOS specifically, Xamarin is the best product I've used for the job.
Code Sharing - We were able to launch an Android implementation of our app within weeks after finishing iOS. The amount of time taken to develop a new platform is very small.
Monetization - not the best, but definitely getting better. We've had issues with finding suitable ad networks that work with Xamarin.
