Currently the mobile version uses a custom version in which we determine what fields are rendered on the profile. It is not possible to render fields dynamically right at this point of time.

Hello Mark

Fair enough. I understand; however, how about the possibility of using the profile completion rule e.g alternatively to redirect them to complete their profile once they activate their account?

In this case you don't have to render any additional fields the app will simply redirect users to the profile edit page to update these info. Do you think this is feasible?

Hm, currently the native mobile app does not have all the fields that a web has and in order for us to support all those fields, it would be extremely tedious because native app is unlike web.

Ahh Ok.. Well whenever you guys decided to expand the fields on the mobile app, do give this a thought It might be a better way to keep the Registration process clean and simple as it is now, yet, help with enforcing rules on the actual desktop site.

Many thanks Mark.. Cheers!

Hm, I was reading your response again and are you saying that the script should load up a browser to have the user fill in these required fields?

I was reading this thread and have the same idea that I think you bring up Mark. How about having the registration process open up in the browser. After the registration is done on the web, the user can come back to the app and log in.
We also have a relatively heavy registration process and it might be easier to take it out of the app for now.

Hi Mark/Babul

Absolutely right. I am thinking that will help keep the app clean and tidy but also help customers who have mandatory fields.

Mark I know you guys are always willing to be creative with solutions where possible so I will wait to hear your thoughts but you are absolutely right, I think a mobile browser redirect as a temporary workaround pending when you guys develop the app further will be helpful.

Hm, yeah rendering it on a webview could be possible. Let's see what we can do in the future major release because this would also have it's downside where the user experience is ruined.

Awesome! Your willingness to consider it is good enough for me

Thanks! Cheers

Thanks for understanding Michael

So finally I was able to run our mobile built on our phone, and the registration is broken for us as well.

I was thinking about this solution:

How about having on Titan a way to choose between: "Default Registration" and "Web registration". If you choose "Web Registration" you will also need to provide a link to the registration on the web as the destination for the user that will click the Registration button on the app.

Honestly, I think even just doing a regular link will do. Webview is nice to have, but not critical from my point of you (it might even create issue if the registration process is a bit complicated.

For our app, we will not be able to publish the app without solving this first.

BTW, this whole issue also appears at the Edit Profile page on the app. It doesn't reflect our profile fields, so taking this out of the app will be ideal as well.

In 1.0.2, there is an option in Titan that allows you to disable the registration button. You are more than welcome to post feature requests under the feature requests area.

We have tried our very best to minimize the cost for everyone and yet develop a native app that works out of the box.

If you want some features immediately, you can always download the source code and hire someone to tweak the flow for you. That is the beauty of open source

Hi Mark

I understand your viewpoint and I agree it makes perfect sense, BUT, I urge you to still adopt what you said on 26th January at 11.01 and that is, that you guys will give thought to redirecting to web view once a user logs in or activates their account.

This probably can be achieved by adding a backend option in Titan to activate "redirect to web view for mandatory registration fields" if switched on, it will be the case in the build when it is generated in Titan but if not, the app will continue in its currently slik seamless build

I admit as you said this might not be the optimum user experience; however, there are positives to it. For example

1. It is a handy workaround for existing Stackideas ES extension subscribers such as myself and Bulbul who have mandatory fields that help our community function properly

2. It will definitely be a temporary workaround also for potential new ES clients who might be concerned about needing such for their community (that makes it a sales pitch ) ;

3 It means that client's who don't have such needs can continue using your excellent build unaffected;

4. It means Clients don't lose the best support in the world, ES support (Remember you guys don't support external customizations); and

5. Above all, you guys at Stackideas can take your time and continue building the excellent app you have started at the pace necessary without any unjustified cost or alterations to the existing build

It's really only going to affect users who enable such a feature from the build in Titan so you see it will not even be noticeable to those who have no need for it.

I really hope you do give this consideration and I understand you are best placed to make a judgment call but anything you can do for the Easysocial clients like I and Bulbul will be greatly appreciated.

Thanks and have a great weekend!

Michael

Thanks Mark,

Actually I'm very happy to hear there is a way to switch off registration in Titan 1.0.2.

Adding the ability to have a link "register here" on the login page will solve the issue for me. I'm sure this is a relatively easy code for us

If you'll not be able to do it, but honestly I would hate to leave Titan and built by myself haha.
Hope you will consider it!

@Micheal if it will come to it, maybe we can hire a freelancer to do it and split the cost...\

@Bulbul ,, naaa I am optimistic Mark and Team will find a workaround, they always do. Just keep your fingers crossed. I really am of the view that the most efficient way will be to insert a menu one can enable or disable in Titan which will give the option to redirect users to mandatory fields upon login or new account activation. Besides, you cannot get the Stackideas support you get here anywhere else that's for sure and I don't wanna lose that

