#applinks

RULES

Mun and Muse are both 21+

Starters are open to any and all! I also do not mind if people reblog memes from here.

I am willing to do violent threads, but please nothing involving being held underwater or drowning.

I am fine with asks being turned into threads.

This blog may have NSFW content, but it will always be tagged.

Please feel free to tag me in starters at any time.

Liz  is known for being a bit rude sometimes. Please do not interpret this as me feeling the same. She’s just a stubborn bitch sometimes.

Anon might be turned off sometimes for my own mental health.

I’m almost always open to plotting. You can message me with an idea and I’ll probably be more than happy to do something. If you want something more violent, I am going to have to make it a requirement to talk to me beforehand, just so I know where the thread will be going.

I also have a Discord that is available to mutuals.

Feel free to message me about threads I owe. I have the memory of a goldfish and tend to forget things.

Be kind to yourself! This is all for fun and should be a fun experience for all involved!

BACKGROUND

Birth Name: Elizabeth Marianne Warner

Nicknames: Liz, Lizzy

Date of Birth: October 30, 1986

Place of Birth: Phoenix, AZ

Current Residence: New York City, NY

Other Known Residences: Apartment in Paris, France; Apartment in Florida near SWORD Headquarters; Beach House in the Hamptons

Known Relatives: Markus Warner {father; deceased}; Kathy Warner {mother; deceased}; Louis Dupont {ex-husband; deceased}

Known Associates: SWORD; Rebecca Chen {ex-girlfriend}

Sexuality: Bisexual

Height: 5’ 10"

Scars: Various scars on forearms from stab wounds; Jagged scar along right calf from stab wound; Hidden scar under her hair from a fractured skull

Known Languages: English, French, ASL, German

Employment History: Starbucks {barista, 2005}; Corper Tech, New York Division {assistant, 2005 - 2007}; Corper Tech, Paris Division {Space Division, 2008 - 2016}; SWORD {consultant, 2017-2018; agent 2019-present}

Skills: Knowledgeable in astrobiology, minor hand-to-hand combat training, trained in the use of handguns

Other: Suffers from PTSD

General Description:

Elizabeth is a “works in the grey area” type of woman. She believes that if getting your hands dirty to find the truth is the only way to get it, then she will get her hands dirty. She can be standoffish and blunt, not particularly caring if she pisses people off who are in her way. She has a hard time trusting people and is very slow to offer her help to those she does not know.

General Summary:

Born into a wealthy family, Elizabeth Warner should have lived a happy, comfortable life. That plan changed on her 18th birthday, when her parents were killed in a boating accident in the Bahamas. Completely alone, Elizabeth decided to throw herself into the workplace in an attempt to numb the loneliness she felt. Her dedication to pleasing people caught the eye of Justin Carter, who offered her a job as his assistant. She did her best to handle his day-to-day business and avoid his extremely unprofessional behavior to keep her job…and her girlfriend. However, when Justin learned of her relationship with his daughter, he sent Elizabeth away to their Paris Division, covering up any potential lawsuit by offering to pay for her schooling and a position in the new Space Division. She saw it as a way out of her boring life and took it, leaving everyone behind.

Elizabeth soon made herself known in the Astronomy world, eventually earning herself a Masters in Astrobiology and frequently giving talks about the idea of life outside of our planet. In 2011, she met Louis Dupont, a man who worked for Corper Tech’s Weapons Division. The two quickly connected and married later that year, though Elizabeth did wonder if they were moving too quickly. Their marriage was a rocky one, with Louis frequently trying to pressure Elizabeth to quit her job and her fighting to keep it. She would often be travelling to give talks and go to conferences and returning home became a nightmare to her as she knew a fight would be waiting for her.

TW: VIOLENCE, SUICIDE

In 2015, she returned to their home in Paris to find her husband extremely drunk and belligerent. They argued and when Elizabeth revealed she was leaving, he attacked her. He knocked her to the ground, fracturing her skull in the process, and attempted to stab her. Elizabeth protected herself, getting slashed across her arms multiple times as she tried to escape. He stabbed her in the leg when she knocked him off of her and she later passed out from blood loss. Believing he had killed his wife, Louis committed suicide by jumping from their balcony. When the neighbors called the police, they discovered Elizabeth’s still breathing body. She was rushed to the hospital and spent several months recovering both physically and mentally. She still suffers from PTSD due to the attack.

END OF TW

Since her attack, Elizabeth became very closed off and untrusting. She threw herself into her work once more and was soon approached by SWORD, who wanted her to consult on a strange alien item that had been discovered. She agreed and worked on them with their new project for the next year. Impressing the project lead by her dedication and no-nonsense approach to finding the facts, she recommended that Elizabeth be brought on as a full time agent. Elizabeth agreed and soon moved to Florida to continue her work.

Services & Rates

Process

Testimonials

About Me

