6
9 Comments

How to prioritize what feature to implement next.

I am an iOS developer and I am going to be straight up with you. I have dozens of feature ideas for my iOS Apps.

Every time I ship a new update with a new feature I hope current users would love it. And new users would come because of the new features my app offers.

The sad truth is, for some reason, this isn't happening.

Why? I think it is because I don't -know- what features my users would love to see. Most of the time they don't even have a way of telling me.

So I built an SDK: https://www.wishkit.io

I wanted it to feel like: it just works ✨

One line of code to rule them all.. or to get a full-fledged native feature wishlist into your iOS app 😆

Users can create feature wishes and upvote them (think reddit)!.
And I? I can prioritize the next feature based on votes. I have an app where one wish has over 500 votes 🙈

Would love to hear what you think of this SDK.
I am super open to any kind of feedback or criticism 🫡

on March 15, 2023
  1. 1

    Having a feature wishlist can be an effective way to engage your users and gather feedback on what features they would like to see in your app. It can also help you prioritize your development efforts based on what your users are asking for.

    Your SDK seems like a straightforward way for iOS developers to add a feature wishlist to their app, and the fact that users can create and upvote feature requests is a great way to crowdsource feedback and prioritize feature development.

    One potential downside to this approach is that some feature requests may not be feasible or may not align with your overall product vision. It's important to set expectations with your users and be transparent about what features you can realistically add to your app.

  2. 1

    Hey Martin! It's a common challenge for developers to prioritize features, and it's great to see you tackling the issue head-on with your SDK, Wishkit.io. Giving users a way to voice their feature wishes and upvote them is an innovative approach to ensure you're focusing on what matters most to them.

    I like the simplicity of integrating your SDK with just one line of code. It makes it easy for other developers to adopt and benefit from it. As for feedback, I would suggest providing clear documentation and possibly some use-case examples to help potential users understand the full potential of your SDK.

    Good luck, and I'm looking forward to seeing how your project evolves! :)

  3. 1

    Thanks for sharing, cool idea.
    https://www.upvoty.com/ does something similar but I think it's only web-based.
    They are highly profitable, the founder is knocking around IH I think.

    1. 1

      Hey DadDev,

      You're right and you also pointed out the gap I am trying to fill: native.
      There's a handful solutions that offer similar features but they are all web based.
      And that is fine if it works for you!

      I know from myself and from other iOS developers that when they could chose they'd prefer native over webview. A native high quality experience is what I am aiming for with it :D!

      1. 1

        Yeah the only concern with these sort of native experiences is to communicate that it's an option to the user without taking up valuable screen real estate on mobile. I don't really like anything that requires a shake to start it, it's too easy to forget it exists if there's no visual cue IMO. It looks like your SDK has a button but is it stylable to the existing App's style system?

        If you have any feedback on my ideas I'd love to hear it.

        1. 1

          You can chose what presents the wish list. A tab bar spot. A button. Or a place in your settings. Up to you. And you are right, the primary color (the plus button, arrow up, etc.) is configurable to match your apps color 🙂

          I read through your list, your list is like 30 entries long and starts from 1 a few times haha

          1. 1

            Thanks for reading through it and offering that feedback. I cleaned it up and whittled it down if you have any thoughts now.

        2. 1

          I think you could also charge a lot more. If this results in one killer feature for a big app that could be hundreds of thousands in revenue. You could charge at least 50$ a month if you can prove that might be the case using testimonials or data.

  4. 1

    I am a big utiliser of such , and the key is radical transparent

    • so many vote FR solutions have many stale FR . Many of these are key. So if needs explanation why it is not moving. FR are best as a 2-way conversation . Most solutions are one-way convesation
    • after 20 -50features, the list becomes less usable from a citizen perspective. Need ability that can find all the correlated, like features. graph polls help
    • List will need moderation, and transparency around how that is done
    • Some mod actions are best given champions or GA (citizens). Of course depends on breath of app)merging FR needed by mod and citizens.

    I am looking for FR solution that allows users to snap-submit from the device. Especially with iphones new live-text capability. Why type when u can snap?

    Feedback made easy, happens quickly. Record/video what I am doing, or or trying to do and cannot. Snap a picture, tag it auto (like geo tag for the app), submit. Make it 1-click style action. The capture is richer when context is fully retained.

    n general the more data crowd sourced the greater need for citizen style apps (citizen scientist as the ocean cleanup uses, or snapsendsolve for councils). Just not seeing any great solution in this space.