It is definitely better to start the user journey in the app I think

Thanks guys. Mark, you're the guru here so we'll wait to hear if you have anything you can whip up for us. Thanks once again

There's a lot of pressure building up here but let me discuss with my awesome mobile team and get some response as I am currently locked down working on something else

That's good enough for me. Thanks Mark!!!

Thanks for understanding Michael.

Happy to heart this.

There's a lot of pressure building up here but let me discuss with my awesome mobile team and get some response as I am currently locked down working on something else

Please do not take this as a guarantee or confirmation. I do not wish to put myself in a position where I give broken promises. We will need to evaluate what needs to be done before confirming to anything

Hi Guys,

it seems profile fields are most tricky part. Mark, I fully understand what you said and that if we want something special, we better code it ourself. You can not make app for everyones custom need.

However, can we first testers of app agree/vote on basic mandatory fields for app?

In my case without gender and age I can not publish the app to public. Location is also nice and can be collected from mobiIe.

Even facebook requires this as mandatory info. And no middle name.

I propose these mandatory fields for app:
First name
Last name
Email
Gender
Age
Location

And this if possible ediable in user profile
about me

Best,
Pavol

Thanks for your input on this Pavol. This look like a decent list of fields, does anyone have any other input on the minimum required fields?

Hello everyone,

Pavol's list covers most of my mandatory requirements except hyperlink to "Terms and conditions" for users to read and decide whether or not to accept. I believe everyone will like to have this option for their community so I propose:

- First name
- Last name
- Email
- Gender
- Age
- Location
- Hyperlink to Terms & Conditions displayed in a pop-up window, and button "Agree & Join" like Linkedin or TikTok mobile app

We can't have gender and age in our registration, so ideally, maybe you can choose if a field is mandatory and if you need it to add to the form?

Adding a Hyperlink to Terms & Conditions displayed in a pop-up window, and button "Agree & Join" like Micheal propose will be fantastic to us.

I'm also will be happy if there will be just an option to opt to a registration via web in the app, so each site could build their on flow.

Hi,

I agree with @Michael we can add terms and conditions in whatever form. It is important. (Im just thinking loud if T&C are not in apple and android stores already)

If some of us cant use gender/age so then these should be possible to turn on/off in Titan.
If we have possibility to turn off in-app registration in Titan, we should have link to web registration in app.

Summary of fields:

- First name (mandatory)
- Last name (mandatory)
- Email (mandatory)
- Gender (mandatory or turned off in Titan)
- Age (mandatory or turned off in Titan)
- Location (mandatory-app should ask for location permission during installation - city level should be enough?)
- Hyperlink to Terms & Conditions displayed in a pop-up window, and button "Agree & Join" like Linkedin or TikTok mobile app
(mandatory)

This looks like it is do-able, will discuss this with the team

Hi,
I would be very grateful for 2 fields that are optional
1. URL - the ability for a user to add a link to their site or page in social networks.
2. Text - a simple text field with a character limit. To add 1-2 suggestions about yourself.

Our goal is to keep the registration as simple as possible while still retaining the basic functionality. I believe everyone's idea makes a lot of sense in their very own way of use cases.

In your use case, adding a URL and a Introduction makes perfect sense but it might not make sense for other sites. A simple solution is to make it configurable in Titan and this will eventually cause Titan to end up with hundreds of different configurations. This is going to be a viscous cycle for us.

If you think that there isn't enough fields on the registration form, by all means you should customize and tweak it.

Hi, unfortunately,the "minimum field requirement" concept does not help at all in my case. The above suggestion looks to add only " gender , age,url" from the already existing fields. The main reason for users to join in such social networking ( in comparison FB and other well developed social medias) is because of other added values ,mostly contextual and local.I am confused and wondering if most of you has only these Fields. if you got other feilds, what would be your plan. I was excited listening the possibility of web view. So,are we dropping that discussion completely?

Webview is an option and that is probably not something that can be cooked up so soon. What we are discussing here is probably the fastest solution that we can come up with

Hi Mark,
I agree. Just these 2 fields are displayed in the about me tab, in the user profile. I believe this is logical by default.
I want to note that the code is so good and intuitive that while I manage to solve the vast majority of questions on my own) in any case, I am sure that with you, no question will remain unresolved, one way or another:)

For understanding, I rather mean the profile editing form. I don't need them in the registration form. Such case:)

Hi Mark,
What about instead of webview for registration it will be a regular link to the registration?

It looks like it can really help for all of us that needs their own customize form, and from your development perspective this is very simple, no?

