I need feedback on app wireframes

[nimble herald]

@here Hello fellow designers! I'd like to request some feedback on the wireframes I've created for a social planning app that aims to help users easily make plans with their friends. 📱🎉

Specifically, I'm looking for insights and suggestions on the screens that will be seen by users who have been invited to an event. I have 3 layouts, which one do you think would work best? Your expertise and input on the user experience, navigation, layout, and overall design would be highly appreciated! 🙌

[steady bobcat]

I think Layout 2 works the best because it allows the user to take an action upfront (takes only one tap) and is similar to Facebook's event feature which users would likely be used to.

I would also move the invite button out of the "Going/Bail/Maybe" section and move it down into the "3 Going - 1 Not Going - 3 Maybe" section.

Lastly, I would also consider making the fonts and font sizes more consistent. Theres a lot of competing font sizes and styles at the moment which makes the screen feel a bit unbalanced.

[fluid bridge]

First one works for me just because the green color, that color caught my attention (acting as user)
i would make those 3 CTA button little bit larger
also that small orange invite circular button more large similar to other profile circles for consistency

[patent heath]

Layout 2. (with minor changes)

Reason being, user would be promoted to this screen if they want to register / got the invite link / or whatever the user flow is, but the purpose of this screen is to let user know about the actions which they can choose from, which are going, bail, maybe, & invite, which in this layout are clearly visible to user and action could be taken accordingly.

The minor changes could be:

1. Assuming that the image icons (below text 3 going , 1 not) are of users who have opted for going, maybe you can Allign then on top of each other (first on top or last on top), if its something else it's OK to keep it this way.

2. Add some lines (not more than 3) below event details such as the topic name or maybe description to let users know what the event is about.

3. You haven't used the green color in layout 2, maybe it's because it's just the wireframe try adding the color and see how it looks.

4. Use only 3 actions in the top, exclude invite from there, ( you will need more research for that, get some insights & then only apply this one), but generally I haven't seen a lot of users invite if they're themselves a attendee. So maybe you can use it as a secondary action.

[patent heath]

Lol. I thought this would be a modal response.

[nimble herald]

Thank you so much for taking the time to review the wireframes and providing your valuable feedback! 😊🙌

I completely agree with your suggestion on Layout 2. Making the primary action more accessible with just one tap is indeed a better choice, and following a familiar pattern like Facebook's event feature will make the experience more intuitive for users. I'll revisit the fonts and font sizes to ensure consistency and balance across the screens, making the overall design more cohesive and visually appealing.

Your feedback has been incredibly helpful, and I'm excited to implement these improvements.

[nimble herald]

Your feedback has given me some excellent ideas for refining the design, and I really appreciate your input. Thanks again for taking the time to review the wireframes and sharing your insights! 🎨🌟

[nimble herald]

Thank you for your insightful feedback on Layout 2! I appreciate your detailed suggestions and the reasoning behind them. 😊👌

Your ideas for minor changes are valuable, and I'll definitely explore those adjustments to enhance the overall user experience and design. Your input on actions, alignment, event details, and the invite button will help me make informed decisions as I refine the wireframes.

[patent heath]

Probably the best given feedback response I got. 😊