Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Java

Posted by Fernando Martinez
.a{fill-rule:evenodd;}techdegree
Fernando Martinez
Android Development Techdegree Student 921 Points

wipe me off if I'm wrong. every package have interfaces. have java a list of interfaces?

Every package have interfaces ?? have java a list of interfaces?

tatenda passmore
tatenda passmore
5,773 Points

Most of the times, my approach is that : - I keep my interfaces in a different package, and the implementing classes in different package. That way, if I want to give my interfaces to some one else, then I can directly give away my package that contain all my interfaces.

But again, that completely depends upon your requirement, and the design practice that you follow in your code.

So my choice of package name generally is: -

com.someName.api -> For Interfaces
com.someName.impl -> For Implementing Classes.