Heck, that would be a very brilliant idea In fact, having the button open a new web browser to register would be the simplest of all and can be implemented right out of the box.

That's gonna literally murder the mobile user experience too sadly; however, I see what you mean Mark.

Is this a viable alternative then:


ACTION: 1
Summary of fields:

- First name (mandatory)
- Last name (mandatory)
- Email (mandatory)
- Gender (mandatory or turned off in Titan)
- Age (mandatory or turned off in Titan)
- Location (mandatory-app should ask for location permission during installation - city level should be enough?)
- Forgot Username and Password Reset links"
- Hyperlink to Terms & Conditions displayed in a pop-up window, and button "Agree & Join" like Linkedin or TikTok mobile app
(mandatory)

with alternative of

ACTION 2
regular link to the registration?

That way, each person can choose what they want which will fulfill their site's requirements.ACTION 1 works for I and Pavol (and perhaps anyone else who does not mind minimum mandatory fields), and if you want extended mandatory fields, you can opt for ACTION 2 with a link to registration.

The option to choose one or the other in Titan would be great! What do you think Mark?

- Gender (mandatory or turned off in Titan)
- Age (mandatory or turned off in Titan)
- Location (mandatory-app should ask for location permission during installation - city level should be enough?)
- Hyperlink to Terms & Conditions displayed in a pop-up window, and button "Agree & Join" like Linkedin or TikTok mobile app

There are also users who also want the above to be optional as not all sites are going to use this. We'll see what we can do with 1.1.0. Right now we are focusing on pushing out 1.0.2 this week. 1.0.2 will contain a huge list of change.

Come on Mark!!, see the sunny side of things. They are perfectly catered for with ACTION 2. If you have an optional link to regular registration in Titan, it means it will render whatever they currently have right? So that's not a problem . We who are happy with ACTION 1 can enjoy the seamless mobile app user experience:p

Anyway, thanks for always willing to find a solution. I trust you and team will work the usual magic. I am definitely looking forward to 1.0.2 but please, like Bulbul, we are unable to really roll out the app without those mandatory fields. Our community functions on those parameters so any last minute creative and witty inventions into 1.0.2 will be GREATLY APPRECIATED!!!.

Cheers!

Hi Mark,

FOOD FOR THOUGHT: I think this is worth considering at this early stage of discussion.

1. How about existing users, I suppose if you choose to include minimum mandatory fields option to the build, it will redirect all users who have not previously provided this information, to update their profile when they login to the app right?

2. I am also guessing that will mean these fields will be editable in the user's profile "Edit Personal Details" section?

3. I think it will be a great idea to include "Forgot Username and Password Reset link"


Just thinking out loud to be sure nothing is missed.

Cheers!

Thanks for your input on this guys! While we won't be able to resolve this in 1.0.2 as there are quite a number of man-hours needed to get this completed, this will definitely be in our next major milestone 1.1.0 or at least 1.0.3.

We are gearing towards 1.0.2 and will be pushing out a release soon that incorporates quite a number of fixes and enhancements which we will be posting on our blog. So stay tune

Hello Mark

Thanks for the update. You previously mentioned and i quote

Heck, that would be a very brilliant idea In fact, having the button open a new web browser to register would be the simplest of all and can be implemented right out of the box.

Can this be provided for in v1.0.2 as a temporary solution? This way clients such as myself and Bulbul can roll out the app, else, our subscription is running but we really are unable to use the app

In 1.0.2, we will add the option to disable the button. I am not sure if we have enough time to change the button to a link, I will check with the guys.

Thank you...that will be much appreciated.

No problem

Hey guys,

The changes are now rolled out into 1.0.2. It does not include the mandatory fields yet but you can now set your custom registration link or hide the registration button altogether, https://take.ms/COStb

Happy first step! I can deploy to existing customers.

Thanks Pavol

Thank you Mark.

Thanks for your input on this guys! While we won't be able to resolve this in 1.0.2 as there are quite a number of man-hours needed to get this completed, this will definitely be in our next major milestone 1.1.0 or at least 1.0.3.

If anyone wants to join me, I propose a vote and suggest the following registration fields be standard in next major milestone:

- First name (mandatory)
- Last name (mandatory)
- Email (mandatory)
- Gender (mandatory or turned off in Titan)
- Age (mandatory or turned off in Titan)
- Location (mandatory-app should ask for location permission during installation - city level should be enough?)
- Forgot Username and Password Reset links"

Thanks Arlex.....done

Thanks Michael.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.

Hey guys,

I am not sure if you guys are aware of this but Michael has already started a new thread on the feature requests area, https://stackideas.com/forums/vote-for-registration-fields-editable-to-be-included-in-mobile-app . Nobody seems to be giving any input :\