alliemobley

While of course I'd like to avoid fraud, the point right now is to make an mvp that people can start using for real. We can iterate on fraud prevention once we have something to defraud, and ideally build toward a system that degrades gracefully to use alternative providers in case the primary is down or tries to withold money such that we can just drop in new ones as startups enter this space and compete against one another.

I agree that building an escrow service to solve a construction problem doesn't make sense. It`s like your car needing a new engine so you build a jet instead. Anyone want to build an escrow startup with a garunteed customer lined up?

We think we have a good idea that seems like a bad idea: http://hometract.blogspot.com/2012/09/connectwithcontractors...

Take this with a grain of salt, and some science on the matter.

http://www.iijiij.com/2012/09/01/science-shows-that-self-dis...

Thank you!

Thanks!

Thanks, that's my instinct as well and I'm going for it, looking foward to unveiling it for critique when I have an mvp.

Server Side: I plan to copy those that scaled before me, a mixmash of: pinterest http://highscalability.com/blog/2012/5/21/pinterest-architec... , reddit: http://kev.inburke.com/kevin/reddits-database-has-two-tables... , and instagram: http://highscalability.com/blog/2012/4/16/instagram-architec... architectures.

The previous devs managed to get everything tightly coupled at the design stage, which is why I think their implementation efforts failed.

The plan for now is to seperate the existing code into layers and decide what to do from there.

The right way in my mind is to start over with bootstrap and make this something I can grok. 100's of aspx files are not the way to make this app. Too much premature complexity.

Asp.net webforms, I ought to have clarified that. The REST API i'll create with javascript, perhaps using this c# to javascript compiler: http://www.erik-kallen.se/blog/saltarelle-open-source-c-to-j... to reuse some of the c# once I decouple the objects from the user interface/data. The problem with the code right now is application logic is mixed with the data and display logic. I feel like I can add more value by removing dependencies for asp.net/mssql and trading them for free/open source software. My concerns are: Build it to scale as cheaply as possible. Make it so I can add functionality to the web/native apps by adding new services to the api, to stay dry. Stay flexible for future iterations/pivots. At some point windows/ios versions will come up, so I'm just trying to excersize some economy of motion here. If I create wcf services, we will have to purchase visual studio licenses when we start hiring developers to maintain them.

I have a lot of flexibility. I am equally comfortable finishing up in c#/asp.net or starting over with bootstrap.  I have a contract for a certain amount of money+equity to deliver a working web app, and then we are back to the negotions table where my next proposal will be for the mobile apps.  As for sql server, i think cassandra, mongo, redis, will work just as well. I'm considering using the c# to js compiler currently mentioned on the front page to serve my api to reuse some of the work that has been done. Time constraints aren't anything to worry about, and it would take me an equal amount of time to restart or flesh out the asp.net app.

This is the sweetest story I have ever heard in my life!