"Google now says that it has expanded its app indexing program to Apple’s iOS platform. 'App indexing' is the practice of Hoovering up the data that lives inside apps, the first step to making that information available by Google searching — it’s analogous to crawling the web. Google has been doing this since 2013 for Android apps"

Turning your content ever more invisible and being available at the right time right place is ever more important.

The idea of a "universal deep link standard" is bound to comes up in any conversation about deep linking and the future of app engagement. It permeates the as-yet-unanswered questions about how the various platforms link together, and how all platforms will "play nicely" together to deliver value for the app developers and marketers. And it was something that Vera Tzoneva asked a lot about in December at a Deep Linking conference in NYC.

The problem is that the various issues that many note as arguments in favor of a standard are not relevant. It's one of the reasons why most of the startups in the space have shied way from trying to build a standard, and why the entities that have tried to push their own guidelines as standards have largely failed at doing so.

Will there ever be an accepted deep linking standard?

Nope. I don't buy it. There are lots of reasons why, but let's start with the reality that a standard would require all of the large players to work together, most notably the OS makers. It's not out of the realm of possibility that Google will be cooperative, as they will approach it as benevolent and good for all parties. Apple, on the other hand, is not known for cooperation or openness. They are a closed platform and a controlled environment.

And let's also not forget that though Android has been growing faster, iOS still owns the scale of developers. With so much money flowing through iOS apps, they have no real incentive to share a standard with Google and making it easier for Android developers to unlock some of that cash.

Don't Google's app indexing, Twitter Cards or Facebook's App Links qualify as standards?

No, they are actually more "guidelines" than they are standards. Each of these guidelines allows an app to get traffic from a specificdistribution source. More specifically:

Google App Indexing/Deep Linking: Allows for deep linking just from Google search results on Android from a few Android devices (Nexus was first, and some more recent versions also support this). If you've integrated Google's app indexing and your links are tapped from anywhere else on an Android device besides Google (or anywhere on an iOS device), this integration will not effect the flow.

Twitter Cards: One of the widest deep linking use cases today, Twitter Cards allow developers to deep link from a tweet of their content right into a page inside the app. However, integrating Twitter Card tags doesn't effect the UX from any other major platform, and it will not make all of your content links into deep links.

App Links: Facebook's open API for deep links is called App Links. Its functionality allows developers to drive app-to-app deep links by calling their API and essentially "asking" if that web URL has a corresponding app link in the App Links database. These links don't work anywhere else, and the solution offers no support for web-to-app deep links

Is there a massive need for a standard?

There would surely be benefit. An accepted standard would democratize the process of accepting deep links from all sources, and would certainly allow for a more seamless user experience across all environments. A standard wouldn't require separate support for each individual traffic source to maximize end-user benefit.

But let's be realistic. It's not likely to happen, and we should all accept that. But the smarter platforms (mainly the startups) are building their businesses to leverage all of the guidelines. Specifically, we've designed Deeplink to check the web markup and if the page hosts their app link in some way (Twitter Cards, App Links, Google), we will handle that and launch the app (if installed).

Hint: Test this by taking any Etsy URL and adding "deeplink.me/" to the front! Etsy is not a client, but we'll find the app URI in their App Link implementation and deep link the user from any starting point). Example:  deeplink.me/etsy.com/listing/221773496/cobweb-felted-scarf-wool-scarf-winter

There are a few app developers that host all of the guidelines above in their web markup, and if you view their source code, it's appears clunky and long, and the same data is repeated over and over again. But at the end of the day, if a site hosts their app URIs anywhere in their web source code, then we have all we need to launch the app from any starting point!

These guidelines all help developers structure the data in such a way that it's readable for a specific traffic source, but since each only works with it's own platform, they are definitively not standards.

Is an accepted standard a necessity for the deep linking ecosystem to take flight?

A standard is not a necessity for deep linking to take off and become commonplace and easy to leverage in many different ways. Though a standard would certainly make linking to content easier, our platform exists (and others do too) to help make app content accessible from organic and paid sources.

Link anywhere on mobile

Una novità di poche ore fa. I vari SDK sono stati rilasciati da Facebook in forma Open Source. Prepariamoci ad una nuova rivoluzione.

With the most recent  update Google Chrome is hiding the URL in the bar. So you will only see the main name like example.com, no more exmaple.com/about-us or similar. 

At the same time Facebook launched AppLinks , an open source standard for app-to-app linking and interactions. The project is backed by few big players including Dropbox, Spotify and Pinterest.

Allen Pike concludes and I share his feelings:

While Google is taking the web out of the browser, Facebook is putting the web into apps.

It’s an open, cross-platform solution for app-to-app linking that gives you the tools you need to expose deep links in your app or to link out to others.

App Links is free. It’s open source. It’s easy to implement. And it’s going to make mobile linking a whole lot easier for developers.

Adoption is clearly going to determine this standard's success, but if the rapid adoption of open graph tags are any indicator, it's looking good for AppLinks.