MangoLassi mobile app...
-
@BBigford said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
I guess it would be useful to see who chatted you, but you wouldn't be able to stay connected and chat back until you were back online. Same usage as voice the way I see it.
Ya maybe I'm the only one that looks back through messages. Maybe it's just me but I still have yet to find a mobile site that "felt" as good as an app.
-
Here is an example. When I click the text box in a chat I have to scroll down really far and it ends up doing this:
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
-
@stacksofplates said in MangoLassi mobile app...:
@BBigford said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
Now is offline content something desired? Maybe, but I doubt by many.
Chat is the big one in my mind.
You want to read chats offline? Makes sense I guess, not one that I would have thought of.
I guess it would be useful to see who chatted you, but you wouldn't be able to stay connected and chat back until you were back online. Same usage as voice the way I see it.
Ya maybe I'm the only one that looks back through messages. Maybe it's just me but I still have yet to find a mobile site that "felt" as good as an app.
I think that a lot of that is perception. People do different things with native and mobile and so they tend to be different, but not because they have to be.
-
I wonder if a dedicated chat app would be hard? If it could talk to the API of ML, in theory it could be pretty light.
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
-
@scottalanmiller said in MangoLassi mobile app...:
I wonder if a dedicated chat app would be hard? If it could talk to the API of ML, in theory it could be pretty light.
Ya and would in theory work with all NodeBB sites. That would be pretty nice.
Or integrate XMPP.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
-
@stacksofplates said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
What does the sharing do? I'm unclear which sharing calls that versus calling something else. Do you have an example application that does that?
-
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
What does the sharing do? I'm unclear which sharing calls that versus calling something else. Do you have an example application that does that?
For example if I have an image open, I could share it to ML and then pick where I wanted it to go ( thread or chat) vs opening the browser going to the thread and hitting reply, then uploading the image and hitting the submit button.
-
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
@stacksofplates said in MangoLassi mobile app...:
@scottalanmiller said in MangoLassi mobile app...:
I think that the web client can do that too, just chooses not to
How would it do that?
Offline capability is a base requirement of the HTML5 standard. Nothing special is needed, HTML5 is fully offline capable if the application writers choose to make it so. No additional components needed. It's just the nature of web apps to be able to work offline. That's how OWA, Google Apps and such do it, they don't have any special sauce, it's just enabling offline characteristics of the HTML5 language.
Right but that's all dependent on the browser doing the caching. So it would be nice to have a native app doing the caching and using the native APIs designed for your device vs a hamburger menu on a mobile site.
Okay, but what's the difference? One depends on the browser, one depends on some other code. Both do the same thing. Native app doesn't do it particularly better, does it? I don't understand the APIs vs hamburger, both do both, right?
Well but native gives you things like the roller for selection on iOS, proper integration with other apps for sharing, etc.
I guess the roller, or whatever it's called, is a bad example because you get that with any selection menu even on a website. But I was thinking more of the sharing functions between applications.
What does the sharing do? I'm unclear which sharing calls that versus calling something else. Do you have an example application that does that?
For example if I have an image open, I could share it to ML and then pick where I wanted it to go ( thread or chat) vs opening the browser going to the thread and hitting reply, then uploading the image and hitting the submit button.
Ah, like "Send to ML"
-
I thought about an app for ML but I can't think of any value adding features.
I don't use the chat feature very often but I'll have a look at it after posting this, so I don't have any gripes about it.
I use IE11 mobile, which I feel provides the worst mobile browsing experience possible, but I find browsing ML is better than average. Pages scale correctly but text entry is craptastic if you want to correct a mistake further up in your reply.
-
Chat seems to be ok looking. Not the prettiest or easiest to use but functional
-
@nadnerB said in MangoLassi mobile app...:
I thought about an app for ML but I can't think of any value adding features.
I don't use the chat feature very often but I'll have a look at it after posting this, so I don't have any gripes about it.
I use IE11 mobile, which I feel provides the worst mobile browsing experience possible, but I find browsing ML is better than average. Pages scale correctly but text entry is craptastic if you want to correct a mistake further up in your reply.
It's def better than most mobile sites. I don't really have any complaints, but just thinking of things that would be nice to have.
-
And they keep improving it. I suspect that it will get pretty good as they get time to hone in on it.
-
This post is deleted! -
I see no reason for an app. But then I do not keep many browser tabs open on my iPhone. So it is easy to get back to ML
-
Yes there is no real technical reason for an app, but there is definitely marketing reasons. Here are some advantages I can think of with the app.
-
Notifications - All the people on this thread are fairly active and check ML whether or not they have mobile notifications. The people that aren't as active would benefit the most from notifications
-
Marketing - Mobile app is definitely a bonus to marketing to new users and vendors. Potential vendors would love to hear about app activity and total downloads. You also have the ability to push notifications such as Mangocon in one week or any other major news.
-
Agenda for Mangocon - Boom put the agenda on the mobile app. You could even use GPS location settings for the rooms, bars, national park, etc.
-
Chat - Chat could be a big deal for new users who might be a bit shy on the forum. Get them involved in the chat by connecting them with a group public chat. It's much harder to go and start messaging people to initiate a chat.
-
Contests - Run vendor contests on the app. You can send out push notifications once a month or whatever you decide to run the contests. This will definitely improve participation
-
Events - Calendar with events that may interest ML users.
All this stuff is pretty easy to do
-
-
Bad enough I have you sordid lot in my browser
-
@IRJ said in MangoLassi mobile app...:
- Notifications - All the people on this thread are fairly active and check ML whether or not they have mobile notifications. The people that aren't as active would benefit the most from notifications
Mobile app had that. It was just too annoying
