5 questions to ask ourselves before using a third-party library in an app

“Don’t reinvent the weel” is a quote we’ve heard a lot as developers during our career. We’ve been constantly encouraged to design our apps making sure we’re not re-writing someone else’s implementation because, at the end, we would supposedly reduce our estimates and make it faster. It’s totally understandable that we should be efficient enough to build software…

Keep the story going. Sign up for an extra free read.

You've completed your member preview for this month, but when you sign up for a free Medium account, you get one more story.
Already have an account? Sign in

David Sánchez Guido

Written by

Lead iOS engineer at Globant. CSM. Food lover. Passionate about traveling, video games, new technologies, and building teams that makes great software.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade