And we are live everyone! An app for individual users, to be able to manage their income vs expenses. One can categorize their data as they prefer and see data regarding their spending habits. https://t.co/sJlMrU0TaF @caffeineai #BuiltWithCaffeine $ICP

App is edging closer. Found 13 issues after thorough testing. Spend the day fixing all of them. Continuing testing tomorrow and hopefully launch the MVP version by the end of the week ahead. #BuiltWithCaffeine $ICP

Day 3: MVP is ready Caffeine is an amazing tool. Yes it caused me a lot of frustrations at times, but maybe it's just the learning curve. I would not have been able to build it in less than 3 days! Stay tuned for the access once launched pending QA $ICP #BuiltWithCaffeine

What impresses me most is that it did all this with less than 2 days worth of work on it, even the fastest of developers would not be able to ship this fast! And finally a screenshot to showcase some of the development that took place! End of thread [3/3]

Still a very impressive tool and I believe I would be able to launch the first version soon, missing some more of the functionality that I would like. An MVP is close to being released now. [2/3]

Day 2 recap with #BuiltWithCaffeine $ICP The was better, still it was slow, and when asked about slowness it stated that it had to rewrite the code every time. hopefully DFINITY would look into this. [1/3]

To wrap this thread of, here's a sneak peak

Still I am very impressed with the speed it build things and eventually it tends to fix itself. I would still use it to build apps as it makes dev in some cases faster, but in others maybe manual intervention would be best!

It got slow with more features! I think this is related to the bad codebase organization as it rewrites the file to do modifications.

It started struggling the more complex the features got. Even when given examples, the implementation would fail the examples.

It does not organize the codebase well! It rewrites the whole file every time it wants to modify it, it does not build modular code and tend to build monolithic files. Was not able to fix that even after prompting it to!

I had to do on average 8 iterations before the bug gets fixed. In one instance I even debugged the codebase, understood the problem, proposed the solution only for it to completely ignore it. on the 8th iteration it built what I had initially stated. That was frustrating!

Day 1 impressions with building with #BuiltWithCaffeine : Still very impressed with it, however, I started seeing some of the pain points with utilizing it. It is not able to resolve bugs quickly. (continued thread)

Got my Early Access and started building a financial tracking app. It's not ready and will share it once done, but man I am impressed. Being a full stack dev for 9 years+, I am very impressed with the speed and how easy it is to use #BuiltWithCaffeine @caffeineai