Basing your apps functionality on what the user tells you they need is considered a wrong approach. In UX it's widely believed best practice to observe your users' behavior and base functionalities on that.
Users don't want what they tell you they want, but want what they
don't know they want.
As for swipe gesture or just buttons, there isn't a clear winner there. Reports and expert opinions differ.
Buttons have a clear and static affordance. It's clear what it does. The affordance on swipes can differ. The Facebook app lets you swipe between several images in your newsfeed when your friend uploaded multiple photos. In some apps, the swipe motion reveals the off-canvas menus on one or both sides. And in other apps it let's you switch between pages. The Flipboard app supports menu swipe gestures. It's takes a little time to get used to the app and some people never get used to it. This is because of the different affordances the swipe gestures bring with them. The trigger is not visible.
Swipes can also be difficult to trigger. In some apps you have to swipe from the outer edges of the screen in order to trigger a functionality. (A lot of) people will get it wrong and they'll blame your application.
Other reports might tell you people want to swipe. They prefer certain interfaces where they can swipe between the content. On mobile devices they already swipe vertically, it's only natural for them to also swipe horizontally.
Buttons are static, normally between 40 and 48 pixels in height and has a fixed place on the screen. Having to reach for the button can be a strain on the thumb. Swipes are normally more "dynamical". The touch area is bigger and it doesn't constrain the user too much.
My advice? Do some more user testing. Check if the users actually try to swipe rather than letting them tell you they want the feature.